6.18 EOS Solutions

Chapter 6

Section 18 – Enterprise Output Solution (EOS)

6.18.1 EOS Overview

Enterprise Output Solution (EOS) offers an electronic option to route mainframe and PC reports to a paperless online facility for the purpose viewing, printing, downloading, and emailing of reports. EOS also offers the ability to archive reports and restore them from the archive.

6.18.2 Billing of EOS

EOS is a billable resource administered by the BIT Data Center Resource Billing.

Each EOS user account is billed:

	A one time charge for a product viewer license
	An annual maintenance fee for the account viewer
	By individual report based on size of the report

Reports are not billed if defined to EOS with a one day online viewable time and zero archive retention. These reports are deleted at midnight of the same day. All other reports are billable.

For additional information refer to the BIT Web site for current rates or contact the BIT Data Center.

6.18.3 Admission to EOS

New users of EOS are in essence leasing an EOS Product License. Acquisition of an EOS license requires management approval or authorization via a BIT Developer on behalf of an agency requestor. The initial request for a user to access EOS must be sent from a management position to the BIT Help Desk.

BIT Help Desk staff will return a “Request For Product License” form to the requestor to gather information tailored to the person who wants to use EOS:

	Name, work address, and telephone number
	Network Id Account
	RACF (Resource Access Control Facility) USERID
	State Agency employed by
	Select access: Thin Client OR Thick Client
	Specify if EOS AFP (Advanced Function Printing) support is desired. This requires another EOS License at additional cost
	Accounting code to which the EOS license is billed
	Accounting code to which product maintenance is billed
	Mainframe job statement account code to bill EOS report printing

Upon receipt of the completed “Request for Product License” form, BIT Help Desk staff will proceed with overseeing the task of establishing a new EOS user account.

6.18.3.1 Establishing an EOS User Account

1) If necessary, BIT Security creates a RACF USERID for a new user.

2) The BIT Data Center Systems group validates the billing number.

3) BIT Production Control staff defines an EOS user profile for the USERID.

4) For a request outside the SD domain firewall, BIT Integrations installs Citrix Full Desk Top.

5) For a request inside the SD domain firewall the requestor has a choice of Thin Client or Thick Client.

6) LAN Services staff will define a new user to the appropriate Citrix Group depending on agency and location. These groups are Group SD Citrix EOS-G and Citrix Program Neighborhood Group SD Citrix EOS Thin Client-G.

7) The EOS Training Group educates user on EOS.

6.18.3.2 Transfer of EOS License

It is permissible to transfer a license from one person to another within the same department, with manager approval. Forward an Auto Call ticket request to the BIT Help Desk with the following information.

1) Name of current user

2) Current RACF User Id

3) Name of new user

4) New RACF User Id

5) List of authorized reports (if no list provided all old user reports are deleted)

6) Date the transfer is to take effect

7) Reason for license transfer

6.18.4 Defining a Report to EOS

A report owner or a BIT Development Agency point-of-contact are the only persons authorized to define reports to EOS. Submit an email request to the BIT HELP Desk, asking for an EOS Report Definition form.

Upon receipt of a completed EOS Report Definition form, BIT Help Desk staff will have BIT Production Control staff define the EOS report assigning it a unique Form ID (name). The Form name along with the options specified on the Report Definition form, instruct EOS how to manage the report. For assistance with filling out the form, contact BIT Data Center Production Control by email 'BIT DC-PROD.CNTRL.SERV.REQUEST'. Here are the options.

Name of report (usually the job name or variation of it)

	Specify request type; new report or changing an existing report definition
	Brief description of the report
	Select a report type: Mainframe line print, AFP, AS/400, RS/6000, or PC file type (doc txt xls rtf jpg gif htm pdf tif bmp pcs pst ppt rpt)
	Primary owner of report; name and phone number of person responsible for granting other persons access to the report
	Secondary owner and phone number if the primary person is unavailable
	Name and RACF USERID of persons authorized to access the report.
	Mainframe job statement account code to bill EOS report printing
	How often the report is generated.
	If a report Table of Contents is desired, describe the criteria.
	Provide instructions if report is to be divided (split) for multiple recipients
	Specify length of time a report is to remain online and if desired specify how long the report is to remain on the EOS Archive. A report to be archived longer than three years and 1 day requires accompanying documentation of justification from Records Management. Default archive retention periods are:

