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.
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.)
|
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 Software AG 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 |
s 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. |
RSM0028 - We are already deallocated
| Explanation |
The operator command DEAL
(deallocate) was issued when the Roll Server already was in deallocated state.
|
| Action |
None. |
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 Software AG
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. |
RSM0033 - All resources deallocated
| Explanation |
In response to a DEAL (deallocate)
operator command, the Roll Server is now in deallocated state.
|
| Action |
None. |
RSM0034 - START allowed in deallocated state only
| Explanation |
The START operator command was
issued while the Roll Server was in active state.
|
| Action |
Issue the DEAL (deallocate) command
before issuing the START command.
|
RSM0035 - START parameters missing
| Explanation |
The START operator command was
issued with insufficient parameters.
|
| Action |
Correct the START command and
re-issue it.
|
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 Role 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 Role 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 Software AG 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 Software AG 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 |
RSM0071 - Timeout check time specified without non-activity
time
| Explanation |
The nineth start-up parameter (or TIMEOUT
TOC command) was specified without a valid eighth parameter (or
preceding TIMEOUT NATnnnn
command).
|
| Action |
Specify a valid non-activity time as start-up parameter or
issue TIMEOUT NATnnnn
command before TIMEOUT TOC.
|
RSM0072 - Timeout processing starting
| Explanation |
The routine to detect and delete non-active sessions is
running.
|
| Action |
None. |
RSM0073 - 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.
|
| 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 - Invalid TIMEOUT parm. Specify NAT, NOW, ON, OFF, TOC, 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. |
| Note |
This message is issued by NATRSM83 only. |
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 Software AG Support. |
| Note |
This message is issued by NATRSM83 only. |
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.
|
RSM0085 - Module NATCMP83 not linked: roll compression
disabled
| Explanation |
Thread compression and decompression will be done by the
Natural nucleus during roll out and roll in, respectively.
|
| Action |
If you want thread compression and decompression to execute in
the Roll Server rather than in the Natural nucleus, re-link
NATRSM83 and include NATCMP83.
|
| Note |
This message is issued by NATRSM83 only. |
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. |
| Note |
This message is issued by NATRSM83 only. |
RSM0087 - WLM 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 Software AG Support. |
| Note |
This message is issued by NATRSM83 only. |
RSM0088 - WLM 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 Software AG Support. |
| Note |
This message is issued by NATRSM83 only. |
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. |
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 diagnostic Zaps supplied by Software
AG.
|
| 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. |
