Maintenance - z/XDC z2.2
09/15/18 -- !!!IMPORTANT!!! MAINTENANCE PROCEDURES HAVE CHANGED DRASTICALLY!!!
Beginning with Maintenance Update DBC-1809C, we have changed the way we internally managed maintenance, and that necessitates significant changes, going forward, to the way you must install new maintenance.
Here are the details:
- The maintenance install job has a new name (MAINTJOB) and has been *COMPLETELY* redesigned. For one thing, SMP IS NO LONGER USED!
- Maintenance is still cumulative, so to apply all maintenance, it remains the case that you only need the newest Maintenance Package.
- Previously, maintenance level information was created at install time, but now it is created at assmbly time. This means that basically *ALL* OF z/XDC'S LOAD MODULES ARE CHANGED BY *EVERY* MAINTENANCE UPDATE regardless of whether or not the update would otherwise affect them.
- In particular, this means that after every maintenance, you will have to reload the XDC and XDC31 modules into the DLPA.
- Also you will have to bounce the XDCSRVER job!
- Bring it down before you apply the maintenance
- And bring it back up when you are done.
You must download the new MAINTJOB.
06/26/18 -- 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.
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: "fml-yymmx".
Here's how to understand that character string:
- The "fml" prefix is the initials of the author of the maintenance deck.
- 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, a Readme and a Maintenance Info 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 "Readme" button gives you the fix names and a one-line description of the problem addressed in each fix, along with detailed installation instructions as well as any maintenance specific instructions.
- The "Maintenance Info" button gives you a file with complete descriptions for each piece of maintenance.
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.
- MAINTJOB needs to be downloaded and customized only once. It can be reused for future maintenance updates.
- Unzip the downloaded package.
- Upload MAINTJOB 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
- Edit the MAINTJOB job to fit your installation requirements. You will typically do this just once unless MAINTJOB has been updated.
- Submit the MAINTJOB job for execution.
- For detailed instructions, View or Browse MAINTJCL. It contains extensive commentary to explain what it does.