The fix is shipped as file IBM.HHOP760.UK53000
The following fixes are prerequisites for this fix:
Steps required to install the fix:
A sequential data set must be allocated on the z/OS system to receive the fix that you will upload from your workstation. You can do this by submitting the job below. Add a job card and modify the parameters to meet your site's requirements before submitting.
//ALLOC EXEC PGM=IEFBR14 //* //UK53000 DD DSN=hlq.IBM.HHOP760.UK53000, // DISP=(NEW,CATLG,DELETE), // DSORG=PS, // RECFM=FB, // LRECL=80, // UNIT=SYSALLDA, //* VOL=SER=volser, //* BLKSIZE=6160, // SPACE=(TRK,(78,10)) //*
Upload the file in binary format from your workstation to the z/OS data set. On a Windows system, you can use FTP from a command prompt to upload the file. In the sample dialog shown below, commands or other information entered by the user are in bold, and the following values are assumed:
| User enters: | Values |
|---|---|
| mvsaddr | TC P/IP address of the z/OS system |
| tsouid | Your TSO user ID |
| tsopw | Your TSO password |
| d: | Your drive containing the fix files |
| hlq | High-level qualifier that you used for the data set that you allocated in the job above |
C:\>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 60 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> put d:\IBM.HHOP760.UK53000 200 Port request OK. 125 Storing data set hlq.IBM.HHOP760.UK53000 250 Transfer completed successfully 4336640 bytes sent in 0.28 seconds ftp> quit 221 Quit command received. Goodbye.
++HOLD(UK53000) SYS FMID(HHOP760) REASON(ACTION) DATE(09351)
COMMENT
(****************************************************************
* Affected function: JES Job Monitor *
****************************************************************
* Description: incorrect time values *
****************************************************************
* Timing: post-APPLY *
****************************************************************
* Part: SFEKSAMP(FEJJJCL) *
****************************************************************
When using the _CEE_ENVFILE keyword to define environment
variables, LE pads these variables with blanks. This padding can
cause LE to ignore the settings of the TZ variable, in which
case it uses the GMT timezone.
LE provided a fix (z/OS 1.8 and higher) in the form of the
_CEE_ENVFILE_S keyword. Here no padding takes place, and the TZ
environment variable is interpreted correctly.
If need be, the _CEE_ENVFILE_S keyword can be used (instead of
_CEE_ENVFILE) in the startup JCL, as shown in the updated sample
JCL, FEK.SFEKSAMP(FEJJJCL).
//*
//* JES JOB MONITOR
//*
//JMON PROC PRM=, * PRM='-TV' TO START TRACING
// LEPRM='RPTOPTS(ON)',
// HLQ=FEK,
// CFG=FEK.#CUST.PARMLIB(FEJJCNFG)
//*
//JMON EXEC PGM=FEJJMON,REGION=0M,TIME=NOLIMIT,
// PARM=('&LEPRM,ENVAR("_CEE_ENVFILE_S=DD:ENVIRON")/&PRM')
//STEPLIB DD DISP=SHR,DSN=&HLQ..SFEKAUTH
//ENVIRON DD DISP=SHR,DSN=&CFG
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
// PEND
//*
****************************************************************
* Affected function: RSE *
****************************************************************
* Description: new variables *
****************************************************************
* Timing: post-APPLY *
****************************************************************
* Part: /etc/rdz/rsed.envvars *
* /usr/lpp/rdz/samples/rsed.envvars *
****************************************************************
This fix updates the sample rsed.envvars by adding the
following optional directives:
#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dprocess.cleanup.interval=600"
Automatically remove RSE thread pools that are in an
unrecoverable error state. By default, erroneous RSE thread
pools are not automatically removed. Uncomment and customize
to automatically remove erroneous RSE thread pool servers at
every interval (interval unit is seconds). Specifying 0
disables the function.
#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Ddeny.nonzero.port=true"
Disallow the client to choose the communication port number.
The default is false. Uncomment and specify true to refuse
connections where the client specifies which host port must
be used by RSE server for the connection.
Note:
The port number used by the RSE server is determined in the
following order:
1. If a nonzero port number is specified in the subsystem
properties on the client, then the specified port number
is used. If the port is not available connect will fail.
This setup is not recommended.
Note:
The host can deny this type of connection request by
specifying the deny.nonzero.port=true directive in
rsed.envvars.
2. If the port number in the subsystem properties is 0, and
if _RSE_PORTRANGE is specified in rsed.envvars, then the
port range specified by _RSE_PORTRANGE is used. If no port
in the range is available, connect will fail.
3. If the port number in the subsystem properties is 0, and
_RSE_PORTRANGE is not specified in rsed.envvars, then any
available port is used.
#_RSE_JAVAOPTS="$_RSE_JAVAOPTS -Dsingle.logon=false"
Allow a user ID to log on multiple times. The default is
false. Uncomment and specify true to allow a user ID to log
on multiple times to a single RSE daemon.
Note:
A second logon attept will cause the first one to be
cancelled by the host if this directive is not active and set
to false. This cancel will be accompanied by console message
FEK210I.
Add these directives to your active rsed.envvars (by default
located in /etc/rdz) if you want to use them.
****************************************************************
* Affected function: console message *
****************************************************************
* Description: new message, FEK210I *
****************************************************************
* Timing: n/a *
****************************************************************
* Part: n/a *
****************************************************************
This fix introduces a new console message.
FEK210I = {0} canceled owing to duplicate logon
The message is issued when the host cancels an existing session
because of a new logon request for that user ID.).
SMP/E RECEIVE and APPLY the fix.