Program Implementation Form Instructions

COMMONWEALTH OF PENNSYLVANIA

DEPARTMENT OF HUMANSERVICES, INSURANCE & AGING

INFORMATION TECHNOLOGY PROCEDURE

Application

Mainframe

11/01/2007

DHS Bureau of Information Systems

General:

The Program Implementation form must be completed and submitted with a mainframe implementation package when a COBOL program has been changed or a standalone ECL has been changed. A standalone ECL is an ECL that does NOT contain an execute (XQT) statement.

The purpose of this document is to aide developers in completing the Program Implementation form.

Procedure:

Implementation Instructions

ITEM ACTION

1. PROG/RUN IDEnter the program or run name.

2. DATE PREPARED/REVISEDEnter the date the Program Implementation Form is completed.

3. TFS TASK#/BUNDLE#Enter the task number and/or the Bundle number.

4. DEVELOPER Enter the name of the developer who prepared the original version of this page or the latest revision.

5. SYSTEMEnter the system name.

6. PROCESSEnter the process name.

7. SUBSYSTEMEnter the subsystem name.

8. ACCOUNT CODEEnter the account code.

9. REVISION #Enter the revision number assigned.

10. Purpose/RevisionDescribe reason for revision. Include

Narrativesufficient background information explaining the change being made. For program fixes, also include explanation of problem being corrected.

NOTE: Items 11 through 20 Data Base Registration, are only to be completed for a new program or when any of the items needs to be changed.

11. RDMS/DMSIndicate whether the program is RDMS or DMS

12. Implementation DateIndicate the date that this will be implemented into production.

13. ModeIndicate whether the program is Batch or Tip.

14. FunctionIndicate whether the program is Update or Retrieval.

15. SystemEnter name of system.

16. SchemaEnter DMS schema and/or RDMS schema used in program.

17. Sub/SchemaEnter DMS subschema and/or RDMS subschema used in program.

18. Run IDEnter program run ID.

19. Account #Enter the account number under which the program will run.

20. SiteEnter the HOST ID on which the Program will run.

21. Element Transfer Check this block to indicate that an Element

RequestTransfer REQUEST Request (ETR) is attached.

22. Program SpecificationCheck this block to indicate that the program specification and/or revision document is attached.

23. Short ListingCheck this block to indicate that a Short Compile, Short MAP and DOWN listing is attached.

24. Full ListingCheck this block to indicate that a Full Compile, Short MAP and DOWN listing is attached.

25. Standalone ECLCheck this block to indicate that a Standalone

ECL listing with a PRT,S, PRT,TL and a DOWN are attached.

26. Standard ECLCheck this block to indicate that a Standard

ECL listing with a PRT,S and a PRT,TL are attached.

27. OtherCheck this block to indicate that some other type of special instructions are attached. Complete the OTHER line.

28. TypeCheck the appropriate box to indicate if the

program is Online, Batch, etc.

29. ApplicationCheck the appropriate box to indicate if the program is Production, Utility etc.

30. ComplexityCheck the appropriate box to indicate if the revision is of Low, Medium or High complexity.

*31. Developer/DateSignature of the developer indicating that this program submission has been developed and meets the standards and procedures as defined in the Detail Program Design Procedures, the Software Development Procedures, the Implementation Procedures, and the Data Processing Standards Manual. Enter the date the checklist is completed by the developer.

*32. Project Leader/Date Signature of the project leader indicating that this program submission has been developed and meets the standards and procedures as defined in the Detail Program Design Procedures, the Software Development Procedures, the Implementation Procedures, and the Data Processing Standards Manual. Enter the date the checklist is completed by the project leader.

33. Quality AssuranceSignature of QA representative who reviewed

Analystthe implementation package. Enter the date the QA representative completes the review of the implementation package.

*NOTE: If the Project Leader and the Developer is the same person, only item 32 needs to be completed

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 DHS Information Technology Standards Team.

Procedure Revision Log:

Program Implementation Form InstructionsPage 1 of 4