Roll Server Messages
This section lists the messages that may be issued by the Natural Roll Server. Unlike
Natural system messages, the explanatory long texts to these messages and codes are only
available in this document, not online.
For information on the Roll Server, see:
In addition, refer to the relevant IBM documents mentioned below.
Overview of Messages
RSM0001 | RSM0002 | RSM0003 | RSM0004 | RSM0005 | RSM0006 | RSM0007 | RSM0008 | RSM0009 | RSM0010 | RSM0011 | RSM0012 | RSM0013 | RSM0014 | RSM0015 | RSM0017 | RSM0018 | RSM0019 | RSM0020 | RSM0021 | RSM0022 | RSM0023 | RSM0026 | RSM0027 | RSM0029 | RSM0030 | RSM0031 | RSM0032 | RSM0033 | RSM0036 | RSM0037 | RSM0038 | RSM0039 | RSM0040 | RSM0041 | RSM0042 | RSM0043 | RSM0044 | RSM0045 | RSM0046 | RSM0047 | RSM0048 | RSM0049 | RSM0050 | RSM0051 | RSM0052 | RSM0053 | RSM0054 | RSM0055 | RSM0056 | RSM0057 | RSM0058 | RSM0059 | RSM0060 | RSM0061 | RSM0062 | RSM0063 | RSM0064 | RSM0065 | RSM0066 | RSM0067 | RSM0068 | RSM0069 | RSM0070 | RSM0072 | RSM0073 | RSM0074 | RSM0075 | RSM0076 | RSM0077 | RSM0078 | RSM0081 | RSM0082 | RSM0083 | RSM0084 | RSM0085 | RSM0086 | RSM0087 | RSM0088 | RSM0089 | RSM0090 | RSM0091 | RSM0092 | RSM0093 | RSM0094 | RSM0095 | RSM0099 | RSM0119 | RSM0120-1 | RSM0120-2 | RSM0131 | RSM0133 | RSM0190-1 | RSM0190-2 | RSM0313-1 | RSM0313-2 | RSM0313-3 | RSM0451 | RSM0452 | RSM0453 | RSM0454 | RSM0455 | RSM0456 | RSM0457 | RSM0458 | RSM0459 | RSM0460 | RSM0461 | RSM0462 | RSM0500 | RSM0501 | RSM0502 | RSM0503 | RSM0504 | RSM0505 | RSM0506 | RSM0507 | RSM0508 | RSM0509 | RSM0510 | RSM0522 | RSM0523 | RSM0524 | RSM0551 | RSM0700 | RSM0701 | RSM0702 | RSM0703 | RSM0704 | RSM0705 | RSM0706 | RSM0707 | RSM0708 | RSM0709 | RSM0710 | RSM0711 | RSM0712 | RSM0713 | RSM0714 | RSM0715 | RSM0716 | RSM0717 | RSM0718 | RSM0719 | RSM0720
RSM0001 - Subsystem ID invalid
| Explanation |
A subsystem ID was specified that is longer than 4 characters. |
| Action |
Specify a subsystem ID of 1 to 4 characters. |
RSM0002 - Roll file number not numeric
| Explanation |
The second parameter is not a number. |
| Action |
Specify a valid number. |
RSM0003 - Invalid number of roll files
| Explanation |
A number greater than 5 was specified. |
| Action |
Specify a number between 0 and 5. |
RSM0004 - Number of LRB slots not specified
| Explanation |
The third parameter was omitted. |
| Action |
This is a mandatory parameter. Specify a valid number. |
RSM0005 - Number of LRB slots not numeric
| Explanation |
The third parameter is not a number. |
| Action |
Specify a valid number. |
RSM0006 - Number of LRB slots > 32767
| Explanation |
The number of LRB slots specified is too large. |
| Action |
Specify a maximum of 32767 LRB slots. |
RSM0007 - Invalid CF structure name
| Explanation |
A structure name of more than 16 characters was specified. |
| Action |
Specify a structure name of 16 characters or less. |
RSM0008 - Bad return code from IEANTRT: rc
| Explanation |
The Name/Token Service returned return code rc.
|
| Action |
See the current IBM MVS Programming: Authorized Assembler
Services Reference manual for information about the return code
from the IEANTRT request.
|
RSM0009 - DCB buffer could not be obtained. Reason:
reasoncode
| Explanation |
A STORAGE OBTAIN request failed with
reasoncode.
|
| Action |
Increase virtual storage available to the Roll Server.
(REGION option of the JCL EXEC statement.)
|
RSM0010 - OPEN failed for DDNAME: ddname
| Explanation |
The roll file specified under DDNAME
ddname could not be opened.
|
| Action |
Specify a valid roll file DSN. |
RSM0011 - Duplicate roll file DSN
| Explanation |
The same DSN was specified for two roll file DDNAMEs.
|
| Action |
Specify unique DSNs for each roll file. |
RSM0012 - Temp roll file buffer could not be obtained. Reason:
reasoncode
| Explanation |
A STORAGE OBTAIN request failed with
reasoncode.
|
| Action |
Increase virtual storage available to the Roll Server.
(REGION option of the JCL EXEC statement.)
|
RSM0013 - RF directory buffer could not be obtained. Reason:
reasoncode
| Explanation |
A STORAGE OBTAIN request failed with
reasoncode.
|
| Action |
Increase virtual storage available to the Roll Server.
(REGION option of the JCL EXEC statement.)
|
RSM0014 - LRB directory could not be obtained. Reason:
reasoncode
| Explanation |
A STORAGE OBTAIN request failed with
reasoncode.
|
| Action |
Increase virtual storage available to the Roll Server.
(REGION option of the JCL EXEC statement.)
|
RSM0015 - Unrecognized parameter or invalid value in parameter file
| Explanation |
An unknown keyword or invalid parameter value was found in the parameter
file.
|
| Action |
Correct the parameter file. |
RSM0017 - Size for LRB > 524287 blocks
| Explanation |
The number of LRB slots times LRB slot size exceeds 2 Gigabytes. |
| Action |
Specify fewer LRB slots or a smaller slot size. |
RSM0018 - LX table could not be obtained. Reason:
reasoncode
| Explanation |
A STORAGE OBTAIN request failed with
reasoncode.
|
| Action |
Increase virtual storage available to the Roll Server.
(REGION option of the JCL EXEC statement.)
|
RSM0019 - Roll Server Version vrs is active
Where vrs represents the relevant product version (see also
Version in the Glossary).
| Explanation |
The Roll Server initialized successfully and is ready for work. |
| Action |
None. |
RSM0020 - Subtask terminated: taskname
rc
| Explanation |
The subtask indicated by taskname
has terminated. If the return code is not zero, it is indicated as
rc.
|
| Action |
If a nonzero rc is reported,
Contact support.
|
RSM0021 - Subtask termination initiated
| Explanation |
In response to a TERM or
DEAL operator command, the Roll Server has started
to terminate its subtasks.
|
| Action |
None. |
RSM0022 - All subtasks terminated
| Explanation |
In response to a TERM or
DEAL operator command, the process of terminating
the subtasks is finished.
|
| Action |
None. |
RSM0023 - Other than MODIFY or STOP command received
| Explanation |
The Roll Server received a CIBVERB other than
MODIFY or STOP.
|
| Action |
Contact support. |
RSM0026 - Command allowed in active state only: command
| Explanation |
In deallocated (DEAL) state, the Roll Server cannot accept
operator command command.
|
| Action |
Issue the START operator command, then repeat
the rejected command.
|
RSM0027 - Unknown command command
| Explanation |
An invalid operator command was issued to the Roll Server. |
| Action |
Check for typing error and correct. |
RSM0029 - Recursive abend in maintask. Now waiting for CANCEL command
| Explanation |
An abend occurred during abend recovery. |
| Action |
Cancel the Roll Server started task and Contact support. |
RSM0030 - Low Water Mark not numeric or invalid
| Explanation |
The sixth parameter is not a number or exceeds 10. |
| Action |
Specify a low water mark between 0 and 10. |
RSM0031 - High Water Mark not numeric or invalid
| Explanation |
The seventh parameter is not a number or exceeds 10. |
| Action |
Specify a high water mark between 0 and 10. |
RSM0032 - Too few/many parameters for command
| Explanation |
The number of parameters is not the one that has been expected. |
| Action |
Correct the number of parameters. |
RSM0033 - All resources deallocated
| Explanation |
In response to a DEAL (deallocate) operator
command, the Roll Server is now in deallocated state.
|
| Action |
None. |
RSM0036 - DUMP successful for roll file n
| Explanation |
Slots from the Local Roll Buffer and the Roll File Directory were
successfully written to Roll File n on disk.
|
| Action |
None. |
RSM0037 - DUMP failed for roll file n
| Explanation |
The Roll Server was unable to write slots and directory to Roll File
n.
|
| Action |
Look for accompanying messages indicating the error situation that
prevented a successful dump.
|
RSM0038 - SNAP failed. Task RB could not be obtained
| Explanation |
A STORAGE OBTAIN request failed.
|
| Action |
Increase virtual storage available to the Roll Server.
(REGION option of the JCL EXEC statement.)
|
RSM0039 - XES functions not available
| Explanation |
Environmental error. XES functions are not available. This can occur
because the coupling facility hardware necessary to provide XES functions is not
present.
|
| Action |
Re-IPL the system or contact IBM. |
RSM0040 - IXLCONN unsuccessful. Reason code: reasoncode
| Explanation |
A connection to the Coupling Facility structure specified as fifth
parameter could not be established.
|
| Action |
Determine the meaning of the reason code in the IBM document
z/OS Programming: Sysplex Services Reference and
follow the indicated action.
|
RSM0041 - CF initialization successful for list: n
| Explanation |
The Roll File Directory for Roll File n was
established in the list structure specified as fifth parameter.
|
| Action |
None. |
RSM0042 - CF initialization failed for list/RSN code:
reasoncode
| Explanation |
The Roll File Directory for Roll File
n could not be established in the list structure
specified as fifth parameter.
The reason codes are as follows:
|
12
|
STORAGE OBTAIN failed.
|
16
|
An abend occurred during initialization. |
20
|
The Structure is allocated too small to hold the Roll File Directory.
|
24
|
Structure failure or connectivity lost. |
| Action |
For Reason Code 12: |
Increase virtual storage available to the Roll Server.
(REGION option of the JCL EXEC statement.)
|
| For Reason Code 16: |
Contact support. |
| For Reason Code 20: |
Define a larger size for the CF structure in the CFRM policy. |
| For Reason Code 24: |
Reset the structure using operator command SETXCF
FORCE,STR,STRNAME=name. If the
error persists, contact IBM.
|
RSM0043 - IXCJOIN failed. Return/Reason code: reasoncode
| Explanation |
The Roll Server could not join its IXC message group. |
| Action |
Determine the meaning of the reason code in the IBM document
z/OS Programming: Sysplex Services Reference and
follow the indicated action.
|
RSM0044 - Act conn buffer could not be obtained
| Explanation |
A STORAGE OBTAIN request failed.
|
| Action |
Increase virtual storage available to the Roll Server.
(REGION option of the JCL EXEC statement.)
|
RSM0045 - Applied zaps:
| Explanation |
When Zaps are applied to the Roll Server, it issues this message, followed
by a list of applied zaps.
|
| Action |
None. |
RSM0046 - Roll file in use by job jobname ASID
asid
| Explanation |
The Roll Server cannot start because another Roll Server is using a roll
file. The other Roll Server is running in job or started task named
jobname with address space
identifier asid. The message is followed
by the roll file's DSN.
|
| Action |
Ensure that all Roll Servers have dedicated roll files. |
RSM0047 - Operator command: command
| Explanation |
The Roll Server echoes operator commands to JESMSGLG.
|
| Action |
None. |
RSM0048 - IARV64 GETSTOR failed. Return code: rc
| Explanation |
The Roll Server uses Memory Objects for the Local Roll Buffers. The Memory
Objects are acquired using the IARV64 services. A GETSTOR function
failed.
|
| Action |
Determine the action in the IARV64 description in the current IBM document
MVS Programming: Authorized Assembler Services
Reference manual.
|
RSM0049 - Disconnected from CF with RSN=FAILURE
| Explanation |
The Roll Server disconnected from the Coupling Facility structure with
parameter REASON=FAILURE in order to notify other participating
Roll Servers of its own termination with failure.
|
| Action |
None. |
RSM0050 - Disconnected from CF with RSN=NORMAL
| Explanation |
The Roll Server disconnected from the Coupling Facility structure with
parameter REASON=NORMAL in order to notify other participating Roll
Servers of its own normal termination.
|
| Action |
None. |
RSM0051 - Roll file n is newer than the CF structure
| Explanation |
A roll file was newly formatted, but the Coupling Facility structure still
contains its Roll File Directory.
|
| Action |
After formatting a roll file, re-initialize the CF structure using operator
command SETXCF FORCE,STR,STRNAME=name
|
RSM0052 - Not enough storage for IARV64 GETSTOR - Increase MEMLIMIT
| Explanation |
Not enough memory in Memory Objects could be allocated to hold the Local
Roll Buffer(s). The allocatable amount is controlled by the
MEMLIMIT parameter of the JCL EXEC
statement and SMF exit IEFUSI.
|
| Action |
Increase the amount of usable storage in the
MEMLIMIT parameter, or change the IEFUSI
exit.
|
RSM0053 - Not enough memory for SNAP
| Explanation |
A SNAP dump could not be taken because a STORAGE OBTAIN
request failed.
|
| Action |
Increase virtual storage available to the Roll Server.
(REGION option of the JCL EXEC statement.)
|
RSM0054 - OPEN for SYSUDUMP failed
| Explanation |
A SNAP dump could not be taken because SYSUDUMP could not be
opened.
|
| Action |
Ensure that the Roll Server job or started task includes a DD statement
for SYSUDUMP.
|
RSM0055 - CF structure does not contain enough lists
| Explanation |
For each roll file, the Roll Server maintains its directory in a separate
list in the CF structure.
The existing structure has fewer lists than the
number of roll files to be used.
|
| Action |
Re-initialize the CF structure using operator command SETXCF
FORCE,STR,STRNAME=name, or use
fewer roll files.
|
RSM0056 - LRB slotsize invalid or not numeric
| Explanation |
The fourth parameter is either not numeric or greater than
10000000.
|
| Action |
Correct typing error or specify a smaller LRB slot size. |
RSM0057 - Bad return code from IEANTCR: rc
| Explanation |
The Name/Token Service denied a create request with return code
rc.
|
| Action |
Determine the action from the description of IEANTCR in the
current IBM document MVS Programming: Authorized Assembler Services
Reference manual.
|
RSM0058 - Rollserver already active in subsid: Job
jobname ASID asid
| Explanation |
The Roll Server determined that in the Natural subsystem specified in the
first parameter, subsid, another Roll
Server is already active. The other Roll Server is running in job or started
task named jobname, with address space
identifier asid.
|
| Action |
Start only one Roll Server per Natural subsystem per MVS image. |
RSM0059 - Roll file ddname is below version 412
| Explanation |
The roll file specified in ddname
has an incompatible format.
|
| Action |
Reformat the roll file using NATRSRFI.
See Natural Roll
Server Operation in the Natural
Operations documentation.
|
RSM0060 - User exit loaded: NATRSU14
| Explanation |
User exit NATRSU14 is loaded and will be called to allocate
users to roll files.
|
| Action |
None. |
RSM0061 - Slot size must be specified when no roll files are used
| Explanation |
When running without roll files, a default value for the LRB slot size
cannot be determined.
|
| Action |
Specify LRB slot size as fourth parameter. |
RSM0062 - Running with in-core roll file
| Explanation |
The second parameter specified 0 for the number of roll
files. Natural threads are held in Local Roll Buffer slots only and are lost
when the Roll Server terminates.
|
| Action |
None. |
RSM0063 - Coupling Facility will not be used
| Explanation |
The second parameter specified 0 for the number of roll
files, yet the fifth parameter specified a CF structure. To enable Natural to
run on several MVS images in a Parallel Sysplex, the Roll Server needs to use
roll files. Operation continues without roll files, but the Roll Server will not
communicate with other Roll Servers in other MVS images.
|
| Action |
Specify roll files in a Parallel Sysplex, or do not specify a CF structure
name with zero roll files.
|
RSM0064 - High/low water marks ignored
| Explanation |
The second parameter specified 0 for the number of roll
files, yet low or high watermarks were also specified. With no roll files, low
and high watermark are meaningless. Operation continues.
|
| Action |
Do not specify watermarks with zero roll files. |
RSM0065 - XES Event exit received unexpected event type:
nn
| Explanation |
The exit for the connection to the CF structure received an event type
that it cannot handle. nn is the number
corresponding to the event type.
|
| Action |
Contact support. |
RSM0066 - REBUILD Start: CF structure temporarily unavailable
| Explanation |
Operator command SETXCF START,REBUILD… was
issued for the Coupling Facility Structure that holds the Roll File Directory.
Roll Server operation is quiesced until the Rebuild operation is complete.
|
| Action |
None. |
RSM0067 - REBUILD End: CF structure available again
| Explanation |
Operator command SETXCF START,REBUILD… was
issued for the Coupling Facility Structure that holds the Roll File Directory.
Rebuild is now complete and the Roll Server resumes normal operation.
|
| Action |
None. |
RSM0068 - LRB slot size parameter ignored
| Explanation |
When running with roll files, the roll file slot size determines the LRB
slot size.
|
| Action |
Specify this parameter only when running without roll file. |
RSM0069 - Invalid non-activity time
| Explanation |
The eighth start-up parameter (or TIMEOUT NAT
command) is not numeric or greater than 10000000.
|
| Action |
Specify a valid number. |
RSM0070 - Invalid timeout check time
| Explanation |
The nineth start-up parameter (or TIMEOUT TOC
command) is not numeric or not a valid time of day.
|
| Action |
Specify a valid time of the form h,
hh, hhm, or
hhmm |
RSM0072 - Timeout processing starting
| Explanation |
The routine to detect and delete non-active sessions is running. |
| Action |
None. |
RSM0073 - Scheduled/Operator timeout processing deleted n
sessions
| Explanation |
Timeout check has detected and deleted n
sessions that had been inactive longer than the non-activity time specified as
start-up parameter or with the TIMEOUT NAT command.
Operator timeout processing was requested by the operator command
TIMEOUT NOW while scheduled timeout processing was
run according to the parameter settings.
|
| Action |
None. |
RSM0074 - Timeout processing ended with return code rc
| Explanation |
The routine to detect and delete non-active sessions has ended with return
code rc. In case of return code 12,
rc takes the form
rc/rsn, where
rsn is the reason code.
|
| Action |
Check in Return Codes and Reason
Codes of the Roll Server Requests for an explanation of
the return and reason code, and action to be taken.
|
RSM0075 - TIMEOUT ON/NOW rejected: No valid timeout parameters
| Explanation |
No valid non-activity time and/or no valid timeout-check-time has been
specified before this command was issued.
|
| Action |
For TIMEOUT ON, either specify non-activity
time and timeout-check-time as start-up parameters, or precede the command with
TIMEOUT NAT and TIMEOUT
TOC commands. For TIMEOUT NOW, either
specify non-activity time as start-up parameter or precede the command with
TIMEOUT NAT.
|
RSM0076 - Timeout processing disabled
| Explanation |
Timeout processing was disabled by a TIMEOUT OFF
command.
|
| Action |
None. |
RSM0077 - REPEAT, TERSE, TOC, VERBOSE, or ?
| Explanation |
The TIMEOUT operator command was issued with an
invalid sub-parameter.
|
| Action |
For a valid TIMEOUT command syntax, refer to
Natural
Roll Server Operation in the Natural
Operations documentation.
|
RSM0078 - Invalid parameter: parameter
| Explanation |
An invalid parameter was specified, or the last parameter was not
UCTRAN.
|
| Action |
Correct the PARM string of the JCL EXEC
statement.
|
RSM0081 - Compression task n started successfully
| Explanation |
The Roll Server has started an additional task to handle the compression
and decompression work load.
|
| Action |
None. |
RSM0082 - Compression task could not be started: Error
n
| Explanation |
Error n occurred while the Roll
Server was starting a new compression task.
|
| Action |
Contact support. |
RSM0083 - Roll Server not in active state. TIMEOUT aborted.
| Explanation |
The Roll Server has deallocated its resources due to the operator command
DEAL or a subtask abnormal end. The
TIMEOUT command cannot execute in this
situation.
|
| Action |
Reactivate the Roll Server with the operator command
START, or terminate the Roll Server and restart
it.
|
RSM0084 - Low water mark cannot be above high water mark
| Explanation |
The low water mark must be below the high water mark. |
| Action |
Correct the PARM string of the JCL EXEC
statement, or the low water/high water values in the parameter file.
|
RSM0085 - Module NATRSCMP not linked: Roll compression disabled.
| Explanation |
Module NATRSCMP must be linked to the Roll Server. |
| Action |
Check the installation process of the Roll Server, and Contact
support.
|
RSM0086 - Roll compression will run on zIIP
| Explanation |
The Roll Server has determined that the system includes one or more IBM
System z Integrated Information Processors (zIIPs). Compression tasks will run
as SRBs and be scheduled to run on the zIIP.
|
| Action |
None. |
RSM0087 - Enclave could not be created for SRB: n
| Explanation |
Error n occurred when the Roll
Server tried to create a Work Load Manager (WLM) enclave for the compression
SRB.
|
| Action |
Contact support. |
RSM0088 - Enclave could not be redirected for SRB:
n
| Explanation |
Error n was returned by the IBM
service that was called to specify CPU offload to an IBM System z Integrated
Information Processor (zIIP).
|
| Action |
Contact support. |
RSM0089 - No zIIP available. Roll compression will run on GP.
| Explanation |
An IBM System z Integrated Information Processor (zIIP) is not installed.
Thread compression and decompression will run on a general purpose processor.
|
| Action |
None. |
RSM0090 - DDNAME ddname does not designate a VSAM LINEAR
file.
| Explanation |
The data set defined in the DD statement for
ddname is a VSAM file but is not of
type LINEAR.
|
| Action |
Specify a VSAM LINEAR file. |
RSM0091 - Unexpected reason code code opening DDNAME
ddname
| Explanation |
A warning return code was received with reason code
code when opening a VSAM roll
file.
|
| Action |
Check message IEC161I in your JESMSGLG and follow the instructions IBM
provides for this message in their MVS System Messages documentation.
|
RSM0092 - Wrong ECSAD version: version
| Explanation |
NATRSMvr is started while there is still an ECSA-Directory present for
another version of NATRSMvr for this subsystem-ID.
|
| Action |
Rename the subsystem-ID, IPL the system, or start NATASMvr with option
ECSADUPD.
|
RSM0093 - High water mark exceeded for roll file n
| Explanation |
The high water mark has been exceeded for the specified roll file
n. The roll server triggers a cleanup, as if
TIMEOUT NOW has been issued.
|
| Action |
If you want to manually free one or more slots, check the roll server slots
occupation with SYSTP
R > subsystem > L.
|
RSM0094 - Low water mark exceeded for roll file n
| Explanation |
The low water mark has been exceeded, but the high water mark has not been
reached yet.
|
| Action |
If this message occurs regularly, increase the size of the roll files to
avoid the eventual exceeding of the the high water mark.
|
RSM0095 - Filling rate under low water mark for roll file
n
| Explanation |
Enough free spots were freed and the occupation level of the roll file
n went under the low water mark.
|
| Action |
None. |
RSM0099 - Storage Obtain error in Staging Task.
RC=rc
| Explanation |
A STORAGE OBTAIN call by a Staging Task ended with a bad
return code. This message reports this return code.
|
| Action |
None. |
RSM0119 - Roll Server settings in effect:
| Explanation |
This message is issued at Roll Server start-up. It is followed by several
RSM0119 messages of varying contents, summarizing parameters in
effect for this run.
Selected RSM0119 messages are also issued
in response to the TIMEOUT operator command.
|
| Action |
None. |
RSM0120 - Start of Statistics
| Explanation |
This message is issued during shut-down and in response to the
STATS operator command.
Several
RMS0120 statistics messages with varying text follow this
message.
|
| Action |
None. |
RSM0120 - End of Statistics
| Explanation |
This message is issued during shut-down and in response to the
STATS operator command.
It indicates the end of
statistics output.
|
| Action |
None. |
RSM0131 - Environment error detected. SubRC:
subrc
| Explanation |
Diagnostic message that goes along with RC = 16. |
| Action |
Contact support. |
RSM0133 - DEAL and START commands are no longer supported.
| Explanation |
The DEAL and START
operator commands are no longer available.
It indicates the end of statistics
output.
|
| Action |
If you want to refresh the roll server, use the z/OS STOP and START
console commands.
|
RSM0190 - +++++ Start of Diagnostics +++++
| Explanation |
This message is issued in response to the
DIAGNOSE operator command.
Several
RMS0190 messages with varying text may follow this message,
depending on the nature of the supplied diagnostic Zaps.
|
| Action |
Follow advice given with diagnostic Zap. |
RSM0190 - +++++ End of Diagnostics +++++
| Explanation |
This message is issued in response to the
DIAGNOSE operator command. It indicates the end of
output generated by the DIAGNOSE command.
|
| Action |
Follow advice given with diagnostic Zap. |
RSM0313 - NATRSCMP return code 99. Diagnostic data follows:
| Explanation |
An unexpected error was encountered during thread
compression/decompression.
|
| Action |
Contact support. |
RSM0313 - NATRSCMP return code 8. UserID and error message follow:
| Explanation |
An unexpected error was encountered during thread
compression/decompression.
|
| Action |
Contact support. |
RSM0313 - DUMP requested by NATRSCMP. Check SYSUDUMP data set.
| Explanation |
An unexpected error was encountered during thread
compression/decompression.
|
| Action |
Contact support. |
RSM0451
| Explanation |
Natural subsystem ID: subsid |
| Action |
Contact support. |
RSM0452
| Explanation |
Number of Roll Files: nnn |
| Action |
Contact support. |
RSM0453
| Explanation |
Number of LRB slots per Roll File: nnn |
| Action |
Contact support. |
RSM0454
| Explanation |
Non-activity time: nnn hours |
| Action |
Contact support. |
RSM0455
| Explanation |
Timeout check scheduled for hh:mm |
| Action |
Contact support. |
RSM0456
| Explanation |
Timeout check not scheduled. |
| Action |
Contact support. |
RSM0457
| Explanation |
Non-activity time not set. |
| Action |
Contact support. |
RSM0458
| Explanation |
Timeout check is enabled / disabled. |
| Action |
Contact support. |
RSM0459
| Explanation |
Invalid REPEAT value. Specify 0 to 1440 minutes. |
| Action |
Contact support. |
RSM0460
| Explanation |
REPEAT interval set to nnn minutes |
| Action |
Contact support. |
RSM0461
| Explanation |
REPEAT interval not set |
| Action |
Contact support. |
RSM0462
| Explanation |
LRB slot size: nnn bytes |
| Action |
Contact support. |
RSM0500
| Explanation |
+++++ start / end of Statistics +++++ |
| Action |
Contact support. |
RSM0501
| Explanation |
Users currently allocated : nnn |
| Action |
Contact support. |
RSM0502
| Explanation |
Roll File n: nnn |
| Action |
Contact support. |
RSM0503
| Explanation |
Maximum users allocated (session) : nnn |
| Action |
Contact support. |
RSM0504
| Explanation |
Total number of writes/errors: nnn nnnnnn |
| Action |
Contact support. |
RSM0505
| Explanation |
Number of direct writes: nnn |
| Action |
Contact support. |
RSM0506
| Explanation |
Total number of reads/errors: nnn nnnnnn |
| Action |
Contact support. |
RSM0507
| Explanation |
Number of direct reads: nnn |
| Action |
Contact support. |
RSM0508
| Explanation |
Peak periods of write activity: |
| Action |
Contact support. |
RSM0509
| Explanation |
Distribution of thread sizes: |
| Action |
Contact support. |
RSM0510
| Explanation |
zIIP CPU time information in seconds: |
| Action |
Contact support. |
RSM0522
| Explanation |
Number of compress calls: nnn nnn.nn% |
| Action |
Contact support. |
RSM0523
| Explanation |
Number of decompress calls: nnn nnn.nn% |
| Action |
Contact support. |
RSM0524
| Explanation |
LRB slot size: nnn bytes |
| Action |
Contact support. |
RSM0551
| Explanation |
Roll File n activity: |
| Action |
Contact support. |
RSM0700
| Explanation |
+++++ start / end of Diagnostics +++++ |
| Action |
Contact support. |
RSM0701
| Explanation |
Compression task Compr.TaskId block at xxxxxxxxx |
| Action |
Contact support. |
RSM0702
| Explanation |
Compression task is Compr.TaskId |
| Action |
Contact support. |
RSM0703
| Explanation |
Resume token: xxxxxxxx xxxxxxxx |
| Action |
Contact support. |
RSM0704
| Explanation |
CRB: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx |
| Action |
Contact support. |
RSM0705
| Explanation |
RESUME errors 4/8/24/other: nnnnn nnnnn nnnnn nnnnn |
| Action |
Contact support. |
RSM0706
| Explanation |
Waits for CSST: nnnnnnn |
| Action |
Contact support. |
RSM0707
| Explanation |
LRB at : xxxxxxxx_xxxxxxxx |
| Action |
Contact support. |
RSM0708
| Explanation |
Highest LRB slot: xxxxxxxx_xxxxxxxx |
| Action |
Contact support. |
RSM0709
| Explanation |
Roll Server YYYYMMDDHHMM loaded at xxxxxxxx |
| Action |
Contact support. |
RSM0710
| Explanation |
ABINFO: Time/PSW: xxxxxxxx xxxxxxxx/xxxxxxxx xxxxxxxx |
| Action |
Contact support. |
RSM0711
| Explanation |
No abend recorded. |
| Action |
Contact support. |
RSM0712
| Explanation |
Abend code: xxxxxxxx Reason: xxxxxxxx ID: xxxx Sxxx |
| Action |
Contact support. |
RSM0713
| Explanation |
xxxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx |
| Action |
Contact support. |
RSM0714
| Explanation |
MSX: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx |
| Action |
Contact support. |
RSM0715
| Explanation |
Invalid slot state: xxxxxxxx Slot address: xxxxxxxx |
| Action |
Contact support. |
RSM0716
| Explanation |
Our ASID: xxxx. RS Control Block at xxxxxxxx |
| Action |
Contact support. |
RSM0717
| Explanation |
Storage Counters: nnnnnnnnnnn nnnnnnnnnnn nnnnnnnnnnn nnnnnnnnnnn |
| Action |
Contact support. |
RSM0718
| Explanation |
Most recent counter: nnn |
| Action |
Contact support. |
RSM0719
| Explanation |
- STCK - - Addr - - Leng - Where File |
| Action |
Contact support. |
RSM0720
| Explanation |
xxxxxxxx_xxxxxxxx xxxxxxxx xxxxxxxx origin rollfile |
| Action |
Contact support. |