Version 4.2.6
 —  Messages and Codes  —

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.


RSM0001 - Subsystem id invalid

Expl. A subsystem ID was specified that is longer than 4 characters.
Actn. Specify a subsystem ID of 1 to 4 characters.

Top of page

RSM0002 - Roll file number not numeric

Expl. The second parameter is not a number.
Actn. Specify a valid number,

Top of page

RSM0003 - Invalid number of roll files

Expl. A number greater than 5 was specified.
Actn. Specify a number between 0 and 5.

Top of page

RSM0004 - Number of LRB slots not specified

Expl. The third parameter was omitted.
Actn. This is a mandatory parameter. Specify a valid number.

Top of page

RSM0005 - Number of LRB slots not numeric

Expl. The third parameter is not a number.
Actn. Specify a valid number.

Top of page

RSM0006 - Number of LRB slots > 32767

Expl. The number of LRB slots specified is too large.
Actn. Specify a maximum of 32767 LRB slots.

Top of page

RSM0007 - Invalid CF structure name

Expl. A structure name of more than 16 characters was specified.
Actn. Specify a structure name of 16 characters or less.

Top of page

RSM0008 - Bad return code from IEANTRT: rc

Expl. The Name/Token Service returned return code rc.
Actn. See the current IBM MVS Programming: Authorized Assembler Services Reference manual for information about the return code from the IEANTRT request.

Top of page

RSM0009 - DCB buffer could not be obtained. Reason: reasoncode

Expl. A STORAGE OBTAIN request failed with reasoncode.
Actn. Increase virtual storage available to the Roll Server. (REGION option of the JCL EXEC statement.)

Top of page

RSM0010 - OPEN failed for DDNAME: ddname

Expl. The roll file specified under DDNAME ddname could not be opened.
Actn. Specify a valid roll file DSN.

Top of page

RSM0011 - Duplicate roll file DSN

Expl. The same DSN was specified for two roll file DDNAMEs.
Actn. Specify unique DSNs for each roll file.

Top of page

RSM0012 - Temp roll file buffer could not be obtained. Reason: reasoncode

Expl. A STORAGE OBTAIN request failed with reasoncode.
Actn. Increase virtual storage available to the Roll Server. (REGION option of the JCL EXEC statement.)

Top of page

RSM0013 - RF directory buffer could not be obtained. Reason: reasoncode

Expl. A STORAGE OBTAIN request failed with reasoncode.
Actn. Increase virtual storage available to the Roll Server. (REGION option of the JCL EXEC statement.)

Top of page

RSM0014 - LRB directory could not be obtained. Reason: reasoncode

Expl. A STORAGE OBTAIN request failed with reasoncode.
Actn. Increase virtual storage available to the Roll Server. (REGION option of the JCL EXEC statement.)

Top of page

RSM0015 - Creation of dataspace failed. Reason: reasoncode

Expl. The DSPSERV macro returned reason code reasoncode.
Actn. See the current IBM MVS Programming: Authorized Assembler Services Reference manual for information about the reason code from the DSPSERV CREATE request.

Top of page

RSM0016 - ALESERV ADD failed. Reason: reasoncode

Expl. The DSPSERV macro returned reason code reasoncode.
Actn. See the current IBM MVS Programming: Authorized Assembler Services Reference manual for information about the reason code from the ALESERV ADD request.

Top of page

RSM0017 - Size for LRB > 524287 blocks

Expl. The number of LRB slots times LRB slot size exceeds 2 Gigabytes.
Actn. Specify fewer LRB slots or a smaller slot size.

Top of page

RSM0018 - LX table could not be obtained. Reason: reasoncode

Expl. A STORAGE OBTAIN request failed with reasoncode.
Actn. Increase virtual storage available to the Roll Server. (REGION option of the JCL EXEC statement.)

Top of page

RSM0019 - Roll Server Version 42x is active

Expl. The Roll Server initialized successfully and is ready for work.
Actn. None.

Top of page

