Messages RSS0100 through RSS0199
This topic contains messages for the Resident Security Server component.
Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.
The table is being loaded. Please wait for a bit ...
Number | Description |
|---|---|
RSS0100E | Open failed for http object indexMemberName Explanation: Resident Security Server has failed while attempting to open one of its required HTTP objects from yourHLQ.HTDOCS, so the product terminates. User Response: Contact BMC Support with the indicated object name. |
RSS0101E | Load failed for http object indexMemberName (indexMemberSize bytes) Explanation: While loading its HTTP objects during startup, Resident Security Server has failed to load part of the indicated object, so the product terminates. User Response: Contact BMC Support with the indicated object name. |
RSS0102D | HTTP object objectName added (objectLength bytes) Explanation: The MessageLevel HTTPTrace parameter is set in the Configuration data set. This message provides an audit trail of each HTTP object loaded from the yourHlq.HTDOCS data set along with its size in bytes. Normally, you would see this message only if BMC Support asked you to activate the HTTP Trace facility. User response: No action is required. |
RSS0103E | No JSON DLL for HTTP object objectId Explanation: This message should never occur since it implies a mismatch between the z/OS server code and the browser interface code. Because both of these primary components are installed together, the installation process might not have worked correctly or that the data sets have suffered some damage subsequently. User response: Contact BMC Support with the text of the message and the current level of Resident Security Server from message RSS001I. |
RSS0104E | Load failed for http object memberName : maximum size exceeded Explanation: Cannot load the specified HTTP object because of its size. The limit is 3 MB. User response: Contact BMC Support. |
RSS0105E | XML parser 'operationType request failed return=returnCode reason=reasonCode Explanation: When parsing an XML stream, the indicated parse function failed with the indicated return and reason codes. The return and reason codes are returned by the IBM z/OS XML System Services and documented in the reference guide for that product. User response: Correct the error and try again. If you can't determine the reason for the error, contact BMC Support. |
RSS0106E | JSON parser error: message Explanation: When parsing a JSON stream, the parse function indicated failed with the indicated reason. User response: Correct the error and try again. If you can't determine the reason for the error, contact BMC Support. |
RSS0107D | HTTP object objectName updated (objectLength bytes) Explanation: This HTTPTrace message is used for diagnostics. User response: No action is required. |
RSS0108E | No HTTP cache available for member memberName Explanation: An update to the HTTP cache was requested, but none was found. User response: Contact BMC Support. |
RSS0110E | No initialisation dll for serverType server serverId Explanation: The initialization DLL for either a CustomApp or REST API application for the indicated application id could not be loaded. The cause might be configuration or installation error. User response: Correct the error and try again. If you can't determine the reason for the error, contact BMC Support. |
RSS0111I | Rest API active for serverId on port serverPort Explanation: A REST API has been activated on the IP address and port indicated and is ready to accept incoming REST transactions. User response: No action is required. |
RSS0112I | Rest API ended for serverId on port serverPort Explanation: The REST API has been terminated on the IP address and port indicated and no longer accepts incoming REST transactions. User response: No action is required. |
RSS0113I | &PID cma cmaAddress cmai cmaiAddress mstr masterCmaiAddress token masterToken Explanation: Reports information about the current environment. User response: No action is required. |
| RSS0114I | ZDTUSS Interval timing overriden to be intervalTime Explanation: This message indicates the USS interval time in minutes. User response: No action is required. |
| RSS0115I | Rexx host environment serviceName enabled Explanation: The indicated service name under the REXX host is enabled. User response: No action is required. |
| RSS0116I | Rexx function functionName enabled Explanation: The specified REXX function is enabled. User response: No action is required. |
| RSS0117E | UTF-8 Translation Error at offset offset Explanation: An error has occurred during conversion of Unicode. |
| RSS0118I | REST API buffer dynamically extended to byte bytes Explanation: The REST API buffer size has been extended dynamically to the indicated number of bytes. User response: No action is required. |
RSS0120E | Dynamic allocation failed for dd ddName : error punits->sysout._errorCode info punits->sysout._infoCode Explanation: BMC AMI Resident Security Server was unable to dynamically allocate the indicated ddname with the indicated error and reason code. For your z/OS level, and explanations of the indicated error code and info code, see "MVS dynamic allocation function" in the z/OS MVS Programming: Authorized Assembler Services Guide. User response: Correct the error and restart the product. If you cannot determine the reason for the error, contact BMC Support. |
RSS0121E | Open failed for dd ddName : errorCode Explanation: A file with the indicated DD name failed to open for the indicated reason. User response: Correct the error and restart the product. If you can't determine the reason for the error, contact BMC Support. |
| RSS0122E | operation failed for DD ddname : errorMessage Explanation: The data set operation for the indicated ddname has failed for the indicated reason. User response: Correct the error and restart the product. If you cannot determine the reason for the error, contact BMC Support. |
RSS0125I | configMember INCLUDE member --> includeMember Explanation: This message provides the member included in the configuration member of the product. User response: No action is required. |
RSS0126I | configMember file line lineNumber --> parameterValue Explanation: This message provides the parameter value at the line number in the product configuration member. User response: No action is required. |
| RSS0128E | Dataspace dataSet checkpoint dataset full Explanation: The indicated checkpoint data set is full. User response: Compress or allocate a checkpoint data set and restart the product. If the problem persists, contact BMC Support. |
| RSS0129E | Dataspace dataSet checkpointing disabled Explanation: The checkpoint data set option is disabled. User response: Allocate a checkpoint data set and restart the product. If the problem persists, contact BMC Support. |
RSS0130E | Unable to operationType checkpoint dataset : reason returnCode Explanation: A function being performed on the checkpoint data set failed for the indicated reason. User response: Contact BMC Support with the indicated reason code. |
RSS0131I | Checkpoint dataset cold start Explanation: BMC AMI Resident Security Server has opened an empty checkpoint data set, which has not been started. User response: No action is required. |
RSS0132I | Checkpoint dataset warm start: size size bytes Explanation: BMC AMI Resident Security Server has opened a valid checkpoint data set allocated with the indicated current size. User response: No action is required. |
RSS0133I | Checkpoint dataset ready Explanation: The checkpoint data set has been successfully opened and is ready for use. User response: No action is required. |
RSS0134I | Checkpoint dataset expanded Explanation: The checkpoint data set has been dynamically expanded for additional data. User response: No action is required. |
RSS0135E | Dataspace dataspaceName operation failed : reason reasonCode r15 register15Contents r0 register0Contents Explanation: The specified dataspace operation failed with the given error messages. User response: Contact BMC Support. |
RSS0136I | Dataspace dataSpaceName cold start Explanation: The specified dataspace was cold started. User response: No action is required. |
RSS0137I | Dataspace dataSpaceName warm start: size dataSpaceSize bytes Explanation: The specified dataspace was warm started. User response: No action is required. |
| RSS0141I | HTTP Server Defaulting to port portNumber Explanation: This message indicates the default port number for the HTTP server. User response: No action is required. |
| RSS0145I | productName, groupName Is reconfiguring from oldMember to newMember Explanation: The configuration member for the indicated product and the group have been changed from one member (oldMember) to another (newMember). User response: No action is required. |
| RSS0146I | Reconfiguring to newMember ended successfully Explanation: The reconfiguration to the new member has been successful. User response: No action is required. |
| RSS0149I | productName, groupName Issued command: command Explanation: This message indicates the command issued by the indicated product. User response: No action is required. |
| RSS0165I | BMC PAM:Client clientName could not be resolved Explanation: The indicated client could not be resolved in PAM. User response: Make sure that the client name is valid and try again. If the problem persists, contact BMC Support. |
| RSS0166I | BMC PAM:Client clientName resolved to clientIP Explanation: This message displays the corresponding client IP for the indicated client. User response: No action is required. |
RSS0138I | Dataspace dataSpaceName ready: size dataSpaceSize bytes Explanation: The dataspace is now ready. User response: No action is required. |
RSS0139E | Dataspace dataSpaceName operation failed pool poolIndex : reason reasonCode Explanation: The specified dataspace operation failed with the given error messages. User response: Contact BMC Support. |
RSS0140E | Dataspace dataSpaceName closed Explanation: The dataspace is now closed. User response: No action is required. |
RSS0150I | Invalid command Explanation: You have issued a command that Resident Security Server does not recognize. User response: See the product documentation and ensure that you issue a valid command. |
RSS0151I | Invalid command syntax Explanation: You have issued an Resident Security Server command but used incorrect syntax. User response: See the product documentation to check the command’s syntax and reissue the command using valid syntax. |
RSS0152I | Invalid command argument argument Explanation: You have issued an Resident Security Server command, but the product does not recognize the indicated argument. User response: See the product documentation to check the command’s syntax and required operands. Then reissue the command with valid arguments. |
RSS0155I | Shutdown command accepted Explanation: You have issued the SHUTDOWN command, which Resident Security Server has accepted, and the product begins to shut down. User reponse: You can log on to RACFGUI and currently logged-on users can no longer use the interface. User response: No action is required. |
| RSS0158I | Command rejected: responseMessage Explanation: The issued command has been rejected. User response: Diagnose the response message and correct any errors. If the problem persists, contact BMC Support |
The following messages have been removed starting with Resident Security Server version 2.3 SPE2404.
Number | Description |
|---|---|
RSS0159I | Command complete: responseMessage Explanation: The issued command has completed. User response: No action is required. |
RSS0160I | Checkpoint dataset checkpointStatus Explanation: This message is returned on a CHKPT command and gives the current status of the checkpoint data set. User response: No action is required. |
RSS0161I | checkpointMetric valueDataspaceSizeBlocks Explanation: This message forms part of a block of messages that the CHKPT command returns. It shows the current value for a specific checkpoint data set metric. User response: No action is required. |
RSS0162I | Pool size bytes blocks free Explanation: This message forms the header for a block of messages that the CHKPT command returns. User response: No action is required. |
RSS0163I | poolId size bytes blocks free Explanation: This message forms part of a block of messages that the CHKPT command returns. It shows the metrics for each buffer pool in the checkpoint data set. User response: No action is required. |
RSS0164I | Total totalSpace totalBlocks Explanation: This message is returned on a CHKPT command and gives the current number of blocks and bytes allocated to the checkpoint data set. User response: No action is required. |
RSS0170I | Active RSS applications Explanation: This is the header message for the APPS command. User response: No action is required. |
RSS0171I | LPAR lparName Explanation: This is the subheading message for the APPS command. This message is issued for each LPAR on which Resident Security Server, with the same RSS ID, has been detected. User response: No action is required. |
RSS0172I | App appId job jobName status Explanation: This message, which is issued for each Resident Security Server APP associated with the product instance, is the detail message for the APPS command. It shows the APP name, job name and status. User response: No action is required. |
RSS0173I | Active TSO instances Explanation: This is the header message for the TSO command. User response: No action is required. |
RSS0174I | Job jobname (x'asid) status xcfStatus autostartFlag Explanation: This message, which is the detail message for the TSO command, shows the job name, ASID, and status of a Resident Security Server TSO Instance. User response: No action is required. |
RSS0175I | Unable to locate &pid csa area Explanation: This message is issued for the CSA command when no Resident Security Server specific CSA area can be found. User response: No action is required. |
RSS0176I | RSS csa token token address csaAddress Explanation: This heading message for the CSA command shows the current CSA Token being used. User response: No action is required. |
RSS0177I | Jobname asid alet dataSpace cmai Explanation: This is the subheading message for the CSA command. User response: No action is required. |
RSS0178I | cmaiJobname cmaiAsid cmaiAlet cmaiDsname pointerAddress Explanation: This message is the detail line for the CSA command. It shows the job details for Resident Security Server instances sharing the same CSA token. User response: No action is required. |
RSS0179I | metric address value Explanation: This message forms part of a block of messages returned by the DS command. Each message in the block describes a specific dataSpace metric and its current value. User response: No action is required. |
RSS0180I | Dataset name filters Explanation: This message is not currently in use. User response: No action is required. |
RSS0182I | Server id server name ip address port status Explanation: This is the heading message for the SERVERS command. User response: No action is required. |
RSS0183I | serverLocalName serverid serverIpAddress serverPort status Explanation: This is the detailed message for the SERVERS command. It gives details of the remote Resident Security Server server. User response: No action is required. |
RSS0184I | Userid ip address login activity keepalive Explanation: This is the heading message for the SESS command. User response: No action is required. |
RSS0185I | userid ipAddress login activity keepalive appid Explanation: This is the detailed message for the SESS command. It shows details of active Resident Security Server sessions. User response: No action is required. |
RSS0186I | SMF statistics (reset) resetDate resetTime Explanation: This message is returned by the SMF command and indicates the last time the SMF statistics were reset. User response: No action is required. |
RSS0187I | smfMetric value Explanation: This message forms part of a block of messages returned by the SMF command. It shows a specific SMF metric and its current value. User response: No action is required. |
RSS0188I | smfKey keyValue Explanation: This message forms part of a block of messages returned by the SMF command. It shows the address and key values associated with the SMF slave task. User response: No action is required. |
RSS0189I | The user userID has multiple sessions open Explanation: MultiSessionAlert is enabled and the user has multiple sessions (browser instances or tabs) open under the indicated user ID. User response: No action is required. |
RSS0190I | RSS task taskId Explanation: This message is a header message for a block of messages returned by the TASK command. User response: No action is required. |
RSS0191I | metricV alue Explanation: This message forms part of a block of messages returned by the TASK command. It shows the address and key values associated with the task indicated. User response: No action is required. |
RSS0192I | Dataspace dataSpaceName Explanation: This message provides the dataspace status. User response: No action is required. |
RSS0193I | metricValue Explanation: This message provides the dataspace status. User response: No action is required. |
RSS0194I | metricValue Explanation: This message provides information about the dataspace. User response: No action is required. |
RSS0195I | metricValue Explanation: This message provides information about the dataspace. User response: No action is required. |
RSS0196I | authorisation failed (resource profileName) Explanation: If CommandSecurity is on, this message is displayed when the command issuer does not have permission to RSM.RSSCMD.cmd[.arg]. User response: Ensure the relevant permissions have been granted. |
RSS0197I | no RSS TSO instances for rexx command Explanation: A REXX command was issued to Resident Security Server, but no RSS TSO address space instance is found. User response: Restart the product with the AUTOSTART TSO address space specified in the configuration parameters. If you can't determine the reason for the error, contact BMC Support. |
RSS0198I | Rexx command completed with no output Explanation: A REXX command was successfully routed to an Resident Security Server TSO instance, but the REXX ended without returning any messages to Resident Security Server. User response: No action is required. |
RSS0199I | End of display Explanation: This trailer was message issued to show that a block of command responses is complete. User response: No action is required. |
Comments
Log in or register to comment.