I have searched and cannot find my test fix.
Test fixes are not generally available so you cannot search for them. Since they are in test status, they are only given to specific customers who have the problem. They are attached specifically only to your case.
In SupportOnline (http://support.ca.com), you must view your open issue first in order to download test fixes.
When you are viewing your open issue, select the 'Summary' tab. At the bottom of the issue summary window, you will see the link for the attached test fix.
Click on the APAR number.
On the next screen, scroll down and click on Download and then save.
If you are downloading a cart, it will come down in zipped format. Unzip the file and then proceed with the following instructions.
For .bin files:
Transfer the file from your PC to the mainframe as binary into a file of LRECL 80 and FIXED format. Once the apar is uploaded to your mainframe, you must "RECEIVE" the file into a PDS. Here is sample JCL that you can modify for your installation:
//RECVSTEP EXEC PGM=IKJEFT01,REGION=2M
//*STEPLIB DD DSN=SYS2.LINKLIB,DISP=SHR
//SYSUDUMP DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
DATASET('new.pds.dataset.name') RESTORE NEW -
SPACE(2,2) RELEASE CYLINDERS -
Important: NEVER receive a file into an existing file. Always allocate a new load library for the load module you are about to receive. Differences in blocksize can cause PDS corruption during a receive.
For text files:
ASCII text solutions should be transferred to the mainframe using the "ASCII" or "CRLF" parameters. (CRLF means carriage return - line feed). This will cause the solution text to be translated to EBCDIC and will retain the original LRECL 80 format.
If you are having difficulty getting the mainframe file in a fixed format, or the text is 'wrapping', try pre-allocating the file on the mainframe, and then upload the file into it.
NOTE: The FTP process puts a final carriage- return/line-feed at the end of the file. This will result in a blank line at the end of the solution. You will need to remove this blank line before running your SMP job to avoid SMP errors.