RSM0020 - Subtask terminated: taskname rc

Expl. The subtask indicated by taskname has terminated. If the return code is not zero, it is indicated as rc.
Actn. If a nonzero rc is reported, contact Software AG.

Top of page

RSM0021 - Subtask termination initiated

Expl. In response to a TERM or DEAL operator command, the Roll Server has started to terminate its subtasks.
Actn. None.

Top of page

RSM0022 - All subtasks terminated

Expl. In response to a TERM or DEAL operator command, the process of terminating the subtasks is finished.
Actn. None.

Top of page

RSM0023 - Other than MODIFY or STOP command received

Expl. The Roll Server received a CIBVERB other than MODIFY or STOP.
Actn. Contact Software AG.

Top of page

RSM0024 - Trace activated

Expl. In response to the TRSTART operator command, the internal trace facility is started.
Actn. None.

Top of page

RSM0025 - Trace stopped

Expl. In response to the TRSTOP operator command, the internal trace facility is stopped.
Actn. None.

Top of page

RSM0026 - Command allowed in active state only: command

Expl. In deallocated (DEAL) state, the Roll Server cannot accept operator command command.
Actn. Issue the START operator command, then repeat the rejected command.

Top of page

RSM0027 - Unknown command command

Expl. An invalid operator command was issued to the Roll Server.
Actn. Check for typing error and correct.

Top of page

RSM0028 - We are already deallocated

Expl. The operator command DEAL (deallocate) was issued when the Roll Server already was in deallocated state.
Actn. None.

Top of page

RSM0029 - Recursive abend in maintask. Now waiting for CANCEL command

Expl. An abend occurred during abend recovery.
Actn. Cancel the Roll Server started task and contact Software AG.

Top of page

RSM0030 - Low Water Mark not numeric or invalid

Expl. The sixth paramter is not a number or exceeds 10.
Actn. Specify a low water mark between 0 and 10.

Top of page

RSM0031 - High Water Mark not numeric or invalid

Expl. The seventh paramter is not a number or exceeds 10.
Actn. Specify a high water mark between 0 and 10.

Top of page

RSM0032 - Work buffer could not be obtained: reasoncode

Expl. A STORAGE OBTAIN request failed with reasoncode.
Actn. Increase virtual storage available to the Roll Server. (REGION option of the JCL EXEC statement.)

Top of page

RSM0033 - All resources deallocated

Expl. In response to a DEAL (deallocate) operator command, the Roll Server is now in deallocated state.
Actn. None.

Top of page

RSM0034 - START allowed in deallocated state only

Expl. The START operator command was issued while the Roll Server was in active state.
Actn. Issue the DEAL (deallocate) command before issuing the START command.

Top of page

RSM0035 - START parameters missing

Expl. The START operator command was issued with insufficient parameters.
Actn. Correct the START command and re-issue it.

Top of page

RSM0036 - DUMP successful for roll file n

Expl. Slots from the Local Roll Buffer and the Roll File Directory were successfully written to Roll File n on disk.
Actn. None.

Top of page

RSM0037 - DUMP failed for roll file n

Expl. The Roll Server was unable to write slots and directory to Roll File n.
Actn. Look for accompanying messages indicating the error situation that prevented a successful dump.

Top of page

RSM0038 - SNAP failed. Task RB could not be obtained

Expl. A STORAGE OBTAIN request failed.
Actn. Increase virtual storage available to the Roll Server. (REGION option of the JCL EXEC statement.)

Top of page

RSM0039 - XES functions not available

Expl. Environmental error. XES functions are not available. This can occur because the coupling facility hardware necessary to provide XES functions is not present.
Actn. Re-IPL the system or contact IBM.

Top of page

RSM0040 - IXLCONN unsuccessful. Reason code: reasoncode

Expl. A connection to the Coupling Facility structure specified as fifth parameter could not be established.
Actn. Determine the meaning of the reason code in z/OS Programming: Sysplex Services Reference and follow the indicated action.

Top of page

RSM0041 - CF initialization successful for list: n

Expl. The Role File Directory for Roll File n was established in the list structure specified as fifth parameter.
Actn. None.

Top of page

RSM0042 - CF initialization failed for list/RSN code: reasoncode

Expl. 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.
Actn. 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.
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.

Top of page

RSM0043 - IXCJOIN failed. Return/Reason code: reasoncode

Expl. The Roll Server could not join its IXC message group.
Actn. Determine the meaning of the reason code in z/OS Programming: Sysplex Services Reference and follow the indicated action.

Top of page

RSM0044 - Act conn buffer could not be obtained

Expl. A STORAGE OBTAIN request failed.
Actn. Increase virtual storage available to the Roll Server. (REGION option of the JCL EXEC statement.)

Top of page

RSM0045 - Applied zaps:

Expl. When Zaps are applied to the Roll Server, it issues this message, followed by a list of applied zaps.
Actn. None.

Top of page

RSM0046 - Roll file in use by job jobname ASID asid

Expl. 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.
Actn. Ensure that all Roll Servers have dedicated roll files.

Top of page

RSM0047 - Operator command: command

Expl. The Roll Server echoes operator commands to JESMSGLG.
Actn. None.

Top of page

RSM0048 - IARV64 GETSTOR failed. Return code: rc

Expl. The Roll Server uses Memory Objects for the Local Roll Buffers. The Memory Objects are acquired using the IARV64 services. A GETSTOR function failed.
Actn. Determine the action in the IARV64 description in the current IBM MVS Programming: Authorized Assembler Services Reference manual.

Top of page

RSM0049 - Disconnected from CF with RSN=FAILURE

Expl. 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.
Actn. None.

Top of page

RSM0050 - Disconnected from CF with RSN=NORMAL

Expl. 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.
Actn. None.

Top of page

RSM0051 - Roll file n is newer than the CF structure

Expl. A roll file was newly formatted, but the Coupling Facility structure still contains its Roll File Directory.
Actn.

After formatting a roll file, re-initialize the CF structure using operator command SETXCF FORCE,STR,STRNAME=name

Top of page

RSM0052 - Not enough storage for IARV64 GETSTOR - Increase MEMLIMIT

Expl. 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.
Actn. Increase the amount of usable storage in the MEMLIMIT parameter, or change the IEFUSI exit.

Top of page

RSM0053 - Not enough memory for SNAP

Expl. A SNAP dump could not be taken because a STORAGE OBTAIN request failed.
Actn. Increase virtual storage available to the Roll Server. (REGION option of the JCL EXEC statement.)

Top of page

RSM0054 - OPEN for SYSUDUMP failed

Expl. A SNAP dump could not be taken because SYSUDUMP could not be opened.
Actn. Ensure that the Roll Server job or started task includes a DD statement for SYSUDUMP.

Top of page

RSM0055 - CF structure does not contain enough lists

Expl.

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.

Actn.

Re-initialize the CF structure using operator command SETXCF FORCE,STR,STRNAME=name, or use fewer roll files.

Top of page

RSM0056 - LRB slotsize invalid or not numeric

Expl. The fourth parameter is either not numeric or greater than 10000000.
Actn. Correct typing error or specify a smaller LRB slot size.

Top of page

RSM0057 - Bad return code from IEANTCR: rc

Expl. The Name/Token Service denied a create request with return code rc.
Actn. Determine the action from the description of IEANTCR in the current IBM MVS Programming: Authorized Assembler Services Reference manual.

Top of page

RSM0058 - Rollserver already active in subsid: Job jobname ASID asid

Expl. 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.
Actn. Start only one Roll Server per Natural subsystem per MVS image.

Top of page

RSM0059 - Roll file ddname is below version 412

Expl. The roll file specified in ddname has an incompatible format.
Actn. Reformat the roll file using NATRSRFI. Please, refer to Natural Roll Server Operation in the Natural Operations documentation.

Top of page

RSM0060 - User exit loaded: NATRSU14

Expl. User exit NATRSU14 is loaded and will be called to allocate users to roll files.
Actn. None.

Top of page

RSM0061 - Slot size must be specified when no roll files are used

Expl. When running without roll files, a default value for the LRB slot size cannot be determined.
Actn. Specify LRB slot size as fourth parameter.

Top of page

RSM0062 - Running with in-core roll file

Expl. 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.
Actn. None.

Top of page

RSM0063 - Coupling Facility will not be used

Expl. 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.
Actn. Specify roll files in a Parallel Sysplex, or do not specify a CF structure name with zero roll files.

Top of page

RSM0064 - High/low water marks ignored

Expl. 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.
Actn. Do not specify watermarks with zero roll files.

Top of page

RSM0065 - XES Event exit received unexpected event type: nn

Expl. 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.
Actn. Contact Software AG Support.

Top of page

RSM0066 - REBUILD Start: CF structure temporarily unavailable

Expl. 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.
Actn. None.

Top of page

RSM0067 - REBUILD End: CF structure available again

Expl. 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.
Actn. None.

Top of page

RSM0068 - LRB slot size parameter ignored

Expl. When running with roll files, the roll file slot size determines the LRB slot size.
Actn. Specify this parameter only when running without roll file.

Top of page

RSM0069 - Invalid non-activity time

Expl. The eighth start-up parameter ( or TIMEOUT NAT command) is not numeric or greater than 10000000.
Actn. Specify a valid number.

Top of page

RSM0070 - Invalid timeout check time

Expl. The nineth start-up parameter (or TIMEOUT TOC command) is not numeric or not a valid time of day.
Actn. Specify a valid time of the form h, hh, hhm, or hhmm

Top of page

RSM0071 - Timeout check time specified without non-activity time

Expl. The nineth start-up parameter (or TIMEOUT TOC command) was specified without a valid eighth parameter (or preceding TIMEOUT NATnnnn command).
Actn. Specify a valid non-activity time as start-up parameter or issue TIMEOUT NATnnnn command before TIMEOUT TOC.

Top of page

RSM0072 - Timeout processing starting

Expl. The routine to detect and delete non-active sessions is running.
Actn. None.

Top of page

RSM0073 - Timeout processing deleted n sessions

Expl. 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.
Actn. None.

Top of page

RSM0074 - Timeout processing ended with return code rc

Expl. 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.
Actn. 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.

Top of page

RSM0075 - TIMEOUT ON/NOW rejected: No valid timeout parameters

Expl. No valid non-activity time and/or no valid timeout-check-time has been specified before this command was issued.
Actn. 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.

Top of page

RSM0076 - Timeout processing disabled

Expl. Timeout processing was disabled by a TIMEOUT OFF command.
Actn. None.

Top of page

RSM0077 - Invalid TIMEOUT parm. Specify NAT, NOW, ON, OFF, TOC, or ?

Expl. The TIMEOUT operator command was issued with an invalid sub-parameter.
Actn. For a valid TIMEOUT command syntax, refer to Natural Roll Server Operation in the Operations documentation.

Top of page

RSM0119 - Roll Server settings in effect:

Expl. 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.

Actn. None.

Top of page

RSM0120 - Start of Statistics

Expl. This message is issued during shut-down and in response to the STATS operator command.

Several RMS0190 statistics messages with varying text follow this message.

Actn. None.

Top of page

RSM0120 - End of Statistics

Expl. This message is issued during shut-down and in response to the STATS operator command.

It indicates the end of statistics output.

Actn. None.

Top of page

RSM0190 - +++++ Start of Diagnostics +++++

Expl. 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.

Actn. Follow advice given with diagnostic Zap.

Top of page

RSM0190 - +++++ End of Diagnostics +++++

Expl. This message is issued in response to the DIAGNOSE operator command. It indicates the end of output generated by the DIAGNOSE command.
Actn. Follow advice given with diagnostic Zap.

Top of page