Maintenance - z/XDC z2.2
Possible #XDCHOOK issues after applying PEM-1806C or later maintenance
Fix PEM-1806C introduced changes into the #XDCHOOK macro that may require you to reassemble some of your code.
The new #XDCHOOK macro changes the values for several of its reason codes. (The return codes have NOT changed. Only some reason codes have changed.)
If you have #XDCHOOK in your assemblies, and if your logic following #XDCHOOK cares about some the the reason codes that the macro sets in R0, then you will need to reassemble your code. (You won't have to change your logic, but you will have to reassemble.)
In all other respects, the new logic of hook processing will continue to accept calls created by older versions of the #XDCHOOK macro.
Applying z/XDC maintenance on zOS 2.2
To apply maintenance on zOS 2.2, APAR OA49577 must be install or the SMP/E step will fail with a S0C4.
Maintenance procedures have changed as of February 2015!
The SMPMAINT job that was available prior to February 2015 will no longer work and will generate errors if used.
A new job stream is available named MAINTJCL.
Changes to Maintenance Procedures
- The maintenance package no longer is just an FB-80 EBCDIC file. It now is a binary file containing a TERSED partitioned dataset.
- The SMPMAINT job (for APPLYing the maintenance) has been entirely redesigned, and is now named MAINTJCL. You can download a copy of MAINTJCL from our website and use that (instead of SMPMAINT) to apply z/XDC maintenance.
- MAINTJCL can be downloaded by clicking on this link. Extract MAINTJCL from the zip file and upload it to the mainframe as a simple text file. Once downloaded, proceed to download the maintenance file below.
- MAINTJCL should just run right out of the box, but you may want to customize it to conform to local standards. It contains extensive commentary to explain what it does.
Keep z/XDC Current
The z/XDC maintenance decks include fixes for reported problems as well as occasional new functionality. All maintenance decks are CUMULATIVE for each release. There's no way to download discrete fixes – you get the whole package. Additionally, if you install a brand new release of z/XDC, it will refuse to initialize unless maintenance is applied, so that you'll be sure you're using the most current update. New maintenance will be linked here as it is released, and will also be announced in our LinkedIn Users Group.
This page contains maintenance for z/XDC releases z2.2. Maintenance for z/XDC z2.1 and earlier can be found here.
Using the Maintenance Files
To find out what maintenance level your copy of z/XDC is running currently, you can start a z/XDC session ("XDCCALL IEFBR14" will do nicely), and issue the "LIST MAINTENANCE" command. z/XDC reports the maintenance level in its own format like this: "ZnX-YYMMX".
Here's how to understand that character string:
- The "ZnX" prefix describes the product level. So, "Z19" refers to z/XDC Release z1.9. "Z1D", refers to release Z1.13.
- The "YYMMX" suffix describes the two-digit year and two-digit month of the fix. The trailing "X" describes the maintenance "generation" for that month.
In the table of available maintenance below you'll see a Download to PC button, a FTP to Mainframe button, and a Text button for each release. The "Download to PC" button downloads the appropriate maintenance deck for the indicated release to your personal computer. The "FTP to Mainframe" button downloads the appropriate maintenance deck for the indicated release directly to your mainframe. The "Text" button gives you the contents of the deck, with the fix names and a one-line description of the problem addressed in each fix.
Please read the Installation Instructions before downloading and installing the maintenance files.
Installation Instructions and Checks:
Read through the following instructions before installing the maintenance files.
- MAINTJCL needs to be downloaded and customized only once. It can be reused for future maintenance updates.
- Upload MAINTJCL to the mainframe as a simple text file.
- Check the EXACT byte length of the maintenance (.tersed) file. (One way to do this is with DOS's DIR command. Another is with the ZTREE program.)
- The length of the maintenance file should be an exact multiple of 1024. If this is not the case, then something is wrong. You may have to contact us for assistance.
- The maintenance file should be uploaded as a binary file, i.e. with ASCII-to-EBCDIC translation turned OFF. Use IND$FILE, FTP, your workstation program's File Transfer Facility or whatever program you have available to perform the upload.
- The DCB attributes for the uploaded maintenance file must be RECFM=FB, LRECL=1024, BLKSIZE=n*1024
- Submit the MAINTJCL job for execution.
- For detailed instructions, View or Browse MAINTJCL. It contains extensive commentary to explain what it does.