Reason:
This message indicates that the NMSAF security exit has failed user logon. The indicated user ID is unknown to the region, and no modeling could be performed.
The user ID is known to the external security system.
System Action:
The logon fails.
User Action:
Log on using a valid user ID.
Reason:
This message indicates that the NMSAF security exit has failed NetMaster user logon. A shortage of storage prevented the exit from obtaining required control blocks.
System Action:
The NetMaster logon fails.
User Action:
Allow the NetMaster region to obtain more storage.
Reason:
This message indicates that the NMSAF security exit has failed NetMaster user logon. The logon request was from TSO (using the NMLOGON TSO command).
The NMSAF exit parameter file has disabled auto-logon from TSO. A user ID and password must be provided.
System Action:
The NetMaster logon fails. The normal NetMaster logon panel is presented (this message is displayed there). Enter a user ID and password on this panel.
User Action:
Log on with a valid user ID and password.
Reason:
This message indicates that the NMSAF security exit has failed CA NetMaster user logon. The logon request was from ROF (the Remote Operator Facility) using the SIGNON command or an implied signon caused by use of the ROUTE command.
The target CA NetMaster is using the NMSAF security exit, and the initialization parameter file has set an option that requires ROF logons to supply a password.
System Action:
The ROF logon to CA NetMaster fails.
User Action:
Use the SIGNON command with the PASSWORD=password operand to sign on to the target CA NetMaster.
Note: The PASSWORD operand of the SIGNON command is not echoed to the panel or the CA NetMaster log.
Reason:
This message indicates that the NMSAF security exit has failed NetMaster user logon. The source of the logon request is not supported by the NMSAF exit.
Unsupported types include NetView CONNECT.
System Action:
The logon to NetMaster fails.
User Action:
This message is unlikely to appear unless you are using an unsupported NetMaster feature. Thus there is no specific user action.
If this message does occur, contact Technical Support.
Reason:
This message indicates that the NMSAF security exit has prevented use of the Password Change function.
The NMSAF initialization file contained a parameter that has disabled password change.
The NetMaster administrator has made this decision.
System Action:
The attempt to change a password fails.
User Action:
Contact your NetMaster administrator to determine why password change is not supported.
Possible reasons include:
- The external security system cannot handle password changes from NetMaster. - A password change on this MVS system may not propagate to other MVS systems.
Reason:
This message indicates that the NMSAF security exit has encountered an unexpected SAF (RACROUTE) error.
The RACROUTE macro SAF return code (aa), RACF return code (bb), and RACF reason code (cc) are displayed.
System Action:
The current NMSAF exit request fails. Requests include user logon, password change, and so on.
User Action:
Contact Technical Support with the following information:
- The request being attempted (logon, logoff, password change, and so on)
- The text of this message
- whether the problem is transient or permanent
It may also be helpful to restart NetMaster with NMSAF tracing enabled. This will help pinpoint the problem.
Reason:
This message indicates that the NMSAF security exit has been asked to verify a user but the user ID is not known to the external security system.
System Action:
The logon request fails.
User Action:
Retry the logon request with a valid user ID.
Reason:
This message indicates that the NMSAF security exit has been asked to verify a user, but the user ID has had all access revoked by the security administrator.
System Action:
The logon request fails.
User Action:
Contact your security administrator.
Reason:
This message indicates that the NMSAF security exit has been asked to verify a user, and the user ID's password has expired.
System Action:
The logon request is accepted, and a password change panel is presented.
If password change has been disabled by the NetMaster administrator, the logon request is rejected.
User Action:
If the password change panel is presented, change your password.
If password change has been inhibited, you will need to change your password using other facilities and attempt to log on to NetMaster again.
Reason:
This message indicates that the NMSAF security exit has been asked to verify a user, and the user ID's password is not correct.
This could be a logon request or a password change request, in which case the supplied current password is not correct.
System Action:
The logon or password change request fails.
User Action:
Retry the request with the correct password.
Reason:
This message indicates that the NMSAF security exit has been asked to change a password for a user.
The supplied new password is invalid
System Action:
The password change request fails.
User Action:
Retry the password change request with the correct password.
The new password may be invalid due to installation restrictions.
Reason:
This message indicates that an &SECCALL CALL request to the NMSAF security exit failed due to a missing or invalid first parameter.
System Action:
The &SECCALL CALL request fails.
User Action:
Correct the NCL procedure and retry.
Reason:
This message indicates that an &SECCALL CALL request to the NMSAF security exit failed due to an unrecognized first parameter.
System Action:
The &SECCALL CALL request fails.
User Action:
Correct the NCL procedure and retry.
Reason:
This message indicates that an &SECCALL CALL request to the NMSAF security exit failed.
The supplied parameter (request code) was recognized, but is not supported by this version of the NMSAF exit.
System Action:
The &SECCALL CALL request fails.
User Action:
Correct the NCL procedure and retry.
Reason:
This message indicates that the NMAF security exit was unable to initialize due to a shortage of storage.
System Action:
NetMaster will terminate.
User Action:
Provide a larger below-the-line region size for NetMaster.
Reason:
This message indicates that the NMSAF security exit was unable to initialize because the NetMaster version is prior to V5.0.
System Action:
NetMaster will terminate.
User Action:
Do not attempt to use the NMSAF security exit with earlier versions of NetMaster.
Reason:
This message indicates that the NMAF security exit was unable to initialize because of errors in the SXCTL input parameter file.
This message will be preceded by other messages detailing the errors.
System Action:
NetMaster will terminate.
User Action:
Correct the SXCTL file parameters.
Reason:
This message indicates that the NMSAF security exit was unable to initialize because the NetMaster region is not APF-authorized.
System Action:
NetMaster will terminate.
User Action:
Ensure the NetMaster load libraries are all APF authorized.
Also ensure any other load libraries in the STEPLIB concatenation are also APF authorized.
Reason:
This message indicates that the NMAF security exit was unable to initialize because the level of SAF (System Authorisation Facility) is not at least 1.9.
System Action:
NetMaster will terminate.
User Action:
Verify the level of SAF support in MVS.
MVS (RACF) SAF 1.9 or later has been in use since at least 1991.
Reason:
This message indicates that the NMAF security exit was unable to initialize because the a RACROUTE TOKENEXTR request failed.
System Action:
NetMaster will terminate.
User Action:
This message should not occur. However, non-IBM security systems may not correctly support the RACROUTE TOKENEXTR request.
Restart NetMaster. If the problem persists, add the following parameters to the SXCTL file:
TRACE=YES TRACESAF=YES
Also add an SXTRACE DD statement to the NetMaster JCL.
Send the diagnostic output from the trace to Technical Support. You should also provide details about the security product that you are using.
Reason:
This message indicates that the NMSAF security exit has detected an internal error.
This message displays the error code and is followed by additional diagnostic messages.
The exit then ABENDs, and NetMaster also ABENDs with a NetMaster internal abend code 268-01.
System Action:
After writing additional diagnostic messages, the security exit ABENDs, and NetMaster also ABENDs with an internal abend code 268-01.
User Action:
Contact Technical Support.
Reason:
This message follows the NSX290 message and provides additional diagnostic information.
System Action:
Refer to message NSX290.
User Action:
Refer to message NSX290.
Reason:
This message follows the NSX290 message and provides additional diagnostic information.
System Action:
Refer to message NSX290.
User Action:
Refer to message NSX290.
Reason:
This message follows the NSX290 message and provides additional diagnostic information.
System Action:
Refer to message NSX290.
User Action:
Refer to message NSX290.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The indicated value is not recognised as a valid parameter.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Correct the incorrect SXCTL line.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The indicated parameter requires a NO or YES as the value.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Correct the incorrect SXCTL line.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The indicated parameter value is not valid.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Correct the incorrect SXCTL.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The indicated parameter value is not valid. This parameter requires a valid name. A valid name is a 1-8 character value, the first character being alphabetic or national (@,#,$) and the remainder being alphanumeric or national.
A null value (meaning 'omitted') can be indicated by using a value of a single dash (-). This is the only otherwise invalid value permitted.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Correct the incorrect SXCTL line.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The indicated parameter value is not valid. This parameter requires a valid user name. A valid user name is a 1-8 character value with all characters being alphanumeric or national (@,#,$).
A null value (meaning 'omitted') can be indicated by using a value of a single dash (-). This is the only otherwise invalid value permitted.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Correct the incorrect SXCTL line.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The indicated parameter value is not valid. This parameter requires a valid resource. A resource name is a 1-20 character value. The exact syntax of this value is set by the security system.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Correct the incorrect SXCTL line.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The indicated parameter value is not valid. This parameter requires a valid model. A model name has the same syntax as a name. Refer to message NSX383 for the rules.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Correct the incorrect SXCTL line.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
The number of entries in the MODELGROUP list has been exceeded.
The location in the source file is also indicated.
System Action:
Parameter validation continues. Following this, NetMaster terminates.
User Action:
Reduce the number of MODELGROUP entries.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
An ABEND occurred when opening the SXCTL file.
System Action:
The region terminates.
User Action:
Examine other JOBLOG messages for the ABEND messages, and correct the problem.
Restart the region.
Reason:
This message is produced during processing of the SXCTL parameter file by the NMSAF security exit.
An I/O error occurred while reading the SXCTL file.
System Action:
NetMaster terminates.
User Action:
Ensure the SXCTL file is valid and accessible.
Reason:
The NMSAF security exit has failed user logon. The indicated user ID is unknown to the region, and no modeling could be performed.
The user ID is known to the external security system.
System Action:
The logon fails.
User Action:
Log on using a valid user ID.
Reason:
The NMSAF security exit has failed user logon. A shortage of storage prevented the exit from obtaining the required control blocks.
System Action:
The logon fails.
User Action:
Allow the NetMaster region to obtain more storage.
Reason:
The NMSAF security exit has failed user logon. The logon request was from TSO (using the NMLOGON TSO command).
The NMSAF exit parameter file has disabled auto-logon from TSO. A user ID and password must be provided.
System Action:
The logon fails. A logon panel is presented.
User Action:
Log on with a valid user ID and password.
Reason:
The NMSAF security exit has failed user logon. The logon request was from ROF (Remote Operator Facility) using the SIGNON command or an implied signon caused by use of the ROUTE command.
The target region is using the NMSAF security exit, and the initialization parameter file has set an option that requires ROF logons to supply a password.
System Action:
The ROF logon to the region fails.
User Action:
Use the SIGNON command with the PASSWORD=password operand to sign on to the target region.
Note: The PASSWORD operand of the SIGNON command is not echoed to the panel or the activity log.
Reason:
The NMSAF security exit has failed user logon. The source of the logon request is not supported by the NMSAF exit.
Unsupported types include NetView CONNECT.
Note: This message can appear if you are using an unsupported feature.
System Action:
The logon to the region fails.
User Action:
For assistance, contact Technical Support at HYPERLINK "http://ca.com/support" http://ca.com/support.
Reason:
The NMSAF security exit has prevented the use of the Password Change function.
The NMSAF initialization file contained a parameter that has disabled password change.
System Action:
The attempt to change a password fails.
User Action:
Contact your region administrator to determine why password change is disabled.
The following reasons are possible:
The external security system cannot handle password changes from the region.
A password change on this MVS system may not propagate to other MVS systems.
Reason:
The NMSAF security exit has encountered an unexpected SAF (RACROUTE) error.
The RACROUTE macro SAF return code (aa), RACF return code (bb), and RACF reason code (cc) are displayed.
System Action:
The NMSAF exit request fails. Requests include user logon, password change, and so on.
User Action:
For assistance, contact Technical Support with the following information:
The request being attempted (logon, logoff, password change, and so on)
The text of this message
Whether the problem is transient or permanent
Restarting the region with NMSAF tracing enabled can help to pinpoint the problem.
Reason:
The NMSAF security exit has been asked to verify a user whose ID is not known to the external security system.
System Action:
The logon request fails.
User Action:
Retry the logon request with a valid user ID.
Reason:
The NMSAF security exit has been asked to verify a user, but the security administrator has revoked all access for the user ID.
System Action:
The logon request fails.
User Action:
Contact your security administrator.
Reason:
The NMSAF security exit has been asked to verify a user, but the password specified with the user ID has expired.
System Action:
The logon request is accepted, and a password change panel is presented.
If password change has been disabled by the region administrator, the logon request is rejected.
User Action:
If the password change panel is presented, change your password.
If password change is disabled, you have to change your password using other facilities and attempt to log on to the region again.
Reason:
The NMSAF security exit has been asked to verify a user, but the password specified with the user ID is not correct.
This could be a logon request or a password change request, in which the specified current password is not correct.
System Action:
The logon or password change request fails.
User Action:
Retry the request with the correct password.
Reason:
The NMSAF security exit has been asked to change a password for a user.
The supplied new password is invalid.
System Action:
The password change request fails.
User Action:
The new password may be invalid due to site restrictions.
Retry the password change request with a correct password.
Reason:
An &SECCALL CALL request to the NMSAF security exit failed due to a missing or invalid first parameter.
System Action:
The &SECCALL CALL request fails.
User Action:
Correct the NCL procedure, and retry.
Reason:
An &SECCALL CALL request to the NMSAF security exit failed due to an unrecognized first parameter.
System Action:
The &SECCALL CALL request fails.
User Action:
Correct the NCL procedure, and retry.
Reason:
An &SECCALL CALL request to the NMSAF security exit failed.
The supplied parameter (request code) was recognized but is not supported by this version of the exit.
System Action:
The &SECCALL CALL request fails.
User Action:
Correct the NCL procedure, and retry.
Reason:
An &SECCALL CALL request to the NMSAF security exit failed.
The supplied parameter (request code) was recognized but is not supported by this version of the exit.
System Action:
The &SECCALL CALL request fails.
User Action:
Correct the NCL procedure, and retry.
Reason:
The NMAF security exit cannot initialize due to a shortage of storage.
System Action:
The region terminates.
User Action:
Provide a larger below-the-line region size for the region.
Reason:
The NMSAF security exit cannot initialize because the NetMaster version is prior to V5.0.
System Action:
The region terminates.
User Action:
Do not attempt to use the NMSAF security exit with earlier versions of NetMaster.
Reason:
The NMAF security exit cannot initialize because of errors in the SXCTL input parameter file.
This message is preceded by other messages detailing the errors.
System Action:
The region terminates.
User Action:
Correct the SXCTL parameters.
Reason:
The NMSAF security exit cannot initialize because the region is not APF-authorized.
System Action:
The region terminates.
User Action:
Ensure that the following load libraries are APF-authorized:
NetMaster load libraries
Other load libraries in the STEPLIB concatenation
Reason:
The NMSAF security exit cannot initialize because the level of SAF (system authorization facility) is earlier than 1.9.
System Action:
The region terminates.
User Action:
Verify the level of SAF support.
Reason:
The NMSAF security exit cannot initialize because a RACROUTE TOKENEXTR request failed.
This message should not occur. However, non-IBM security systems may not support the RACROUTE TOKENEXTR request correctly.
System Action:
The region terminates.
User Action:
Restart the region. If the problem persists, add the following parameters to the SXCTL file:
TRACE=YES
TRACESAF=YES
Also, add an SXTRACE DD statement to the region JCL job.
Contact Technical Support with the diagnostic output from the trace and details about the security product you are using.
Reason:
The NMSAF security exit has an internal error.
This message displays the error code and is followed by additional diagnostic messages.
System Action:
After writing additional diagnostic messages, the security exit abends. The region also abends with an internal ABEND code 268-01.
User Action:
For assistance, contact Technical Support at HYPERLINK "http://ca.com/support" http://ca.com/support.
Reason:
This message follows the NSX290 message and provides additional diagnostic information.
System Action:
See the NSX290 message.
User Action:
See the NSX290 message.
Reason:
This message follows the NSX290 message and provides additional diagnostic information.
System Action:
See the NSX290 message.
User Action:
See the NSX290 message.
Reason:
This message follows the NSX290 message and provides additional diagnostic information.
System Action:
See the NSX290 message.
User Action:
See the NSX290 message.
Reason:
This message indicates that an inbound File Transfer request is waiting for exclusive use of a dataset.
The name of the dataset is indicated in a following NSXA02 message.
System Action:
The File Transmission Request will wait until the dataset is available.
User Action:
Determine the cause of the dataset contention.
Reason:
This message follows an NSXA01 or NSXA03 message, and indicates the name of the dataset referred to in those messages
System Action:
See Messages NSXA01 and NSXA03.
User Action:
See Messages NSXA01 and NSXA03.
Reason:
This message indicates that an inbound file transfer request that was previously waiting for exclusive control of a data set can now continue.
The name of the data set is indicated in a following NSXA02 message.
System Action:
The File Transmission Request continues.
User Action:
None.
Reason:
The NMSECDSN exit detects an unsupported version of NetMaster.
This exit cannot be used with versions prior to NetMaster Version 7.0.
System Action:
The ALLOCATE request will fail unconditionally.
User Action:
Do not use the NMSECDSN exit with an incorrect version of NetMaster.
Reason:
This message is produced by the NMSECDSN exit during processing of an ALLOCATE command when invalid parameters are detected.
The most likely explanation for this is the use of the NMSECDSN exit when not using the NetMaster SAF security exit (As specified by the NetMaster JCL parm SEC=NMSAF).
System Action:
The ALLOCATE command fails unconditionally.
User Action:
Ensure that the correct security exit is in use.
Reason:
This message is produced by the NMSECDSN exit during processing of an ALLOCATE command when invalid parameters are detected.
The most likely explanation for this is the use of the NMSECDSN exit when not using the NetMaster SAF security exit (As specified by the NetMaster JCL parm SEC=NMSAF).
System Action:
The ALLOCATE command fails unconditionally.
User Action:
Ensure that the correct security exit is in use.
Reason:
This message is produced by the NMSECDSN exit during processing of an ALLOCATE command when invalid parameters are detected.
The most likely explanation for this is the use of the NMSECDSN exit when not using the NetMaster SAF security exit (As specified by the NetMaster JCL parm SEC=NMSAF).
System Action:
The ALLOCATE command fails unconditionally.
User Action:
Ensure that the correct security exit is in use.
Reason:
The NMSECDSS exit produces this message during the processing of a request when invalid parameters are detected.
The most likely explanation is the use of the NMSECDSS exit when not using the region SAF security exit (as specified by the JCL parameter SEC=NMSAF).
System Action:
The Dataset Services request fails unconditionally.
User Action:
Ensure that the correct security exit is in use.
Reason:
This message is produced by the NMSECDSS exit during processing of a Dataset Services request when invalid parameters are detected.
The most likely explanation for this is the use of the NMSECDSS exit when not using the NetMaster SAF security exit (As specified by the NetMaster JCL parm SEC=NMSAF).
System Action:
The Dataset Services request fails unconditionally.
User Action:
Ensure that the correct security exit is in use.
Reason:
This message is produced by the NMSECDSS exit during processing of a Dataset Services request when invalid parameters are detected.
The most likely explanation for this is the use of the NMSECDSS exit when not using the NetMaster SAF security exit (As specified by the NetMaster JCL parm SEC=NMSAF).
System Action:
The Dataset Services request fails unconditionally.
User Action:
Ensure that the correct security exit is in use.
Reason:
This message is produced by the NMSECDSS exit during processing of a Dataset Services request when invalid parameters are detected.
The most likely explanation for this is the use of the NMSECDSS exit when not using the NetMaster SAF security exit (As specified by the NetMaster JCL parm SEC=NMSAF).
System Action:
The Dataset Services request fails unconditionally.
User Action:
Ensure that the correct security exit is in use.
Reason:
This message is produced by the NMSECDSS exit during processing of a Dataset Services request. The current user's SAF user ID and the pre-registered HFS user ID do not match.
This can only occur for NetMaster background user IDs when the security exit has nominated a different SAF user ID, and the SYSPARM HFSUSEC=YES is in effect. (SYSPARMS HFSUSEC=YES causes NetMaster to internally register the NetMaster user ID as the HFS user ID).
System Action:
The Dataset Services request fails unconditionally.
User Action:
Do not use SYSPARMS HFSUSEC=YES with the NMSECDSS and SEC=NMSAF exits.
Reason:
This message is produced by the NMSECDSS exit during processing of a Dataset Services request. An attempt to perform HFS security initialization failed. The BPX1SEC system call return and reason codes are displayed.
These codes can be found in the Unix System Services Messages and Codes manual.
System Action:
The Dataset Services request fails unconditionally.
User Action:
Examine the return and reason codes to determine the cause of the failure.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|