Program Implementation Form Instructions

COMMONWEALTH OF PENNSYLVANIA DEPARTMENT OF HUMAN SERVICES, INSURANCE & AGING INFORMATION TECHNOLOGY PROCEDURE

Name Of Procedure: Program Number: Implementation Form Instructions PRO-EASS003 Domain: Category: Application Mainframe Date Issued: Issued By: 11/01/2007 Date Revised: DHS Bureau of Information Systems 09/30/2015

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 ID Enter the program or run name.

2. DATE PREPARED/REVISED Enter 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. SYSTEM Enter the system name.

6. PROCESS Enter the process name.

Program Implementation Form Instructions Page 1 of 4 7. SUBSYSTEM Enter the subsystem name.

8. ACCOUNT CODE Enter the account code.

9. REVISION # Enter the revision number assigned.

10. Purpose/Revision Describe reason for revision. Include Narrative sufficient 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/DMS Indicate whether the program is RDMS or DMS

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

13. Mode Indicate whether the program is Batch or Tip.

14. Function Indicate whether the program is Update or Retrieval.

15. System Enter name of system.

16. Schema Enter DMS schema and/or RDMS schema used in program.

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

18. Run ID Enter program run ID.

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

20. Site Enter the HOST ID on which the Program will run.

21. Element Transfer Check this block to indicate that an Element Request Transfer REQUEST Request (ETR) is attached.

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

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

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

Program Implementation Form Instructions Page 2 of 4 25. Standalone ECL Check this block to indicate that a Standalone ECL listing with a PRT,S, PRT,TL and a DOWN are attached.

26. Standard ECL Check this block to indicate that a Standard ECL listing with a PRT,S and a PRT,TL are attached.

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

28. Type Check the appropriate box to indicate if the program is Online, Batch, etc.

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

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

*31. Developer/Date Signature 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 Assurance Signature of QA representative who reviewed Analyst the 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.

Program Implementation Form Instructions Page 3 of 4 Procedure Revision Log:

Change Version Change Description Author and Organization Date 11/01/2007 1.0 Initial Creation Virjean Dauksha 06/28/2010 1.0 Reviewed Virjean Dauksha 10/27/2010 1.1 Added implementation date Virjean Dauksha 03/17/2011 1.2 Updated content Virjean Dauksha 11/04/15 1.3 Name change from DPW to DHS Virjean Dauksha

Program Implementation Form Instructions Page 4 of 4