Open Object Rexx

The ooRexx compatible with Rexx it can run normal Rexx programs, you can get ooRexx via the Open Object Rexx website of Download Page.

How to collect CICS troubleshooting data

As subject for CICS problem determination on z/OS refer to this link.

IBM z/OS V2R3 documentation

Where you can find information about how to install, maintain, and use IBM z/OS

Data set encryption for z/OS V2.2

The describes data set encryption for z/OS V2.2 the information refer to IBM Techdocs.

Using IBM Installation Manager on z/OS

IBM Installation Manager is a tool for installing and maintaining computer software on a wide range of platforms. This document provides information on planning and using Installation Manager on z/OS it was written by IBM's Jeff Mierzejewski, and you can find it on IBM Techdocs Library website.

Get z/OS Basic System Information from REXX

How to display basic mainframe processor and z/OS system information from a REXX, the REXX source code refer to this link.

COBOL access to MVS Control Blocks

Accessing MVS control blocks from a COBOL program. The following sample program shows how you can access the job, step, and program names for the currently running program. MVS Control Blocks:

File Manager for z/OS Remote Services

File Manager has been enhanced in order to provide remote services for the following types of resource: - QSAM, VSAM, PDS or PDSE including load libraries - CICS files - File Manager templates in read access The more information refer to IBM website

Dynamically deallocate a file from CICS

Use the ADYN transaction to dynamically deallocate a file from CICS while CICS is up. ADYN is documented to in the CICS TS information center under the dynamic allocation sample program.

CICS Maintenance methodology

Example Step by Step CICS Maintenance Procedure. 1. After installation of a new release, and having already created DFHCSVC in hlq.CICS.TEST.DFHCSVC.SDFHLPA.NEW (VERY IMPORTANT!!!!!), run the CICSSVC3 job to rename the Target version of DFHCSVC to SVCMAINT. 2. RECEIVE a new level of maintenance or a set of PTFs. 3. Research any HOLDs, especially ACTIONS. 4. APPLY the maintenance. Research and resolve any problems. 5. Take the Test LPAR down. 6. Run job TSTCLONE to rename the current TEST versions of SDFHLPA SDFHLINK, SDFHAUTH, SDFHLOAD, and SEYULINK to .OLD, and copy the Target versions of the same data sets to hlq.CICS.TEST.*. (verify the hlq for the Target data sets is correct in TSTCLONE). Rename hlq.CICS.TEST.DFHCSVC.SDFHLPA to hlq.CICS.TEST.DFHCSVC.SDFHLPA.OLD, then rename hlq.CICS.TEST.DFHCSVC.SDFHLPA.NEW to hlq.CICS.TEST.DFHCSVC.SDFHLPA 7. IPL the Test LPAR. 8. Change CICSSVC=216 to CICSSVC=217 in the SIT, in hlq.CICS.TEST.SYSIN (in whatever member is the active member), or on the EXEC statement. 9. Bring up the Test CICS system on the Test LPAR, verify it comes up OK, test CEMT, CEDA etc., and in general, test as much as possible. 10. Take the Production LPAR down. 11. If it does not exist, create hlq.CICS.PROD.DFHCSVC.SDFHLPA and copy the production MAINTSVC into it as DFHCSVC. Make the necessary PARMLIB updates. 12. Copy MAINTSVC from hlq.CICS.TEST.SDFHLPA to hlq.CICS.PROD.SDFHLPA after renaming the existing MAINTSVC to MAINTSVO in hlq.CICS.PROD.SDFHLPA. 13. IPL the Production LPAR. 14. Add hlq.CICS.TEST.SDFHLPA and hlq.CICS.TEST.SDFHLINK to the STEPLIB for the Test CICS system if that has not already been done. 15. Bring up the Test CICS system on the Production LPAR and perform rudimentary testing. 16. Change CICSSVC=216 to CICSSVC=217 in hlq.CICS.DEVL.SYSIN, in whatever member is the active member. 17. Add hlq.CICS.TEST.SDFHLPA and hlq.CICS.TEST.SDFHLINK to the STEPLIB for the Development CICS system. Change the DD for SDFHAUTH in STEPLIB from hlq.CICS.PROD.SDFHAUTH to hlq.CICS.TEST.SDFHAUTH. Change the DD for SDFHLOAD in DFHRPL from hlq.CICS.PROD.SDFHLOAD to hlq.CICS.TEST.SDFHLOAD. 18. Bring up the Development CICS system on the Production LPAR. Let it run there for several days. 19. Take the Test LPAR down. 20. Rename DFHCSVC to DFHCSVCO in hlq.CICS.TEST.SDFHLPA, then copy MAINTSVC to DFHCSVC in hlq.CICS.TEST.SDFHLPA. 21. IPL the Test LPAR. 22. Change CICSSVC=217 to CICSSVC=216 in the SIT, in hlq.CICS.TEST.SYSIN, or via the EXEC statement. 23. Bring up the Test CICS system on the Test LPAR, verify it comes up OK, test CEMT, CEDA etc., to test as much as possible. 24. Take the Production LPAR down. 25. Run job PRDCLONE to rename the current PROD versions of SDFHLPA SDFHLINK, SDFHAUTH, SDFHLOAD and SEYULINK to .OLD, and copy the TEST versions of the same data sets to hlq.CICS.PROD.*. 26. IPL the Production LPAR. 27. When the Production CICS system is up, it will be using the new maintenance, so do some testing. 28. If problems arise: a. Take the Production LPAR down. b. Run job PRDBACK on the Production LPAR. This job will clear the hlq.CICS.PROD.* data sets, and copy the contents of hlq.CICS.PROD.*.OLD into them. c. IPL the Production LPAR, which will bring the Production CICS system up without the maintenance. 29. When the maintenance problem is resolved and has been tested on the Test LPAR using the Test CICS system, then on the Production LPAR with the Test CICS system and the Development CICS system, repeat steps 23 through 26 to retry it with the Production CICS system. 30. omment hlq.CICS.TEST.SDFHLPA and hlq.CICS.TEST.SDFHLINK out of STEPLIB in the Test CICS system. 31. Comment hlq.CICS.TEST.SDFHLPA and hlq.CICS.TEST.SDFHLINK out of STEPLIB in the Development CICS system. Leave CICSSVC=217 in hlq.CICS.DEVL.SYSIN.

z/OS data set encryption

z/OS data set encryption the detail real implementation and customization information refer to IBM Techdocs document.