This document covers the following topics:
Can I get every source fix (INPLs, IUPDs, etc.) for a particular product in one downloadable module?
My operating system does not have a TCP/IP stack. What else can I use?
How do I prepare a mainframe PDS or other variable-blocked file for FTP?
How can I obtain all Zaps for a specific product version easily?
Why are source fixes encoded which require decoding before they can be applied to the mainframe?
The decoder gives me an error when I try to decode a fix data set on the mainframe. What can I do?
Use the Knowledge Center or the Fix Explorer.
No. The size of such a module would be prohibitive for downloading. All source fixes are available for download from Empower one fix at a time.
Move the fix from the PC to your mainframe using of your own utility. Software AG recommends native FTP for this process.
For further details, see General Support Info > Diagnostic Information in the navigation bar on the left.
There are TCP/IP stack add-on products available from other vendors for a fee. Software AG also offers additional products that will accomplish this task, such as Com-plete, Natural for ISPF and Entire Connection. CICS utilities (UPLOAD) may also work.
For further details, see General Support Info > Diagnostic Information in the navigation bar on the left.
Product fixes are loaded into Empower on a daily basis.
All fixes created after January 01, 1997 are accessible on Empower. If you need a correction that does not appear in Empower but refers to a product maintenance level that is still officially supported, contact your customer support or submit a support request.
For details, see General Support Info > Diagnostic Information in the navigation bar on the left.
The required Zap or source change can be downloaded by choosing the download button. Your browser will do the actual download to your PC and will ask you where on your PC's hard disk to save the data set.
For further details, see General Support Info > Diagnostic Information in the navigation bar on the left.
Typically this problem occurs when a user's firewall restricts the user from being assigned to a specific port number. Empower needs to assign you to a specific port to display or download a fix. Check with your network people to find out if your firewall restricts the assignment of port numbers.
This error occurs when Empower thinks it has detected an illegal attempt to gain access to a fix. Empower checks where you came from and how you accessed it prior to allowing fixes to be given. If you are using a bookmark to access Empower, check to be sure the path is correct.
This message is issued by your browser and is due to the file extensions that we have given our fixes. We depend upon your browser to handle the actual download and what your browser is telling you is that it does not have a helper application defined to handle a file with this type of extension. This is by design and is normal. Your browser should provide you with various options, one of which will instruct your browser to save the file on your PC's hard disk.
This is a browser problem and no Empower error. It occurs with some older versions of the Microsoft Internet Explorer. If you experience this problem, update your browser to a newer version.
If a minimum of 20 Zaps exists per product version/release/SM, Zap combinations are provided upon request.
The Zap combinations for a specific product version/release/SM are combined in a single solution data set. You can search for and download all available Zaps in one step instead of handling each Zap separately.
In the Knowledge Center, go to All Fixes. Choose the product and then see the entry for the correction type "all zaps".
Mainframe source data fixes are encoded and must be decoded prior to being applied. To decode the fix, you will need the Software AG decoder.
You can find the z/OS version here: Loading Binary Host Files to z/OS.
The decoder must be installed on the mainframe and the encoded fix should be moved from the PC to the mainframe prior to decoding. We recommend using native FTP (available as freeware or shareware) to move the fix. The source fix should then be decoded using the Software AG decoder and then applied (for example, via INPL).
Some mainframe corrections must be provided in a coded and compressed format to guarantee correct data set transformation, decrease the data set size and enable installation via SMA (MF System Maintenance Aid).
Mainframe source data fixes are encoded because of blocking factors. All mainframe Software AG source fixes are variable-blocked, which a PC will not tolerate. Zaps, on the other hand, are fixed-block and do not have this problem. Mainframe source fixes must be encoded so that their blocking factors are not lost by the PC. Move the encoded source fix from your PC to the mainframe prior to decoding it. We recommend using native FTP (available as freeware or shareware) to move the encoded data set to the mainframe.
For further details, see General Support Info > Diagnostic Information in the navigation bar on the left.
z/OS and BS2000/OSD users can download the decoder here:
z/VSE and CMS for z/VM users should submit a Support Request asking that the appropriate decoder be sent to them on tape.
In urgent situations, please contact your customer support.
First, please see the section SNTDECOD Error Messages as it contains the most common errors and their resolution. If this section does not resolve your problem, submit a support request or call your customer support.
Choose the product group for the fix that you are applying (If you are working with an Adabas fix, choose "data management", if you are applying a Natural fix choose "application engineering", etc.).
Coded and compressed corrections must be converted prior to being
uploaded and applied to the mainframe. To decode/decompress the correction,
please apply the Empower SNTDECOD software.
See the following sections: