COMMONWEALTH OF PENNSYLVANIA

DEPARTMENT OF PUBLIC WELFARE

INFORMATION TECHNOLOGY PROCEDURE

Name Of Procedure: / Number:
Automated Procedure Request Form / PRO-IOS008
Domain: / Category:
Operations / General Operations Procedures
Date Issued: / Issued By:
Unknown / DPW Bureau of Information Systems
Date Revised:
08/12/2009

General:

To provide a systems standard for implementing or updating a data processing flow.

This procedure will provide the Bureau of Infrastructure Management and Operations personnel with standard documentation for each batch run which is to be run for the Office of Information Systems.

Reference “Automated Scheduling, Distribution, Tape Library System” in this document.

Procedure:

Batch Run Request Form

The automated scheduling request form requires the following fields be completed for computer scheduling to proceed:

A. Run Name, Account number, Qualifier: Must be the same as on the @RUN statement of the job’s runstream.

B.  Common Name, Host: Enter how you refer to the job flow, and the system where the job will execute.

Example: Common Name BCS Daily Host Production (A)

C.  Start Key: Must be the start statement in the format entered by the operator including the account code and user ID. The run and the element name should be identical.

Example: ST PROD*ECL-LIB.ELEMENT,,,999999/XXX

D. Frequency: Enter the exact frequency that the job should run. Include whether the job should run on holidays.

E. Data Base Data: Mark an "X" in the appropriate block - UPDATE, RETRIEVAL,1 or N/A, or note the data base function.

1. Schemas and Subschema Names: Enter if a database run.

2. Common Data Base Name: Enter common name.

F. Analyst Name: Enter responsible person.

G. Switch 23/24 software used: Enter "Y" or "N"

H.  Job error instructions, Restart From Beginning, Notify Analyst:

1.  If the job does not include checkpoint restart capabilities and must be started from the beginning, enter YES.

2.  If the job includes checkpoint restart and may be restarted at a checkpoint, enter NO.

3.  Specify whether the analyst should be notified immediately, or the next workday.

I. Possible Job Conflicts: Enter run names if any.

J. Mass Storage Total Fixed Tracks Needed: Enter the number of tracks.

K. Number of Tape Drives Required: Enter the total number of drives.

L. Estimated Run Time: Enter Estimated time.

M.  Foreign Input Tapes: Enter “Y” or “N”.

N.  Xerox Printing Requirements: Enter the start key for any Xerox print tapes, which would be produced. Also required is the print orientation, paper type, etc. If this section is not needed please enter N/A. Copy this section for each unique Xerox filename.

O. Output Distribution Section: List all printed output files created by the run and where the reports are to be sent by the Output Distribution unit. Indicate if there is any special handling of the reports such as bursting, decollating, mailing by county or county and district, etc. Indicate if any special pick up of output will occur such as messenger or Vendor. If this section is not needed please enter N/A.

P. Tape Library Section: Enter any input or output tapes that must be released from the library. If this section is not need please enter N/A.

Q.  Special Instructions/Parameter updates: Enter a brief job description, any special restart instructions, and parameter update instructions, which apply. If a parameter is required and multiple fields are required, complete exhibit 30.03, Parameter Update Control Log.

Also enter in this section any tape files that will need to be available as input to this run that are not created by this job flow.

The Customer Services and Application Processing Sections may also use this field as an area to include additional operational information.

Automated Scheduling, Distribution, Tape Library System

****** SCHEDULING INFORMATION REQUIRED *****

RUN NAME - XXXXXX ACCOUNT # - 999999 QUAIFIER______

COMMON SCHEDULING PATH NAME - XXXXXXXXXXXXXXXXXXXX HOST - HSD,HSE,IKC,IKF

START KEY - ST PROD*ECL-LIB.XXXXXXXX,,,999999/XXX

FREQUENCY - DAY OF WEEK, MONTH, ECT. -

ALL STATE WORKING DAYS -

MODAY THRU FRIDAY -

STATE HOLIDAYS - Y OR N

VIA SCHMSG -

DATA BASE DATA - UPDATE ( ) RETRIEVAL ( ) NA ( )

SUBSCHEMA NAME - XXXXXXXXXXXXXX COMMON DATA BASE NAME (CIS, LIH ETC.)

ANALYST NAME ______SWITCH 23/24 SOFTWARE USED - _ Y, _ N

JOB ERROR INSTRUCTIONS - RESTART FROM BEGINNING - _ Y, _ N

NOTIFY ANALYST - _ ASAP _ NEXT WORK DAY

POSSIBLE JOB CONFLICTS -

MASS STORAGE FIXED TRACKS NEEDED -

NUMBER OF TAPE DRIVES REQUIRED -

ESTIMATED RUN TIME - ______FOREIGN INPUT TAPES _ Y, _ N

******** XEROX PRINTING REQUIREMENT - FILENAME ********

START KEY -

PAPER TYPE - _ HOLES _ NO HOLES

PRINT ORIENTATION - _ LANDSCAPE _ PORTRAIT

PRINT CHARATERISTICS - _ SIMPLEX _ DUPLEX _ QUAD

***** OUTPUT DISTRBUTION SECTION *****

REPORT NAME______REPORT NAME______

RECIPIENT ______RECIPIENT ______

ADDRESS ______ADDRESS ______

COPIES ______COPIES ______

***** TAPE LIBRARY SECTION *****

SEND OUTPUT TAPE (FILENAME) TO -

SPECIAL INSTRUCTIONS/PARAMETER UPDATES *****

Refresh Schedule:

All procedures and referenced documentation identified in this document will be subject to review and possible revision annually or upon request by the DPW Information Technology Standards Team.

Procedure Revision Log:

Change Date / Version / Change Description / Author and Organization
Unknown / 1.0 / Initial Creation / Beverly Shultz
08/12/2009 / 1.1 / Reviewed & Edited Style / Wayne Mumau

Automated Procedure Request Form.doc Page 1 of 4