IBM has issued a Red Alert titled: z/OS Unicode Services Conversion Information Service fails after December 15, 2015.
This Alert describes a problem with z/OS Unicode Services Conversion Information Service that will cause it to fail after December 15, 2015. This problem causes the Unicode Services conversion information service on all z/OS releases starting with z/OS 1.10 to return an incorrect return code on systems IPLed on or after December 15, 2015. This failure will affect many system services and applications such as (but not limited to) Telnet, System Automation, BCPii, ICONV sample job EDCICONV, FTP / SFTP, and Java / WebSphere.
The full text of the Red Alert can be found at the following URL:
https://www14.software.ibm.com/webapp/set2/sas/f/redAlerts/20150930.html
The following is included in this fix:
This document describes how to install the PTF fixes for Red Alert APAR OA48941 to Rational Development and Test Environment for System z ADCD z/OS distributions 1.13 and 2.1, and the PTF fixes for APAR OA48989 to Rational Development and Test Environment for System z ADCD z/OS distribution 1.12. It is strongly recommended you install the appropriate level fix for these APARs prior to December 15, 2015 to avoid any issues related to this problem. If you run multiple releases of z/OS, you will need to update each release.
You can review APAR OA48941 at the following URL:
http://www-01.ibm.com/support/docview.wss?uid=isg1OA48941
You can review APAR OA48989 at the following URL:
http://www-01.ibm.com/support/docview.wss?uid=isg1OA48989
An IPL is required to activate the fix.
Overview of Installation Steps
Overview of steps required to install the PTF fix for APAR OA48941 and APAR OA48989 on Rational Development and Test Environment for System z.
The SMP/E input data sets to install the PTF fix for APAR OA48941and APAR OA48989 are provided as tersed binary files, and must be uploaded to z/OS.
To ensure that the data sets are allocated correctly, it is advised to allocate empty data sets before uploading the data. You can use the sample file RAALLOC.jcl to allocate the data sets. The sample JCL needs the following updates:
//ALLOC PROC LLQ=,
// LRECL=,
// BLKS=,
// HLQ=<HLQ>
//ALLOC EXEC PGM=IEFBR14
//DATASET DD DSN=&HLQ..REDALERT.&LLQ,
// DISP=(NEW,CATLG),
// RECFM=FB,LRECL=&LRECL,
// DSORG=PS,BLKSIZE=&BLKS,
// UNIT=SYSALLDA,
//* VOL=SER=vvvvvv, * uncomment to specify a volser
// SPACE=(CYL,(1,1))
//EALLOC PEND
//*
//TSMPJCL EXEC ALLOC,LLQ=SMPJCL.TRS.BIN,LRECL=1024,
// BLKS=10240
//TPTF EXEC ALLOC,LLQ=TRS.BIN,LRECL=1024,
// BLKS=10240
//SMPJCL EXEC ALLOC,LLQ=SMPJCL.UNTERSE,LRECL=80,
// BLKS=800
//PTF EXEC ALLOC,LLQ=PTFS.UNTERSE,LRECL=80,
// BLKS=800
//*
Expected Return Codes and Messages: You will receive a return code of 0 if this job runs correctly.
Upload the files in binary format from the unzipped folder containing the PTF files to the z/OS data set.
In the following sample dialog, we use FTP from a Linux command line to do the transfer. The following values are assumed:
User enters: | Values |
mvsaddr | TCP/IP address or hostname of the z/OS system |
tsouid | Your TSO userid |
tsopw | Your TSO password |
/ptf_files | Temporary Linux path where the PTF files are located |
hlq | High-level qualifier you used for the data sets you allocated in the previous step |
Commands or other information entered by the user are in bold.
$ ftp mvsaddr
Connected to mvsaddr.
220-FTPD1 IBM FTP CS %version% at mvsaddr, %time% on %date%.
220 Connection will close if idle for more than 5 minutes.
User (mvsaddr:(none)): tsouid
331 Send password please.
Password: tsopw
230 tsouid is logged on. Working directory is "tsouid.".
ftp> cd ..
250 " " is the working directory name prefix.
ftp> cd hlq
250 "hlq." is the working directory name prefix.
ftp> binary
200 Representation type is Image
ftp> prompt
Interactive mode Off.
ftp> mput /ptf_files/REDALERT.*
200 Port request OK.
125 Storing data set hlq.REDALERT.SMPJCL.TRS.BIN
250 Transfer completed successfully.
2048 bytes sent in 7.8e-05 secs (26256.41 Kbytes/sec)
125 Storing data set hlq.REDALERT.TRS.BIN
250 Transfer completed successfully.
151552 bytes sent in 0.00776 secs (19542.49 Kbytes/sec)
ftp> quit
221 Quit command received. Goodbye.
The uploaded data sets are in terse format and must be untersed in order to work with them.
You can use the sample file UNTERSE.jcl to unterse the data sets. The sample JCL needs the following updates:
//UNTERSE PROC IN=,
// OUT=,
// HLQ=<HLQ>
//UNTERSE EXEC PGM=TRSMAIN,PARM=UNPACK
//SYSPRINT DD SYSOUT=*
//INFILE DD DSN=&HLQ..&IN,
// DISP=SHR
//OUTFILE DD DSN=&HLQ..&OUT,
// DISP=SHR
//EUNTERSE PEND
//*
//SMPJCL EXEC UNTERSE,IN=REDALERT.SMPJCL.TRS.BIN,
// OUT=REDALERT.SMPJCL.UNTERSE
//PTF EXEC UNTERSE,IN=REDALERT.TRS.BIN,
// OUT=REDALERT.PTFS.UNTERSE
//*
The untersed SMPJCL dataset is an unloaded partitioned dataset in TSO TRANSMIT format and must be expanded with the TSO RECEIVE command to become usable. hlq Specifies the high level qualifier you used for the data sets you allocated in the previous step.
RECEIVE INDA('hlq.REDALERT.SMPJCL.UNTERSE')
When prompted on the TSO RECEIVE commands, use the appropriate DSNAME:
DS('hlq.REDALERT.SMPJCL')
Edit and submit sample job SMPRECVR to perform the SMP/E RECEIVE for the PTF fixes for APARs OA48941 and APAR OA48989. Consult the instructions in the sample job for more information.
The XXSYS1 volumes are typically acceptable system work volumes for an ADCD z/OS distribution. The following is a list of the XXSYS1 volumes that correspond to an ADCD z/OS Distribution.
Expected Return Codes and Messages: You will receive a return code of 0 if this job runs correctly.
Expected Return Codes and Messages from APPLY CHECK: You will receive a return code of 0 if this job runs correctly.
Expected Return Codes and Messages from APPLY: You will receive a return code of 0 if this job runs correctly.
Perform a cold start IPL (specifying CLPA) to complete the installation of the fix.