Daily reports 5 days a week Retained 11 days

Daily reports 7 days a week Retained 15 days

Weekly reports Retained 15 days

Bi-monthly reports Retained 21 days

Monthly reports Retained 35 days

Quarterly reports Retained 113 days

Annual reports Retained 180 days

Non-defined reports that are routed to EOS are deleted.

It is the responsibility of the Developer to update job JCL with the EOS form name destined for SYSOUT CLASS 9 so the report will be routed to EOS.

//ddname DD SYSOUT=(9,,form)

6.18.5 Modifying an EOS Report Definition

The report owner or BIT Development Agency point-of-contact are the only persons authorized to make modifications to an EOS report definition. The request is initiated by sending an email of intent to the BIT Help Desk who will return an EOS Report Change form to the requestor.

EOS Report Change form - required information

	Name of report
	Date the modification(s) is to become effective
	Name of person authorizing the modification(s)
	Describe the nature of the change(s)

Upon receipt of the completed EOS Change form, BIT Production Control staff will update the Report definition in compliance with the requested change(s). And the BIT Development staff will update job JCL as necessary.

6.18.6 Viewing EOS Reports and Recalling Archived Reports

Reports may be viewed using either EOS Thick Client or EOS Thin Client. However, a license for AFP Viewer is required to view AFP formatted reports.

EOS reports are archived on a daily basis according to the specifications defined for individual reports. Once a report is archived it is removed from the online data base and is not directly viewable.

EOS Thick/Thin Client facility can be used to browse the index of archived reports and select a report for recall from the archive file to the online data base where it can be viewed. The report is scheduled for the next recall task; those being at 10:15am, 12:15pm, 3:15pm, and midnight.

In an emergency, a report can be scheduled for immediate recall from the archive by contacting BIT Data Center Production Control by email 'BIT DC-PROD.CNTRL.SERV.REQUEST'.

A recalled report is simply a working copy of the archived report that is viewable for 7 days, at which time the working copy is automatically deleted. The original report remains untouched on the archive as per your pre-defined specifications.

Reports defined to EOS with a zero archive retention period are deleted when the online viewable time expires.

6.18.7 Downloading EOS Reports - Mainframe to PC

The security of a downloaded report becomes the responsibility of the person performing the download.

Both EOS Thick and Thin Client products can be used to download a copy of a report from the Server Report List on the EOS data base as a txt file in a folder on the PC hard drive. For those within the state intranet using EOS Thick Client through a Citrix server, the downloaded reports will be stored on PC hard drive directory H:\WORK\EOS. EOS Thin Client users must define a path to the destination folder each time a download is performed.

For those outside the state intranet using EOS Thick Client loaded on individual PC hard drive, downloaded reports are stored on the C: drive in directory C:\WORK\EOS.

Reports downloaded to your local drive are retained for a maximum of 60 days and then automatically deleted. You may manually delete the downloaded file.

6.18.8 Uploading EOS Reports - PC to Mainframe

Prerequisites to uploading a PC report file to the mainframe EOS for viewing:

	Have permission to use EOS as described in “Admission to EOS” and “Establishing a New EOS User Account”
	Assign an EOS Form ID to the report as described in section “Defining a Report to EOS”.

BIT Production Control staff will create a DOS BAT file and send it to the user of EOS who must save the BAT file on the same PC folder that the report file will be uploaded from.

The PC report file must be in one of these EOS recognized file formats: doc, txt, xls, rtf, jpg, gif, htm, pdf, tif, bmp, pcs, pst, ppt, rpt. And the report file name must remain the same for each upload.

The EOS user may initiate the upload process by executing the appropriate BAT file that contains the FTP commands which perform the upload process. The uploaded report is sent directly to the EOS data base in the original PC file format and distributed according to the EOS form definition specifications.

6.18 EOS Solutions