Reason:
Displayed when a user is cancelled by a CANCEL command.
System Action:
This message is displayed for a short period only.
User Action:
None.
Reason:
Displayed when a user is disconnected by a DISCONN command or timeout action.
System Action:
This message is displayed for a short period only.
User Action:
None.
Reason:
Displayed when a user is cancelled by a timeout action.
System Action:
This message is displayed for a short period only.
User Action:
None.
Reason:
Displayed when a user logs off from the system.
System Action:
This message is displayed for a short period only.
User Action:
None.
Reason:
A user has selected a Primary Menu function for which they are not authorized.
System Action:
The selection is rejected.
User Action:
Contact your systems administrator.
Reason:
A Primary Menu function was selected but this SOLVE system is not configured for the function.
System Action:
The selection is rejected.
User Action:
None.
Reason:
Confirms a successful change of password.
System Action:
None.
User Action:
The new password will be required from now on eg. for logging on and for unlocking LOCKed screens etc. If an external security manager is in use the new password may also apply to other applications and subsystems.
Reason:
The primary menu NCL procedure has terminated without specifying any direct action to be taken. This may reflect an NCL coding error or logic error.
System Action:
The line messages associated with the primary environment are displayed.
User Action:
Press the END key (PF03/15) to redrive the primary menu NCL. Press the RETURN key (PF04/16) to close the window.
Reason:
Issued when a terminal under the control of EASINET is passed successfully to another VTAM application as a result of a logon request entered at the terminal.
System Action:
None.
User Action:
None.
Reason:
An unidentified logon request was made at a terminal under EASINET control.
System Action:
None.
User Action:
Refer to the procedures set down by your installation for logging on to your required application. Correct and re-enter.
Reason:
A VTAM INQUIRE macro failed during the attempt to pass the terminal to the requested application. SOLVE also assumes request failure if no response is received from VTAM within 30 seconds.
System Action:
The terminal remains under the control of EASINET. If VTAM sense codes are received message N20212 will go to the activity log, giving specific return code information. If a timeout occurred, N20214 is written to the activity log.
User Action:
Retry the logon request. If the condition persists, the return code information logged in message N20212 should be investigated.
Reason:
A logon request was made from a terminal under EASINET control, but the selected application is not running.
System Action:
The terminal remains under EASINET control.
User Action:
Determine why the application is not running and/or retry the request later.
Reason:
An attempt to log on to an application failed because it will not allow any logons.
System Action:
The logon request is ignored.
User Action:
Check the status of the application and retry the logon when logons are allowed.
Reason:
An attempt to logon to an application failed because the VTAM CLSDST PASS operation failed.
System Action:
The logon request is ignored and the terminal remains under EASINET control. Message N20211 is written to the activity log providing specific error information.
User Action:
Contact your systems administrator.
Reason:
An attempt was made to log on to an application that is undefined or inactive. The DEFLOGON used is identified by P1 and the associated application LU name is P2.
System Action:
The logon request is rejected.
User Action:
Consult your systems administrator. Ensure that the application is defined to VTAM and that the DEFLOGON specifies the required LU name.
Reason:
A logon request specified the name of a logical unit that:
- Is not an application program, or
- Is an application program in another domain, but the domain is not currently accessible (for example, the cross-domain resource-manager is not active)
P1 is the string that identifies the DEFLOGON used and P2 is the target application LU name.
System Action:
The logon request is ignored.
User Action:
If the logical unit is not an application, the DEFLOGON entry pertaining to the logon request is wrong and you must change it. In the case of an inaccessible domain, retry the request later when communications are re- established.
Reason:
A logon request failed because the LOGMODE table entry specified in a DEFLOGON entry, or &LOGON statement, is not known to VTAM.
System Action:
The request is ignored.
User Action:
Consult your systems administrator to enable the DEFLOGON entry to be changed, or the &LOGON statement to be corrected.
Reason:
Written to the activity log with message N20207. Gives specific VTAM return code, feedback and sense information.
System Action:
None.
User Action:
Interpret the information using the VTAM Programming manual. Refer to the related message N20207.
Reason:
Written to the activity log with message N20204. Gives specific VTAM return code, feedback and sense information.
System Action:
None.
User Action:
Interpret the information using the VTAM Programming manual. Refer to the related message N20204.
Reason:
An attempt was made to log on to an application that has been suspended using the SUSLOGON command.
System Action:
The logon is denied.
User Action:
Retry the logon later when the application is available.
Reason:
Written to the activity log when a VTAM INQUIRE APPSTAT has not completed within an expected interval.
System Action:
The associated function is failed as not completed successfully.
User Action:
Refer the details to your systems administrator for problem determination.
Reason:
An attempt was made to log on to an application that has been suspended using the SUSLOGON command. The text, P1 , indicates the reason for the suspension set by the issuer of the SUSLOGON command.
System Action:
The logon is denied.
User Action:
Retry the logon when the application has been made available.
Reason:
An attempt was made to access an application that is undefined. A DEFLOGON command, that matches the first word of the MAI-FS logon string, has not been found.
System Action:
The session request is terminated.
User Action:
Correct the application name used in the logon request. If necessary, consult your systems administrator.
Reason:
The session with an EASINET controlled terminal has been lost for a reason identified as recoverable by SOLVE.
System Action:
The system will try to re-establish the session with the terminal. Attempts of this nature are reported to Monitor status operators.
User Action:
None.
Reason:
A dynamic allocation request specified an invalid dataset name.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
A request was made for dynamic allocation of a member of a generation data group but the system was unable to resolve the absolute dataset name of the specified member.
System Action:
The allocation request is rejected.
User Action:
None.
Reason:
A request for dataset replace was made. This involves deleting the dataset and subsequently re-creating it. The dataset to be deleted could not be found.
System Action:
This message is written to the log as an informational message only.
User Action:
Refer to Data Management SPL for explanation of CAMLST LOCATE return codes.
Reason:
The CAMLST SCRATCH macro has failed with the return codes as described.
System Action:
The request fails.
User Action:
Refer to Data Management SPL for explanation of CAMLST SCRATCH return codes.
Reason:
The CAMLST CATALOG macro has failed with return codes as described.
System Action:
The dataset is not uncatalogued.
User Action:
Refer to Data Management SPL for explanation of CAMLST CATALOG return codes.
Reason:
This message appears on VOS3 systems only. It confirms that terminal aaaaaaaa which has just connected to SOLVE is a bbbbbb device type. bbbbbbb is either 3270 or 560/20.
System Action:
None.
User Action:
None.
Reason:
A logon was attempted but no userid was entered.
System Action:
None.
User Action:
Enter userid and password.
Reason:
A logon was attempted but no password entered.
System Action:
None.
User Action:
Enter userid and password.
Reason:
A logon was attempted for an undefined USERID.
System Action:
The logon is rejected.
User Action:
Correct and re-enter, or have your USERID defined to SOLVE.
Reason:
The password entered during a logon attempt was not valid for the USERID.
System Action:
The logon is rejected.
User Action:
Correct and re-enter.
Reason:
The maximum number of password retries was exceeded during a logon attempt.
System Action:
The logon is rejected.
User Action:
See your systems administrator.
Reason:
This message is logged and sent to all monitor status users identifying users as they logon to SOLVE.
user-class: the user type, classed as LOCAL, REMOTE, SYSTEM, TSO, CONSOLE, NET/VIEW, VM/OPER or APPC. userid: the userid who has logged on. nodename: the terminal node name at which the user has logged on. In the case of an APPC user a nodename of *GLOBAL* indicates that any subsequent APPC logon requests for the same user will use this region irrespective of the node from which the logon request originates. username: the name of the user taken from their UAMS definition.
System Action:
None.
User Action:
None.
Reason:
A logon has completed, but since the USERID password has expired, the system requires that it be changed. This was not done so the USERID is logged off.
System Action:
None.
User Action:
Logon again and change your password as requested.
Reason:
This message is logged to users with monitor status to indicate that the specified user has logged off. user-class identifies the class of user (see message N20E05). usertype indicates whether the user has multiple signon authority; values returned are MULTI or SINGLE.
System Action:
None.
User Action:
None.
Reason:
The specified userid has been forcibly logged off from the specified node because the VTAM session has failed or been terminated due to Operator action.
System Action:
The userid is logged off.
User Action:
If disconnection has occurred as indicated by the message then the user may wish to logon and re-connect to the lost session.
Reason:
A logon attempt, in which the user passed the userid and password as logon 'userdata' failed because the password specified was wrong.
System Action:
The SOLVE logo is displayed and this message prompts the user to re-enter both userid and password.
User Action:
Re-enter, or logoff.
Reason:
A logon attempt is in progress. A 1 to 8 character userid is required to identify the user to the system.
System Action:
If possible the logo panel is displayed prompting for input.
User Action:
Enter your userid, or logoff.
Reason:
A logon attempt is in progress. A 1 to 8 character password is required to confirm the identity of the user to the system.
System Action:
If possible the logo panel is displayed prompting for input.
User Action:
Enter your password, or logoff.
Reason:
A logon attempt has been rejected. The message text is that returned by the system or user security system.
System Action:
The logon is rejected and the logon panel is displayed.
User Action:
Re-enter your userid and password, or logoff.
Reason:
During user logon, the user definition time zone name was not found in the TIMEZONE table.
System Action:
The system time zone is used (name is SYSTEM).
User Action:
Ensure that time zone names are set up during system initialization using the TIMEZONE command.
Reason:
An LU1 logon has been rejected because the user is not authorised for Operator Control Services.
System Action:
The logon is rejected.
User Action:
Contact your installation help desk to arrange OCS authorisation for your userid.
Reason:
An LU1 logon has completed successfully.
System Action:
None.
User Action:
Review broadcast messages if any. Proceed with work.
Reason:
A product ( P1 ), specified using the PROD= JCL parameter, is allowed only if another product is also specified. The prerequisite product ( P2 ) is either the name of a specific product or *Multiple to indicate that the product requires any one of multiple products as specified in the product documentation.
System Action:
The region terminates.
User Action:
Change the RUNSYSIN member to specify the correct PROD= values.
Reason:
A product ( P1 ), specified using the PROD= JCL parameter, is not allowed on the current operating system.
System Action:
The region terminates.
User Action:
Change the RUNSYSIN member to remove the relevant PROD= value. Contact your product supplier for product availability information.
Reason:
A product ( P1 ), specified using the PROD= JCL parameter, is not allowed on the version and maintenance level ( P2 ) of Security and System Services.
System Action:
The region terminates.
User Action:
Change the RUNSYSIN member to remove the relevant PROD= value. Contact your product supplier for product availability information.
Reason:
A product ( P1 ), specified using the PROD= JCL parameter, is not allowed to run concurrently with product P2.
System Action:
The region terminates.
User Action:
Remove one of the two PROD= values from the RUNSYSIN member. Contact your product supplier for product availability information.
Reason:
The initialization process for CA Common Services has not been run since the last IPL. This product requires the services for some functions, including LMP checking.
The services are initialized by the CAS9 started task, which is normally run as part of your system IPL process.
System Action:
Some functions, such as LMP checking, are not operational.
User Action:
Contact your systems administrator.
Reason:
A product ( P1 ), with LMP code P2 , has been registered with the Licence Manager Program (LMP) component of Resource Initialization Manager (CAIRIM). CAIRIM will monitor product usage.
System Action:
None
User Action:
None, for information only
Reason:
The P1 product (product code P2) failed registration with the LMP component of the Resource Initialization Manager (CAIRIM). P3 is one of the following failure reasons:
Indicates that CA Common Services initialization process has not been run.
Indicates an unexpected LMP error. xx is the LMP return code in hexadecimal.
System Action:
None.
User Action:
If the reason is CAS NOT RUN, review the N21302 message. For other reasons, contact Technical Support.
Reason:
A product ( P1 ), with LMP code P2 , has been registered with the Licence Manager Program (LMP) component of Resource Initialization Manager (CAIRIM). However, the product will expire within 30 days.
System Action:
None
User Action:
Contact your product supplier to obtain a new licence key.
Reason:
The product is registered with License Management Program (LMP) of CAIRIM, but its LMP key has either expired or is not valid for this CPU.
P1 is the product name key. The key is in a PROD statement in the RUNSYSIN member.
P2 is the product LMP code.
System Action:
None.
User Action:
Check that the LMP key registered for the product is correct:
Reason:
A DEFLOGON command could not be processed because of a storage shortage.
System Action:
The command fails.
User Action:
Consider increasing the SOLVE region or partition size. Investigate possible cause of storage shortage.
Reason:
When the terminal, aaaaaaaa, connects to the region, a Read Partition Query was sent to the terminal to obtain information about its characteristics. The Query Reply, which was sent from the terminal to the region, contains invalid data. This message precedes a hexadecimal dump of the Query Reply.
System Action:
The logon of the terminal proceeds, but the region cannot use some abilities of the terminal such as extended color or extended highlighting.
User Action:
The dump of the invalid Query Reply follows this message. See this dump of the Query Reply to determine why it is invalid.
Reason:
This message is preceded by N21801. This is the hexadecimal dump of the invalid Query Reply.
System Action:
None.
User Action:
None.
Reason:
This message is the title line of the SHOW SYSPARMS display.
System Action:
None.
User Action:
None.
Reason:
This message is produced for each SYSPARM displayed by the SHOW SYSPARMS command. It includes the following information:
P1 - The SYSPARM operand name.
P2 - The current value.
P3 to P5 Indicates how the value was set. Possible values for P3 are: DEFAULT - The value is the default.
OCS - The value was set by a command entered in OCS.
P4 is the user ID that executed the command.
ROF - The value was set by a command entered in a remote region.
P4 is the user ID that executed the command.
P5 is the link name of the remote region.
COMMAND ENTRY - The value was set by a command entered using the Command Entry function.
P4 is the user ID that executed the command.
BG COMMAND - The value was set by a command entered from a background environment, for example, as a result of a time command.
P4 is the user ID of the background environment.
PROCEDURE - The value was set by an NCL procedure.
P4 is the procedure name.
Note: A procedure name of SYSPARMS indicates that a command replacement for the SYSPARMS command is in effect. For more information, see the CMDREPL Customizer parameter group and the SYSPARMS CMDREPL command.
CUSTOMIZER - The value was set when a Customizer parameter group was actioned.
P4 is the name of the parameter group.
Note: When a SYSPARM operand is set by Customizer, it cannot be updated using OCS, Command Entry, or an NCL procedure. The SYSPARM operand must be updated using the Customizer parameter group to ensure that values remain synchronized. Synchronization checks can be bypassed using SYSPARMS SYSPGCHK=NO; however, this is not recommended except in an emergency situation because there is no synchronization with the Customizer parameter group. If used, we recommended that you issue SYSPARMS SYSPGCHK=YES (the default) as soon as possible to reinstate synchronization checking.
System Action:
None.
User Action:
None.
Reason:
A storage shortage has prevented processing of the SHOW SYSPARMS command.
System Action:
The command is not processed.
User Action:
Retry the command. If the problem persists, contact your systems administrator.
Reason:
A CLSDST operation could not be performed to pass a terminal to a target application because of a temporary storage shortage.
System Action:
The logon request fails.
User Action:
Retry. If the condition persists refer to your systems administrator.
Reason:
A logon request was issued for an active application and the terminal was passed successfully. However, the application subsequently rejected the session and SOLVE re- acquired the terminal.
System Action:
The logon request fails.
User Action:
Determine why the application rejected the session. In the case of systems such as CICS or IMS, the terminal may not be defined properly.
Reason:
A logon request was issued for an active application and the terminal was passed to it successfully. However, the terminal subsequently rejected the session and SOLVE re- acquired the terminal.
System Action:
The logon request fails.
User Action:
Determine why the terminal rejected the session. The application could have supplied invalid bind parameters.
Reason:
A logon request was issued for an active application. The terminal
P1 is now being passed to application P2 . In VTAM terms, a CLSDST/PASS is about to be issued. The logmode specified for the session is P1 . The word DEFAULT indicates no logmode is specified and that the terminal's default logmode will be used.
System Action:
The logon request proceeds. Subsequent messages indicate the result of the operation.
User Action:
None.
Reason:
A logon request was issued for an active application and the terminal was passed to it successfully. However, the session between the terminal and the application was not established successfully, and EASINET re-acquired the terminal.
System Action:
The logon request fails and EASINET processing resumes.
User Action:
The error condition may be temporary - retry the logon request. If necessary examine the log for related messages which detail the error that occurred.
Message N22712 is written to the activity log to provide various reason and sense code information, which should be examined to determine the exact cause of the failure.
Message N22731 indicates that the communication subsystem does not support Third Party Notify for this application. Modification of the application's DEFLOGON definition to specify NOTIFY=NO may be used to bypass this condition.
Message N22732 indicates that an attempt to logon using a specific logmode failed due to a queued session request. Retry the logon request.
Reason:
A logon request is issued for an application which is not active.
System Action:
The logon request fails.
User Action:
Retry when the application is active.
Reason:
A logon request was issued for an active application and the terminal luname was passed to that application. However, the session between the terminal and application did not establish successfully, and SOLVE attempted to re-acquire the terminal. During this re- acquisition, a VTAM SIMLOGON macro failed.
System Action:
The re-acquisition fails.
User Action:
Firstly, determine the cause of the session establishment failure. Message N22712 will detail the reason and sense codes. Secondly, determine the cause of the SIMLOGON failure. The VTAM return code, feedback and sense information in this message indicate the cause and should be used in reference to the VTAM Programming manual. If the terminal should be connected to the EASINET component, an OPNDST command should be issued from an OCS window.
Reason:
A logon request was issued for an active application applname and the terminal luname was passed to it successfully. However, the session between the terminal and the application was not established successfully.
System Action:
The region attempts to reacquire the terminal and issues an error message to the user.
User Action:
Determine the cause of the failure. The reason and sense codes that are provided in this message are obtained from the information that is given to the region NSEXIT by VTAM. For information about NSEXIT, see the VTAM Programming guide. The region provides a more meaningful message for certain failure conditions (see messages N22703 and N22704).
Reason:
A logon request was issued for an active application and the terminal luname was passed to that application. However, the session between the terminal and application did not establish successfully, and SOLVE attempted to re-acquire the terminal to notify the user. However, this re-acquisition failed.
System Action:
The re-acquisition fails.
User Action:
Determine if the terminal should be connected to the EASINET component, and if so issue an OPNDST command from an OCS window to connect it. The re-acquisition attempt could have failed because another application acquired the terminal, or because the terminal became otherwise unavailable or inactive.
Reason:
A logon request was issued for an active application and the terminal luname was passed to that application. However, the session between the terminal and application did not establish successfully, and SOLVE attempted to re-acquire the terminal. During this re- acquisition, a VTAM OPNDST macro failed.
System Action:
The re-acquisition fails.
User Action:
Firstly, determine the cause of the session establishment failure. Message N22712 will detail the reason and sense codes. Secondly, determine the cause of the OPNDST failure. The VTAM return code, feedback and sense information in this message indicate the cause and should be used in reference to the VTAM Programming manual. If the terminal should be connected to the EASINET component, an OPNDST command should be issued from an OCS window.
Reason:
A logon request was issued for an active application and the terminal luname was passed to that application. However, the session between the terminal and application did not establish successfully, and SOLVE re-acquired the terminal to notify the user.
System Action:
The EASINET procedure regains control after the &LOGON statement with an error message in the &SYSMSG variable.
User Action:
Other messages detail the cause of the session failure.
Reason:
A logon attempt was received from an LU specifying BIND parameters that indicated that it was not an LU type 1,2 or 3 or LU 0 3277 device.
System Action:
The system rejects the logon attempt.
User Action:
Check the BIND parameter definitions for the device if it is a terminal that should be able to logon to SOLVE.
Reason:
A 3270 device rejected a BIND issued by EASINET. The system will retry the BIND to attempt to connect the terminal as a model 2 (24 x 80) terminal.
System Action:
The system retries the BIND.
User Action:
Check the BIND parameter definitions for the device if it is a terminal that should be able to logon to SOLVE.
Reason:
Connection of the nominated terminal failed because the LOGMODE table entry lgmdname is not defined to VTAM. SOLVE will retry the connection with a default set of BIND parameters.
System Action:
The system retries the BIND.
User Action:
Check the MODE TABLE entry specified for the terminal.
Reason:
A previous attempt to pass the terminal to another application using a VTAM CLSDST/PASS operation requested that VTAM provide notification to indicate the success or otherwise of the operation (this is referred to as Third Party Notify). VTAM has not provided notification and as such SOLVE cannot determine if the operation was successful.
System Action:
The current logon attempt is not completed. The EASINET procedure which issued the original CLSDST/PASS request via the &LOGON verb regains control of the terminal, and this error message is available in the &SYSMSG system variable after the &LOGON verb completes.
User Action:
Investigate the cause of the failure of VTAM to provide Third Party notification. Some versions of VTAM do not support the Third Party Notify feature. If this is the case, the use of this feature can be avoided by use of a SYSPARMS VTAMNTFY=NO command.
Reason:
When a terminal connected to a SOLVE system requests logon using a Logmode other than the current one, SOLVE uses a VTAM CLSDST macro to terminate the current session, then a VTAM SIMLOGON macro to create a new session with the requested Logmode. After the CLSDST macro was issued, SOLVE detected that the terminal had logged on again before the SIMLOGON could be issued.
System Action:
The current logon attempt is not completed. The EASINET procedure which issued the original &LOGON request regains control of the terminal and this error message is available in the &SYSMSG system variable after the &LOGON verb completes.
User Action:
This occurrence indicates that VTAM has caused the terminal to be logged on (possibly because of LOGAPPL) when SOLVE had indicated the session with the terminal was not required. This has prevented SOLVE from reacquiring the terminal with the specified logmode. This error should be reported to your system administrator.
Reason:
An EXIT was attempted from OCS. However, there is an NCL process active. 'Reason' contains the reason an exit was not performed. Either: EXIT PREVENTED BY PROFILE OPTION or RE-ENTER EXIT TO FORCE OCS TERMINATION An exit from OCS is not performed.
System Action:
None.
User Action:
Action depends on the reason. Either re-enter EXIT or terminate the NCL process.
Reason:
A temporary storage shortage prevented the user from entering Operator Console Services mode.
System Action:
None.
User Action:
Retry. Refer to your systems administrator if the condition persists.
Reason:
MSGPROC could not be invoked for the OCS window because of a storage shortage.
System Action:
None.
User Action:
Consider increasing the SOLVE region or partition size.
Reason:
The statement in error has wrong syntax or a required variable has been omitted.
System Action:
The procedure terminates.
User Action:
See the NCL Reference for the syntax of the statement.
Reason:
The failing statement specified a duplicate variable name.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The procedure has failed because of a storage shortage.
System Action:
The procedure terminates.
User Action:
Consider increasing the SOLVE region or partition size.
Reason:
An invalid length or skip value is specified.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The failing statement contains invalid LIST syntax or an invalid variable.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The failing statement contains a reserved keyword (e.g an attempt to modify a system variable).
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
You cannot perform generic processing of all global variables in the system. A generic processing request must specify a generic prefix longer than the global variable prefix so that only a subset of all global variables is selected.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
Issued in response to a SHOW NCLVARS command. The message contains:
NAME The name of the variable.
LENGTH The length of the variable.
MODF# Either blank or a number in the range 1 to 255. A value indicates the variable as having being modified by a system service eg. Panel Services, NDBGET.
ATTR Indicates the attributes of the variable. Either:
Blank- No special attributes set.
MOD - The variable has been modified using the ASSIGN OPT=SETMOD function.
ERR - The variable has been modified using the ASSIGN OPT=SETERR function.
HEX - The variable contains non-displayable hexadecimal data.
DATA Up to the first 12 bytes of data contained in the variable. If LIST=ALL is used then the second line contains the complete data of the variable.
System Action:
None.
User Action:
None.
Reason:
aaaa does not conform to the rules for variable names.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
Dynamic generation of a variable name using aaaa would cause an invalid name to be generated.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
SYSPARM NCLGBTRC has been set to cause tracing of varname. The trace is of a GLOBAL variable (vartype). The contents of the variable have been updated by the named user using procedure xxxx. The first 12 bytes of the data are displayed.
System Action:
None.
User Action:
Verify that the update is valid. When tracing is no longer required issue 'SYSPARM NCLGBTRC=', ie. without a value to terminate tracing.
Reason:
An operation was specified using a global variable (ie a variable whose name begins with the global variable prefix as defined by the NCLGLBL SYSPARM) but the operation is only valid for local variables. For example, setting or resetting the errfld or modified field attributes of a variable using ASSIGN OPT=SETERR/RESETERR etc.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The data being moved into a buffer is too large for the buffer. For example, in a file operation the data exceeds the maximum record size.
System Action:
Operation is not completed.
User Action:
Reduce the length of data used in the operation.
Reason:
An attempt was made to reference an NCL variable that is specified as containing hexadecimal data. The data has either invalid hexadecimal CHARACTERS or an invalid LENGTH (the length must be even) as indicated in reason.
System Action:
The NCL procedure is terminated.
User Action:
Correct, and retry.
Reason:
This message is the title line for a variable display. The variables displayed are sorted into ascending alphabetic name order and show attributes (Modfld, Errfld, Outfld, Hex) and data. This display is produced by the DEBUG DISPLAY command. Refer to description of message N23318 for more information.
System Action:
None.
User Action:
None.
Reason:
This message is the detail line for a variable display produced by the DEBUG DISPLAY command. The meanings of the fields are as follows:
variable - the name of the variable
len - the length of data contained in the variable
modf# - the current modfld order for the variable
meoh - attributes assigned to the variable
m - if 'Y' variable has MOD attribute set (otherwise '-')
e - if 'Y' variable has ERR attribute set (otherwise '-')
o - if 'Y' variable has OUT attribute set (otherwise '-')
h - if 'Y' variable contains HEX data (otherwise '-')
data - the contents of the variable
- If FORMAT=CHAR was entered on the DEBUG DISPLAY command the data contents are shown in character format.
- If FORMAT=HEX was entered on the DEBUG DISPLAY command the data contents are shown in hexadecimal format.
- If FORMAT=DUMP was entered on the DEBUG DISPLAY command the data contents are shown in a hex/character dump format in message N23319 which follows this message.
System Action:
None.
User Action:
None.
Reason:
This message is produced by the DEBUG DISPLAY command when the FORMAT=DUMP operand is entered. The message contains a hex and character dump format display of the data in the specified MDO. The meanings of the fields are as follows:
+ooo - shows the offset into MDO at which the data starts
xxxxxxxx - the hexadecimal format of the data
cccccccc - the character format of the data
System Action:
None.
User Action:
None.
Reason:
A generic operation which creates variables by appending a suffix to a supplied prefix attempted to create a token name longer than 12 characters. e.g. VARS=XXXXXXXXXX* RANGE=(1,100) aaaaaaaaaaaaaaaaa = Invalid variable name.
System Action:
Procedure is flushed.
User Action:
Modify statement in error so that variable names generated don't exceed 12 characters, either by using a shorter prefix, or a different range or generic suffix set.
Reason:
The maximum number of concurrent NCL processes allowed for any user is set by the NCLUMAX value. You have attempted to start more than this
System Action:
User Action:
Reason:
A START command was issued but the SERVER operand value server-name is not unique within the scope provided.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
This is the standard termination message for any process that fails. The NCLID of the process is yyyyyy.
System Action:
None.
User Action:
Determine the reason for procedure termination from other error messages that accompany this message.
Reason:
The process has failed to execute because of a storage shortage.
System Action:
The procedure terminates.
User Action:
If the condition persists, increase the SOLVE region or partition size.
Reason:
This message indicates that an object services method procedure invoked via &OSCALL has terminated due to an error.
System Action:
None.
User Action:
Investigate the reason for the failure of the object services method procedure. Other messages which precede this message will indicate the type of error encountered.
Reason:
A general termination message; the failing statement follows this message.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
If WAIT is coded as the last statement in a procedure it is ignored and the procedure is ended.
System Action:
The procedure terminates.
User Action:
None.
Reason:
This message appears if JCL PARMS TRACE1= includes GT1TRDRR (X'20'). The NCL procedure membername from the library memberlib has been dropped from the NCL retain queue because of one of the following reasons:
Members are dropped from the retain queue in least used order.
System Action:
None.
User Action:
None.
Reason:
The NCL statement syntax is incorrect.
System Action:
The NCL procedure is terminated.
User Action:
Check the syntax of the statement in error, correct and retry.
Reason:
The prefix specified for generic variable name processing is too long for the range suffix to be appended.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
An NCL statement which contains the ARGS and RANGE operands has specified a range which includes the system variable 0.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An NCL statement which contains the FILE ADD PRTCNTL= operand has invalid options. For example, nulls in list, duplicates in list, too many entries or a syntax error. e.g. prtcntl=(skip2,skip1) should generate this error.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An invalid value has been specified for the ROUTCDE operand on either an EVENT verb in an NCL procedure, or on a PROFILE EDS command.
System Action:
The NCL procedure terminates, or the PROFILE command fails.
User Action:
Correct operand value and retry. An example of valid syntax is: ROUTCDE=(1,2,3,4).
Reason:
The RESOURCE operand on an EVENT NCL statement has an invalid value. The RESOURCE operand is specified as a single resource, or a pair of resources. e.g. RESOURCE=(luname,userid).
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The prefix specified for generic variable name processing is too long for the range suffix to be appended.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
The prefix specified for generic variable name processing is too long.
System Action:
The NCL procedures is terminated.
User Action:
Correct and retry.
Reason:
ASSIGN has a processing limit of 256 generic variables in any one operation.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
An ASSIGN NCL statement has specified an incorrect NONULLS or NORESET operand.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
If parentheses are used to delimit the evaluation order of an arithmetic statement an equal number of left and right parentheses, correctly paired, is required.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
Too many operators (+, - * etc) have been coded in the statement for the number of operands to be operated on.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
Too many operands have been coded in the statement for the number of operators (+, - * etc).
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
An arithmetic statement is processed as a sequence of simple expressions. There is a limit of 32 simple expressions per statement.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
An arithmetic statement is processed as a sequence of simple expressions. There is a limit of 32 simple expressions per statement.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
The failing statement had an expression, the result of which was too large to be held in an 8-byte floating-point register ( CONTROL REAL) or a 4-byte binary register ( CONTROL INTEGER).
System Action:
The procedure terminates.
User Action:
Correct and retry. of NCL arithmetic.
Reason:
An attempt was made to divide by zero.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
An expression yielded a number greater than the largest supported positive or negative value.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
Each operand in an arithmetic expression must be separated from the next by an arithmetic operator.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
A variable in an arithmetic expression does not have a numeric value.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
The arithmetic statement cannot be resolved.
System Action:
The NCL procedure is terminated.
User Action:
Check the logic of the statement.
Reason:
Each operator in an arithmetic expression must be followed by an operand.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
The failing statement had an expression containing the remainder operator (\), however the expression contained floating-point values or
CONTROL REAL was in effect.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The nominated statement contains an ELSE verb that is either not on its own statement or is logically inconsistent.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
&DOEND statements to close preceding &DO, &DOUNTIL or &DOWHILE groups are missing.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
An &DOEND statement was encountered, however there was no corresponding
&DO statement preceding it.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
A statement was found which does not make sense as the statement is the result of an IF, ELSE or ENDAFTER statement. For example, ` IF A EQ
B THEN ELSE'.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An &ELSE statement was encountered where the previous statement was not an &IF statement or the closure of an &DO .. &DOEND group which was the executable part of an &IF statement.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
A statement label (that is, a valid name preceded by a period character `.') was found on an &ELSE statement. It is illegal to branch directly to the &ELSE portion of an &IF statement, therefore labels are not allowed on the &ELSE statement.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An &ELSE keyword was encountered on the same line as an &IF statement. The &ELSE keyword must be on a separate statement.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
A valid NCL keyword was encountered at the beginning of a statement but that keyword is not valid at the beginning of a statement. For example, the &THEN keyword or any NCL builtin function.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
A statement was encountered which terminated prematurely. For example, nothing appeared after the &THEN keyword of an &IF.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An &IF, &DOWHILE or &DOUNTIL statement was encountered that had an incorrect number of parameters to make up the condition.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The aaaa function requires fewer parameters than have been coded.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
The maximum number of nested &DO constructions has been reached. The maximum will vary depending upon the precise logic structure of the procedure, but is always a large number. Your procedure should never be structured in a manner that should ever approach this maximum.
System Action:
The NCL procedure is terminated.
User Action:
Restructure the procedure.
Reason:
&NRDDEL requires at least one DOMID (delete-operator-message identifier).
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
An &NRDDEL statement specified a delete-operator-message identifier (DOMID) to delete a non-roll delete message, but the DOMID specified was invalid.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
The NCL procedure has issued an AOM NCL verb that is not supported under this operating system. For example, &WTOR is not supported in z/VM.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The NCL procedure has issued an &DOM NCL verb, but the DOM macro abended with the indicated code. This can occur if an invalid DOMID is provided.
System Action:
The NCL procedure is terminated.
User Action:
Ensure only valid DOMIDs are used.
Reason:
The text for an &WTO or &WTOR NCL verb was either omitted, or the value provided was all blank.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The ROUTCDE parameter of an &WTO or &WTOR NCL verb was not valid.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The DESC parameter of an &WTO NCL verb was not valid.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The MCSFLAG value supplied for an &WTO or &WTOR NCL verb is not a valid list of allowable MCSFLAG values.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The NCL procedure has issued an &WTOR NCL verb with WAIT=0 or NOWAIT specified. This is invalid, as a valid delay is required to give the operator some chance to reply.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure.
Reason:
The console ID entered on an &WTO or &WTOR NCL statement is invalid. It must either be a number from 1 to 99 or (if extended MCS consoles are supported) a valid console name.
System Action:
The NCL process is terminated.
User Action:
Correct the console ID.
Reason:
The LINETYPE operand of the &WTO NCL statement cannot be specified as anything other than NO unless the SOLVE system is running APF authorized.
System Action:
The NCL process is terminated.
User Action:
Determine why the SOLVE system is not running APF authorized.
Reason:
Use of the LINETYPE operand on the &WTO NCL statement is only supported in the MVS and similar environments. It is not valid in z/VM,
System Action:
The NCL process is terminated.
User Action:
Remove the LINETYPE operand.
Reason:
The substitution character provided to the ZSUBST function is missing or in error.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
The substitution string in the &ZSUBST function contains invalid variables.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
The result of the &ZSUBST function is too long.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
The data to be quoted by the &ZQUOTE2 function was too long. This function will always add quotes to the data and hence the total length of the data must be less than or equal to the maximum variable size minus the number of quotes that will be added by the function.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
The &SETVARS function did not locate a KWD= with the ARGS or VARS operands. The variable is 'aaaaa'. The supplied data is 'bbbbb' and must contain KWD=.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
The DATA= operand of the &SETVARS functions contains an invalid keyword or the keyword is missing. The start of the data is displayed.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
A quoted string in the DATA= operand of the &SETVARS function is in error. Either the quotes are not paired or the data is too long.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
The keyword aaaaa specified on a data string was not in the list of keywords specified on the KEYWORDS= operand of the &SETVARS verb.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry. Refer to the NCL Reference for a description of the &SETVARS verb.
Reason:
The variable name that is created by the &SETVARS function (PREFIX= operand data concatenated with the KEYWORDS= operand data) is invalid or reserved.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
The input data specified in the DATA=, VARS= or ARGS operand of the
&SETVARS function contains a duplicate keyword and DUPLICATE=NO is specified.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
The DUPLICATE=NO operand on the SETVARS function is specified. Too many keywords have been specified on the KEYWORDS= operand to perform checking for duplicates - the keyword table has overflowed.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
During processing of an &SETVARS verb, the value extracted for assignment to the named variable exceeded the maximum value that can be set into an NCL variable.
System Action:
The NCL procedure terminates, or, if the ERROR=CONTINUE operand was specified on the &SETVARS statement, this message is returned in &SYSMSG and a non-zero return code is set.
User Action:
Correct the input and retry.
Reason:
During the processing of an &SETVARS verb, embedded or trailing blanks were found while processing the named keyword.
System Action:
The NCL procedure terminates, or if the ERROR=CONTINUE operand was specified on the &SETVARS statement, this message is returned in &SYSMSG and a nonzero return code is set.
User Action:
Correct the input and retry.
Reason:
The input variable name to be generated by the SETVARS function using the VARS= and RANGE= operand will create a variable name that is greater than 12 characters.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
The PREFIX= operand of the &SETVARS function has been is a numeric value, all keywords of the KEYWORD= operand must be numeric.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
The variable name to be generated by the &SETVARS function, using the PREFIX= operand concatenated either with one of the KEYWORDS= operand values or with one of the keywords specified in the PARMS, ARGS, VARS= or DATA= operand will be greater than 12 characters.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
The VARS= operand has been specified on the &SETVARS function. The prefix of each of the VARS must be generic.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
The KEYWORDS=list operand has been specified on the &SETVARS function. There is a syntax error in the specification of the list. The syntax of the list must be KWD,...,KWD or (KWD,...,KWD).
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
An &ZFEATURE statement was encountered that had no feature parameters specified.
System Action:
The NCL procedure is flushed.
User Action:
Correct the NCL procedure and retry.
Reason:
The &FEATURE verbs has been used to set version and level data for the feature indicated as AA..AA but this is invalid for the reason that is described as BB..BB which will be:
IS NOT A VALID FEATURE NAME The feature name is not a valid SOLVE feature name.
IS NOT AN NCL BASED FEATURE The feature name is not an NCL feature.
System Action:
The NCL process is flushed.
User Action:
Correct the NCL procedure.
Reason:
The &ZFEATURE verb has been used to set the version and/or level for an NCL-based feature but the value specified for the version is invalid. The correct formats for version are either Vn.n or Vn.n.n (where n is a numeric digit).
System Action:
The NCL process is flushed.
User Action:
Correct the NCL procedure.
Reason:
The &ZFEATURE verb has been used to set the version and/or level for an NCL-based feature but the value specified for the PUT level is invalid. The only valid format is a 4-digit value.
System Action:
The NCL process is flushed.
User Action:
Correct the NCL procedure.
Reason:
The &ZFEATURE verb has been used to set the version and/or PUT level for an NCL- based feature but is invalid because additional data follows the PUT level value.
System Action:
The NCL process is flushed.
User Action:
Correct the NCL procedure.
Reason:
This message shows an unrecognized operand that was passed to the &BOOLEXPR NCL builtin function.
System Action:
The NCL process is terminated.
User Action:
Correct the &BOOLEXPR operand.
Reason:
This message indicates a duplicated operand on an NCL statement using the &BOOLEXPR built-in function.
System Action:
The NCL process is terminated.
User Action:
Correct the &BOOLEXPR syntax.
Reason:
The value supplied for the SUBCHAR operand of the &BOOLEXPR builtin function is invalid or was omitted.
The SUBCHAR values permitted are: ! % ? `
System Action:
The NCL process is terminated.
User Action:
Correct the SUBCHAR operand.
Reason:
The value supplied for the FOLD operand of the &BOOLEXPR builtin function is invalid or omitted.
Valid values are YES (meaning fold all character data), NO (meaning do not fold), and * (meaning honour the &CONTROL IFCASE setting).
System Action:
The NCL process is terminated.
User Action:
Correct the FOLD operand.
Reason:
The value supplied for the EVAL operand of the &BOOLEXPR builtin function is invalid or omitted.
Valid values are YES (meaning attempt to evaluate the expression) and NO.
System Action:
The NCL process is terminated.
User Action:
Correct the EVAL operand.
Reason:
The value supplied for the VARS operand of the &BOOLEXPR builtin function is invalid or omitted. The value must be a valid generic variable name prefix (including an asterisk (*) at the end).
System Action:
The NCL process is terminated.
User Action:
Correct the VARS operand.
Reason:
The value supplied for the RANGE operand of the &BOOLEXPR builtin function is invalid or omitted. It must be a parenthesized pair of numbers, with the second greater than or equal to the first, and the values must range from 0 to 32767.
System Action:
The NCL process is terminated.
User Action:
Correct the RANGE operand.
Reason:
A combination of operands on the &BOOLEXPR NCL builtin function is invalid. You have coded both the VARS and DATA operands or have not coded either.
System Action:
The NCL process is terminated.
User Action:
Correct the combination of operands.
Reason:
The operand values specified for the VARS and RANGE operands of the
&BOOLEXPR NCL builtin function together result in a possible variable name length that exceeds 12 characters.
System Action:
The NCL process is terminated.
User Action:
Correct the operands.
Reason:
No boolean expression data has been supplied on the &BOOLEXPR NCL builtin function.
System Action:
The expression is regarded as 'invalid'.
User Action:
Provide an expression.
Reason:
Invalid expression syntax was detected in the provided expression for the &BOOLEXPR NCL builtin function.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression syntax.
Reason:
Whilst parsing the &BOOLEXPR builtin function boolean expression, a syntax error in the expression was found. Either an 'AND', an 'OR' or a ')' (right parenthesis) was expected, but none was found.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression syntax.
Reason:
An IGNORE clause in an &BOOLEXPR NCL builtin function boolean expression was not correct. The word IGNORE must be followed by either TRUE or FALSE.
System Action:
The return value is 'INVALID'
User Action:
Correct the expression syntax.
Reason:
Whilst parsing an &BOOLEXPR NCL builtin function boolean expression, a syntax error was detected. A number or literal or NCL variable was expected, but none was found.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression syntax.
Reason:
While parsing an &BOOLEXPR NCL built-in function, invalid boolean expression syntax was detected. An operator was expected, but none was found.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression.
Reason:
Whilst parsing an &BOOLEXPR NCL builtin function, a range or generic value was found but the associated operator was not EQUAL (=) or NOT EQUAL (^=).
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression.
Reason:
Whilst parsing an &BOOLEXPR NCL builtin function, a GENERIC operation was found with numeric operands.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression.
Reason:
During parsing of an &BOOLEXPR NCL builtin function, a range test was found (:). The token after the range was not a number, literal, or variable.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression.
Reason:
While parsing an &BOOLEXPR NCL builtin function boolean expression, a range test with differing data types was found.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression.
Reason:
Whilst parsing an &BOOLEXPR NCL builtin function boolean expression, a TYPE ('IS') test was found. The following token(s) were not either valid type names, or variable names.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression.
Reason:
While parsing an &BOOLEXPR NCL builtin function boolean expression, a modifier on a test (CHARACTER, NUMERIC, FOLD or NOFOLD) was either invalid or duplicated. For example, both CHAR and NUM were specified.
The CHARACTER or NUMERIC modifiers are only allowed when both sides of the operator are variables. The default action is to perform a numeric comparison if both variables are numeric or a character comparison if either is not numeric. The modifier enables the comparison type to be forced.
If either side of the operator is a constant, then the comparison type is implicitly determined by the presence or absence of quotes around the constant. If quoted, a character compare is forced. If not quoted, the constant must be numeric and a numeric compare is forced. In these cases it is invalid also to specify a modifier as this is a duplication.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression.
Reason:
Whilst parsing an &BOOLEXPR NCL builtin function boolean expression, an invalid type name was found.
System Action:
The return value is 'INVALID'.
User Action:
Correct the type name.
Reason:
Whilst parsing an &BOOLEXPR NCL builtin function, constant values was found on both sides of an operator. This is a constant expression, which needs no dynamic evaluation.
This can occur if you allow variables to be substituted into the expression, rather than use SUBCHAR and allow &BOOLEXPR itself to retrieve the variable values as required.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression.
Reason:
Whilst parsing an &BOOLEXPR NCL builtin function boolean expression, either a strict operator , LIKE or CONTAINS operator with numeric operands was found. Since these operators always perform character compares, this is not permitted.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression.
Reason:
Whilst parsing an &BOOLEXPR NCL builtin function, constant values was found on both sides of an operator. This is allowed, but the types of the constant expressions were mixed. That is, there was a number on one side of an operator (unquoted), and a quoted string on the other side. You cannot compare these mixed types of data.
This can occur if you allow variables to be substituted into the expression, rather than use SUBCHAR and allow &BOOLEXPR itself to retrieve the variable values as required.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression.
Reason:
Whilst parsing an &BOOLEXPR NCL builtin function, constant values were found as arguments to the 'IS' or 'IS NOT' operators. Only variables may be provided as arguments. (Constants are allowed in the type list.)
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression and retry the operation.
Reason:
Whilst parsing an &BOOLEXPR NCL builtin function boolean expression, invalid data was found. Parsing could not continue.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression.
Reason:
Whilst parsing an &BOOLEXPR NCL builtin function boolean expression, an invalid variable name was found.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression.
Reason:
Whilst parsing the boolean expression supplied to an BOOLEXPR function, a word longer than 256 characters was found.
System Action:
The return value is 'INVALID'.
User Action:
Correct the erroneous expression syntax.
Reason:
While parsing an &BOOLEXPR NCL built-in function Boolean expression, an invalid number was found.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression.
Reason:
While parsing an &BOOLEXPR NCL built-in function Boolean expression, an invalid quoted string was found. Either the quoted value was too long or no ending quote was found.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression.
Reason:
Whilst parsing an &BOOLEXPR NCL builtin function boolean expression, an NCL keyword was found that is not a system variable name.
System Action:
The return value is 'INVALID'.
User Action:
Correct the expression,
Reason:
An NCL system variable was encountered in a BOOLEXPR function that OML does not support.
System Action:
An error is raised or an invalid expression return is given.
User Action:
Correct the expression,
Reason:
Whilst executing an &BOOLEXPR NCL builtin function boolean expression, a variable value was retrieved and a numeric value was expected. The value was not numeric or was not in the range -2147483648 to 2147483647 for &CONTROL INTEGER setting (default) or in the range +1E-70 to +1E+70 or -1E+70 to -1E-70 for &CONTROL REAL setting.
System Action:
The return value is 'BAD'.
User Action:
Determine the reason for the bad variable data.
Reason:
While executing an &BOOLEXPR NCL builtin function boolean expression, a type test ('IS') with a variable was processed. When the variable value was examined an invalid type name was found.
System Action:
The return value is 'BAD'.
User Action:
Correct the variable type list.
Reason:
While processing a BOOLEXPR expression, the value for the named variable exceeded 256 bytes. This is presently not supported.
System Action:
An error is raised or a bad expression return is indicated.
User Action:
Ensure that all source variables used in the expression are not longer than 256 bytes,
Reason:
While processing an &BOOLEXPR NCL built-in function, a storage shortage was encountered.
System Action:
The NCL process is terminated.
User Action:
Investigate the reason for the storage shortage.
Reason:
A filter supplied to the object services selection method was invalid.
System Action:
Request is rejected.
User Action:
Correct the filter in the request SDU and submit it again.
Reason:
The object passed in an object services selection method was invalid.
System Action:
The request is rejected.
User Action:
Correct the object coded in the request SDU and resubmit the request.
Reason:
An PPI RECEIVE function has been called either without a prior PPI DEFINE being performed or PPI DEFINE was unsuccessful.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
An &PPI SEND or ALERT function has been issued with OPT=HEXPACK operand. The data specified in the DATA= operand is not valid hexadecimal data.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
An &PPI SEND or ALERT function has been issued with the MDO= operand. The mapped data object specified was invalid or not found.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
An &PPI RECEIVE function was issued with MDO= operand. A processing error was encountered with the mapped data structure when assigning the data to an object.
System Action:
The NCL procedure is terminated.
User Action:
Correct the mapped data structure and retry.
Reason:
An &PPI SEND or ALERT command was issued with the VARS= operand. An error was encountered processing the VARS and the variable tokens could not be buffered.
System Action:
The NCL procedure is terminated.
User Action:
Correct the VARS= operand or the variables and retry.
Reason:
An &PPI RECEIVE or SEND command was issued. The ID specified is an invalid name. The name must be one to eight characters and contain valid characters - A-Z, @, #, $, % or .
System Action:
the NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
An NCL process has been started using either the START command with NOTIFY=YES or the NCL verb APPC START.
System Action:
None.
User Action:
None.
Reason:
An NCL process previously started using either the START command with NOTIFY=YES or the NCL verb APPC START, has ended normally and the procedure return code is dddd .
System Action:
None.
User Action:
None.
Reason:
An NCL process previously started using either the START command with NOTIFY=YES or the NCL verb &APPC START, has ended abnormally. An indication of the cause of failure is given by the reason code dddd and the message eeee .
System Action:
None.
User Action:
None.
Reason:
An allocation request was issued for an APPC transaction whose remote end has been defined as a server (see DEFTRANS command) but the server was already active and an attempt to transfer the conversation to it was rejected by the active server.
System Action:
None.
User Action:
Refer to the DEFTRANS command for information on how to define the remote end of an APPC transaction as a server.
Reason:
Protocol error occurred during cleanup of remote OSCALL servers context.
System Action:
Cleanup of context fails.
User Action:
Contact Systems Programmer.
Reason:
A corrupted OSCALL directory entry was detected during cleanup of remote OSCALL server's context.
System Action:
Cleanup of context fails.
User Action:
Contact Product Support Representative.
Reason:
Invalid or null data was received during cleanup of remote OSCALL server context.
System Action:
Cleanup of context fails.
User Action:
Contact Technical Support.
Reason:
A cleanup request was received for an unknown remote OSCALL server context.
System Action:
Cleanup of context fails.
User Action:
Contact Technical Support.
Reason:
An attempt to send a request to a remote system to cleanup a remote OSCALL server context failed.
System Action:
Send cleanup request not issued.
User Action:
Check log for related messages if any, and check for APPC link failures.
Reason:
Invalid syntax was used on the SRCEMDO operand of the &ZFMTLINE verb.
System Action:
Procedure terminates in error.
User Action:
Contact product support representative.
Reason:
The MDO used for formatting the text lines on the &ZFMTLINE verb was not found, or contained no data.
System Action:
Procedure terminates in error.
User Action:
Contact product support representative.
Reason:
A storage error/shortage occurred during processing of the &ZFMTLINE verb.
System Action:
Procedure terminates in error.
User Action:
Determine reason for storage shortage on system.
Reason:
The length of one of the fields in a text line caused the text line to exceed the maximum length on the &ZFMTLINE verb.
System Action:
Procedure terminates in error.
User Action:
Contact product support representative.
Reason:
A variable name generated by the &ZFMTLINE verb exceeds the maximum variable name length.
System Action:
Procedure terminates in error.
User Action:
Contact product support representative.
Reason:
The FMTMDO operand was missing, or was invalid, on the &ZFMTLINE verb.
System Action:
Procedure terminates in error.
User Action:
Contact product support representative.
Reason:
The MDO specified on the FMTMDO operand of the &ZFMTLINE verb has invalid or missing data.
System Action:
Procedure terminates in error.
User Action:
Contact product support representative.
Reason:
The MDO specified on the SRCEMDO operand of the &ZFMTLINE verb was not found, or was unmapped or had invalid data.
System Action:
Procedure terminates in error.
User Action:
Contact product support representative.
Reason:
The vars list format of the VARS= operand was used on the &ZFMTLINE verb in conjunction with the SUFFIX= operand. This combination is invalid. SUFFIX= is only valid with a generic form of VARS= operand.
System Action:
Procedure terminates in error.
User Action:
Contact product support representative.
Reason:
An attempt was made to update a VARTABLE entry with a data element longer than 256 bytes, or an attempt was made to reference a vartable entry with a key longer than the maximum stipulated on the KEYLEN parameter of the VARTABLE ALLOC statement.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
A variable containing a non-numeric value was used for the ADJUST, COUNTER or user correlator field in an &VARTABLE ADD, UPDATE or PUT statement, or an attempt was made to access a vartable entry with a non-numeric key where the key format was specified as numeric in the
&VARTABLE ALLOC statement.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
An attempt was made to reference a VARTABLE entry data item, using an item number greater than the number of data items defined by the DATA= keyword of the VARTABLE ALLOC statement. For example, the field list specified 'DATA=5' but the vartable ALLOC statement defining the vartable specified 'DATA=4' for the number of data items.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
An &VARTABLE GET statement was encountered which specified OPT=GEN or OPT=IGEN to do a generic or an inverse generic get operation on a vartable, however, the vartable was defined as having a numeric key (KEYFMT=NUM) in the &VARTABLE ALLOC statement. Generic and Inverse generic gets are only supported for character- format keys.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
When a VARTABLE entry contains a mapped data object then access by field number is not allowed. The entire object only may be accessed via the MDO operand.
System Action:
The NCL procedure is terminated.
User Action:
Use MDO operand to access a VARTABLE containing MDOs.
Reason:
A vartable statement was encountered specifying 'SCOPE=AOM' for the vartable scope, however, this installation is not licensed for the AOM feature, or the feature was specifically excluded when the Net-Master system was brought up.
System Action:
The procedure terminates.
User Action:
Change the SCOPE to either PROCESS, REGION, or GLOBAL, if the vartable is not required for AOM.
Reason:
An &VARTABLE ALLOC statement was encountered which specified 'SCOPE=AOM', however, either no keylength or a keylength not equal to 16 was specified with the KEYLEN option. Vartables which are required for AOM screening must have a keylength of 16.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An &VARTABLE ALLOC statement was encountered which specified 'SCOPE=AOM', however, no limit was specified with the 'LIMIT' operand. Vartables which are required for AOM screening must have a limit to the number of entries specified.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An &VARTABLE ALLOC statement was encountered which specified 'SCOPE=AOM', however, either no DELOLD option was specified or DELOLD=YES was specified. Vartables which are required for AOM screening must specify DELOLD=NO.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An &VARTABLE ALLOC statement was encountered which specified 'SCOPE=AOM', however, either no AGE option was specified or the incorrect AGE option was specified. Vartables which are required for AOM screening must specify either AGE=NO or AGE=NEW.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An &VARTABLE RESET statement was encountered which specified 'SCOPE=AOM', however, the options OLDEST or NEWEST were specified. Vartables which are required for AOM screening can only be wholly reset.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An &VARTABLE ALLOC statement was encountered which specified 'SCOPE=AOM', however, KEYFMT=NUM or UCHAR was specified. Vartables which are required for AOM screening must have a character key and it must be 16 characters long. Also data translation to upper case is not supported.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
An VARTABLE statement was encountered where the number of elements in the fields list (FIELDS= keyword) was different to the number of elements in the variables list (VARS= keyword). There must be a 1-1 correspondence between the elements in the field list and the variables list.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The FIELDS list on an &VARTABLE statement has null entries eg FIELDS=(A,,B). This is not permitted.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The FIELDS list on an &VARTABLE statement has a duplicated entry (including option + .option). This is not permitted.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The FIELDS list on an &VARTABLE statement has more entries than the system can handle.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The FIELDS list on an &VARTABLE statement has invalid syntax.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The FIELDS list on an &VARTABLE statement is empty.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The FIELDS list on an &VARTABLE statement contains invalid or unrecognizable keywords. Only the keywords listed for the current option of &VARTABLE can be used.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
An VARTABLE statement was encountered which specified either 'DATA*' or 'MDO' in the field list (FIELD operand) however the corresponding entry in the variable list (VARS operand) was not either a generic token name (eg 'AB*') or an MDO name (eg 'ABC.') respectively.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The VARS list on an &VARTABLE statement has null entries eg: VARS=(A,,B). This is not permitted.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The VARS list on an &VARTABLE statement has a duplicated entry. This is not permitted.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The VARS list on an &VARTABLE statement has more entries than the system can handle.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The VARS list on an &VARTABLE statement has invalid syntax.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The VARS list on an &VARTABLE statement is empty.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The VARS list on an &VARTABLE statement contains an invalid variable name.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
An &VARTABLE statement was encountered with 2 or more generic variable names (ie variable names ending with '*') in the 'VARS=' operand. There may only be one generic variable name in the variables list of a vartable statement and it must correspond with the DATA* or .DATA* element in the FIELDS= list.
System Action:
The NCL procedure is terminated.
User Action:
Correct the NCL procedure.
Reason:
The FIELDS operand specified a list of items but the VARS operand was not a list of the same length.
System Action:
The procedure is terminated.
User Action:
Correct and retry.
Reason:
The size and number of NCL variables exceeded the system limit for a single VARTABLE entry.
System Action:
The NCL procedure is terminated.
User Action:
Try using an MDO.
Reason:
An invalid or extraneous operand aaaaaaaa was entered on the SHOW VARTABLES command. Refer to the Command Reference for a description of the syntax of the SHOW VARTABLES command.
System Action:
None.
User Action:
Correct and retry.
Reason:
Either an operand appears twice or the operand is invalid for this particular scope of the SHOW VARTABLES command. Refer to the Command Reference for a description of the syntax of the SHOW VARTABLES command.
System Action:
None.
User Action:
Correct and retry.
Reason:
The operand specified on the SHOW VARTABLES command was missing or invalid. Refer to the Command Reference for a description of the syntax of the SHOW VARTABLES command.
System Action:
None.
User Action:
Correct and retry.
Reason:
There is no NCL procedure running in the active region matching the NCLID specified on the SHOW VARTABLES=nclid command. You can only display process scope vartables for NCL procedures executing in your region.
System Action:
None.
User Action:
None.
Reason:
A temporary storage shortage occurred while trying to process the SHOW VARTABLES command. The command was not processed.
System Action:
None.
User Action:
Consider increasing the SOLVE region/virtual storage/partition size.
Reason:
A show vartables command specifying a userid was entered but that userid is not currently logged on to SOLVE.
System Action:
None.
User Action:
None.
Reason:
A show vartables command specifying a logical unit name was entered but that logical unit is not currently in session with SOLVE.
System Action:
None.
User Action:
None.
Reason:
This message is the header for the following messages, a response to the SHOW VARTABLES command. The column headings are:
Displays the scope of the vartable, or, if the scope is process, the NCL ID of the procedure owning it.
(SCOPE=REGION) Displays the user ID.
Displays the defined key lengths.
Displays the maximum number of entries possible in the vartable.
Indicates the number of entries currently in the tables.
Displays the number of data fields per entry in each table.
Displays the aging option that is specified for the table.
Indicates whether a user correlator is present in the table.
Displays the DELOLD option that is specified on the vartable.
Identifies the key format:
System Action:
None. The table list follows.
User Action:
None.
Reason:
This is the subheader message for the following list of items, a response to the SHOW VARTABLES=AOM command. The column headings are: MIR Whether this vartable is mirrored or not. STG(K) The amount of storage taken up by the vartable mirror.
System Action:
None. The table list follows.
User Action:
None.
Reason:
This message is produced for each vartable in the nominated scope. The columns are described in the N23Y10 message description.
System Action:
None.
User Action:
None.
Reason:
This message is produced for each SCOPE=AOM table nominated. The columns are described in the N23Y11 message description.
System Action:
None.
User Action:
None.
Reason:
This message terminates a multi-line display of the response to the SHOW VARTABLES command.
System Action:
None.
User Action:
None.
Reason:
This message appears as a response to a SHOW VARTABLES STATS command. It provides subheadings for the following N23Y16 message.
Shows the total storage allocated to the vartable.
Shows the average number of bytes per entry.
System Action:
None.
User Action:
None.
Reason:
This message is the detail line displayed for a SHOW VARTABLES STATS command.
Is the total storage allocated to the vartable.
Is the average number of bytes per entry.
System Action:
None.
User Action:
None.
Reason:
The user did a SHOW VARTABLES command but there were no vartables in existence matching the selection criteria specified.
System Action:
None.
User Action:
None.
Reason:
An invalid generic variable prefix was specified on an CONTROL SHRVARS statement.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An &PANEL statement either omitted or specified an invalid name for the panel to be displayed.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The &PANEL statement can be used only in NCL procedures that have access to a screen which will display full-screen panels.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An &LOGON statement either omitted or specified an invalid name for the `request accepted' panel.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The length of data following the panelname on an &LOGON statement cannot exceed 168 characters. This includes any 'userdata' that is being passed to the application.
System Action:
The EASINET procedure terminates.
User Action:
Correct the text and retry.
Reason:
The &LOGON statement may be used only within an EASINET procedure.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The &LOGON statement has specified an invalid logmode name on the logmode operand.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
&PANEL processing failed because of a temporary storage shortage.
System Action:
The procedure terminates.
User Action:
Retry. Contact your systems administrator if the condition persists.
Reason:
An &CALL statement omitted the name of the target module or specified a name that is not a valid load module name.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
&CALL processing failed because a temporary storage shortage prevented successful calling of the requested module.
System Action:
The procedure terminates.
User Action:
Retry. Contact your systems administrator if the condition persists to investigate the cause of the storage shortage.
Reason:
&CALL processing failed when the target module could not be successfully attached (MVS, VM, FSP) or loaded (VSE).
System Action:
The procedure terminates.
User Action:
Ensure that the target module is in a load library (core-image library) that is accessible to SOLVE. Contact your systems administrator.
Reason:
The valid range of return codes that may be passed back from a module invoked via &CALL is 0 - 99 inclusive. The module has returned a return code in register 15 which is outside this range.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The module invoked via &CALL abended with the specified completion code. This completion code will be SYS-zzz for a system abend code or USER-zzz for a user abend code.
System Action:
The procedure terminates.
User Action:
Correct the module and retry.
Reason:
&CALL supports simple substitution only. For example, &CALL MYMODULE &PARM1 &PARM2 is valid, but &CALL MYMODULE &PARM&NUMBER1 &PARM&NUMBER2 is invalid because complex substitution would be required to evaluate the parameters passed.
System Action:
The NCL procedure is terminated.
User Action:
Correct the procedure and retry.
Reason:
The PARMLIST= operand on the &CALL statement has specified an invalid value. The value must be NEW or OLD.
System Action:
The NCL procedure is terminated.
User Action:
Correct the operand and retry.
Reason:
An &CALL statement with the SUBSYS= operand has specified a subsystem which is not defined.
System Action:
The NCl procedure is terminated.
User Action:
Correct the procedure and retry. See the SUBSYS command description for help on defining a subsystem.
Reason:
A &CALL to a subsystem has failed whilst waiting to be actioned due to the reason specified.
System Action:
The NCL procedure is terminated.
User Action:
Find out why the subsystem failed.
Reason:
A program called using CALL has returned a variable which has a length which is negative or too large.
System Action:
The NCL procedure is terminated.
User Action:
Correct the program and retry.
Reason:
&LOGREAD, &LOGDEL are verbs reserved for use by the LOGPROC system level procedure and cannot be used in any other process.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An &GOTO or &GOSUB statement either omitted a target label or specified an invalid label name, and &CONTROL LABEL is in effect.
System Action:
The procedure terminates.
User Action:
Correct and retry. &CONTROL NOLABEL will avoid the procedure being terminated due to this type of error.
Reason:
An &GOTO or &GOSUB specified a label that is not defined within the procedure, or was not found within the search range specified, and the procedure is executing without the &CONTROL NOLABEL option.
System Action:
The procedure terminates.
User Action:
Correct and retry or use the &CONTROL NOLABEL option to allow this occurrence.
Reason:
Duplicate labels are not allowed unless &CONTROL NODUPCHK is specified. The procedure has been terminated because a label has been duplicated.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The &GOTO and &GOSUB statements provide generic search capabilities. You have attempted to use an argument that is not valid.
System Action:
The procedure terminates.
User Action:
For a detailed description of this command, refer to the NCL User Reference manual.
Reason:
The &RETSUB statement has attempted to pass an invalid return code back to the mainline.
System Action:
The procedure terminates.
User Action:
Correct the error and retry.
Reason:
SOLVE allows 250 levels of nested subroutines only. The procedure has attempted to nest deeper than this.
System Action:
The procedure terminates.
User Action:
Restructure the procedure to prevent it from exceeding this maximum.
Reason:
Error opening a file. Not enough internal SOLVE storage was available to create the control blocks required to process this file.
System Action:
File is not opened. System may soon run out of memory and abend.
User Action:
Try again later.
Reason:
No file id was specified on an &FILE OPEN ncl statement.
System Action:
No file opened.
User Action:
Specify a fileid on the &FILE OPEN statement.
Reason:
The NCL exit provided for an FILE OPEN statement (NCLEX01) returned an invalid return code. Valid return codes are: 0,4,8,12,16.
System Action:
None.
User Action:
Examine the NCL exit, NCLEX01 to determine why it returned an invalid return code.
Reason:
Old file verbs: aaaaa = {KEY|PUT|GET|ADD|DEL}. No file is currently opened for processing.
System Action:
None.
User Action:
Use an &FILEID statement (for old file verb processing) before issuing the &FILE KEY/PUT/ADD/GET/DEL request.
Reason:
New file verbs: aaaaa={SET/PUT/ADD/GET/DEL} Old file verbs: aaaaa={KEY/PUT/ADD/GET/DEL} bbbbb = File name. The specified file has not been successfully opened.
System Action:
None.
User Action:
Check that a &FILE OPEN, or &FILEID statement was specified, and check the return code after opening the file to see if it was opened successfully.
Reason:
New file verbs: aaaaa = {SET/PUT/ADD/GET/DEL/OPEN} Old file verbs: aaaaa = {KEY/PUT/ADD/GET/DEL} bbbbb = File identifier. The specified file is not available to NCL for processing.
System Action:
None.
User Action:
Check the return code after opening the file. Check that the DDNAME is allocated and the UDB is open.
Reason:
New file verbs: aaaaa={SET/PUT/ADD/GET/DEL} Old file verbs: aaaaa={KEY/PUT/ADD/GET/DEL} bbbbb=File name. The data set for this file was not defined with a relative key position of zero, and the file was opened as either delimited or mapped.
System Action:
None.
User Action:
It is not possible to carry out either Delimited (standard udb) or Mapped processing on a file which does not have a relative key position of 0. Use a different file, or a different processing mode.
Reason:
Applies to old file verbs only. aaaaaaaa = {KEY/PUT/ADD/GET/DEL} bbbbbbbb = File name File key has been specified in a different format to the file format. e.g. a Text key specified for an EXT-HEX format file.
System Action:
None.
User Action:
Specify the file key using the correct format.
Reason:
No key has been set for a file processing request which requires a key. e.g. GET/PUT/ADD/DEL. aaaaaa = {PUT/ADD/GET/DEL}. bbbbbb = File name.
System Action:
None.
User Action:
Specify a file key for the operation to be carried out. For the new file verbs, specify a key using the KEY=filekey operand. For the old file verbs, use the &FILEKEY verb to set a key.
Reason:
The particular file has been defined as a key only file, and yet data has been specified on a file PUT/ADD operation. aaaaa = {PUT/ADD} bbbbb = File name.
System Action:
None.
User Action:
Don't specify data, or change file definition.
Reason:
The specified key exceeds the maximum key length for the file. aaaaa = {SET/KEY/PUT/ADD/GET/DEL} bbbbb = File name. ccccc = Maximum key length for the file.
System Action:
None.
User Action:
Make the length of the key correct. If the key is specified in HEX it may be necessary to Halve it's length.
Reason:
Access to a file using an alternate index must be via it's base cluster. This usually applies to PUT/ADD/DEL requests, where although a record is retrieved using the alternate index, processing must be switched to the base cluster for update requests.
System Action:
None.
User Action:
Swap processing to the base cluster before issuing the request.
Reason:
Access to the file is restricted (e.g. Read only, or Read/Write but no Delete etc.). aaaaaa = {PUT/ADD/GET/DEL}. bbbbbb = File name.
System Action:
Request discarded.
User Action:
Access may have been restricted by NCLEX01, or because the UDB was opened for INPUT only. Update the users authority, or reopen the UDB for read/write.
Reason:
A key was specified for a non-keyed file. For example, a key was specified for an ESDS or SYSOUT.
aaaaa has the following values: KEY, SET, PUT, ADD, GET, and DEL.
bbbbb is the file name.
System Action:
None.
User Action:
Correct the NCL code, and retry.
Reason:
The data being written to a file on a PUT/ADD is larger than the maximum record length specified for that file. aaaaa = {PUT/ADD} bbbbb = File name. ccccc = Maximum record length for this file (in bytes).
System Action:
None.
User Action:
Write less data to the file.
Reason:
The format of the data being written to the file is invalid. (e.g. writing Text to a Hexadecimal format file)
System Action:
None.
User Action:
Use correct format for this file.
Reason:
Indicates that the operands used are invalid for a file opened in the current format. For example, using the DATA= operand on a mapped file, or the VARS= operand on a mapped file which uses a map other than the $NCL map, or specifying the MAP= operand on a file that was not opened in mapped format.
System Action:
None.
User Action:
Make sure the file has been opened in the desired format, and that the operands are valid for that particular format.
Reason:
An invalid PRTCNTL option has been specified on an FILE ADD/PUT statement when writing to a SYSOUT file that was defined with machine control characters, i.e. DCB=RECFM=M, which is indicated by specifying PRTCNTL=M on the ALLOCATE command for the SYSOUT dataset.
When machine control characters are used the only allowable options for &FILE ADD/PUT are DATA, LEFT, CENTRE, and RIGHT.
System Action:
None.
User Action:
Correct the NCL procedure and rerun. You should either use ASA control characters by specifying PRTCNTL=A on the ALLOCATE command, or use PRTCNTL=DATA and specify the machine control character in the first character of the data line.
Reason:
An option was specified on a file verb which is invalid for the current processing mode. In particular when print control options are used on a file which is not opened in external or unmapped mode.
System Action:
None.
User Action:
Use a different processing mode, or don't use the options.
Reason:
A Mapping error occurred while trying to map an mdo during an FILE request. This error should only occur when processing a file using MAPPED format. aaaaa = OPEN|SET|GET|PUT|ADD|DEL bbbbb = File id cccccccc = Map name
System Action:
For &FILE GET, the incoming data is placed in the mdo as is, and the mdo remains unmapped.
User Action:
Make sure the file processing mode is intended to be MAPPED. If so, ensure the correct map name is being specified on the &FILE OPEN and/or the &FILE GET. Check that the map definition accurately describes the incoming data.
Reason:
An NCL procedure has fallen over on an FILE verb because GENLEN=0 was specified. aaaaaaaa = ADD/DEL/GET/PUT/SET. bbbbbbbb = file id.
System Action:
Procedure is flushed.
User Action:
Modify procedure to ensure the GENLEN field always has a none-zero value.
Reason:
An operand is missing from an FILE verb.
System Action:
None.
User Action:
Correct the syntax.
Reason:
During the processing of an ENCODE or DECODE NCL statement, with the Advanced Translation Facility in use, ATF returned an error. This error occurred while the translation of a specific component of the MDO was being processed.
The message shows the ATF return code, the MDO component name, and specific error information as follows:
R15 Information
4 OUTPUT OVERFLOW, LENGTH GT nnnnnn The output string exceeded the allowable length
8 INPUT STRING ERROR, CODE=cc APPROX. OFFSET=oo DATA FOLLOWS A syntax error was detected in the input data. The approximate offset in the data is indicated. A dump of the input data will follow this message (Message ID N24K11).
The error codes are:
2 Double-byte string or substring has odd length
3 Invalid input character detected
4 Input exhausted unexpectedly for example, in the middle of a multi-byte character
5 Invalid unicode surrogate pair
6 Invalid or truncated shift sequence
12 SOURCE TYPE UNKNOWN: ssssss The requested source character set name is not defined to ATF
20 TARGET TYPE UNKNOWN: ssssss The requested target character set name is not defined to ATF
24 SOURCE TABLE LOAD FAILURE: ssssss The requested source character set table failed to load. (If this is the first request, additional messages will be logged describing the error)
28 TARGET TABLE LOAD FAILURE: ssssss The requested target character set table failed to load. (If this is the first request, additional messages will be logged describing the error.)
System Action:
&ENCODE or &DECODE fails.
User Action:
Look at the reason description and rectify as appropriate.
Reason:
This message follows the N24K10 message and displays the input data that was being translated by ATF.
It can be used to determine why a syntax error occurred during translation.
System Action:
&ENCODE or &DECODE fails.
User Action:
Refer to message N24K10.
Reason:
This is a warning against possible errors detected by an ENCODE operation. aaaaa = Warning Description
System Action:
&ENCODE ignores the warning and proceeds to completion.
User Action:
Look at the warning description to determine its severity.
Reason:
A terminal error has occurred while processing an &ENCODE operation. aaaaa = Reason description bbbbb = Component in error
System Action:
&ENCODE fails.
User Action:
Look at the reason description and rectify as appropriate. Possible reasons are:
Invalid data encountered in MDO. :- Check data of component in error. Mandatory component not found. :- Assign data to the component, or modify its MAP definition.
Reason:
This is a warning against possible errors detected by an &DECODE operation. aaaaa = Warning Description
System Action:
&DECODE ignores the warning and proceeds to completion.
User Action:
Look at the warning description to determine its severity.
Reason:
The &DECODE operation has encountered a non-recoverable error in the data string being decoded. aaaaa = Description of the error bb = Offset(hex) of the structure in error cc = Offset(hex) from the structure bb ddddd = Component in error
System Action:
&DECODE fails.
User Action:
Look at the error description and rectify as appropriate. Possible reasons are: Invalid BER encoding detected. Mandatory component not found. Implementation limit exceeded.
Reason:
MDO processing was unable to obtain enough storage from the system pool to satisfy the last MDO request.
System Action:
Procedure is flushed.
User Action:
Retry request later.
Reason:
An assign statement with an MDO= operand has invalid syntax.
System Action:
Procedure is flushed.
User Action:
Check syntax.
Reason:
An index was used in an MDO= operand where it wasn't expected, or the index value is out of range.
System Action:
Procedure is flushed.
User Action:
Check map definition, and see that this is a valid indexable component, and if so, check that the index does not exceed 32767, or any maximum imposed by a SIZE specification.
Reason:
An error occurred while trying to map an MDO's data during an MDO request.
System Action:
Procedure is flushed.
User Action:
Check program logic. Test that map connection has been performed, and that it was successful. Ensure correct map is in use.
Reason:
The internal recursion stack limit was exceeded while attempting to process an MDO request, possibly caused by having too many segments in a compound name.
System Action:
Procedure is flushed.
User Action:
Reduce number of name segments in MDO name. May require redefinition of the map.
Reason:
A variable indexed MDO name (e.g. MDO=a.b.{*}) was used invalidly.
System Action:
Procedure is flushed.
User Action:
Check use of index on MDO operand.
Reason:
Mutually exclusive operands were used on an &ASSIGN verb using MDO.
System Action:
Procedure is flushed.
User Action:
Check syntax.
Reason:
A feedback was returned during &ASSIGN processing of an MDO which was unexpected.
System Action:
None.
User Action:
Contact your product support representative.
Reason:
This message is only issued if &CONTROL MDOCHK is on. The message indicates a ZMDORC of 8 or 12 was obtained. MDO TYPE CHECK ERROR: ZMDORC=8, ZMDOFDBK=0 MDO DATA CHECK ERROR: ZMDORC=8, ZMDOFDBK=1 MDO NAME CHECK ERROR: ZMDORC=12, ZMDOFDBK=0
System Action:
Procedure is flushed.
User Action:
Determine the reason for the error. Type check: Attempt made to assign invalid data into or from an MDO. Data check: Physical limitations exceeded assigning data to an MDO. Name check: Component name used in MDO assign is not defined in the map.
Reason:
Message is only issued if CONTROL MDOCHK is set. xxxxxxxxxxx is the map name. An attempt to attach a map to an MDO failed because:
System Action:
Procedure is flushed.
User Action:
Verify that the map is defined and loads successfully, and that the data in the MDO agrees with the map definition. (Issue the LOAD MAP=map_name command to see whether the map loads successfully.)
Reason:
This message is the response obtained when a SYSPARMS MAPLOAD=mapname command is entered. It indicates that the map load process has begun.
System Action:
Map loading commences.
User Action:
None.
Reason:
Indicates that the map has been loaded. Issued in response to a SYSPARMS MAPLOAD=mapname command. aaaaa = mapname.
System Action:
Map has been loaded into memory. Errors during load will have been displayed.
User Action:
None.
Reason:
This is the response to a SYSPARMS MAPDEL=map or MAPRESET=map command. It indicates that the map delete process has begun. aaaaa = the number of map connections still in use which includes any MDO's using this map, or any other maps that import definitions from this map. When the use count goes to zero the map is completely purged.
System Action:
Map deletion commences.
User Action:
None.
Reason:
This is issued in response to a SYSPARMS MAPDEL=mapname command, and indicates that the map deletion process is complete. aaaaa = the name of the map which was deleted from memory.
System Action:
Map has been deleted from memory.
User Action:
None. Issue SYSPARMS MAPLOAD=MAPNAME to reload the map into memory.
Reason:
This message is issued in response to a SYSPARMS MAPDEL=mapname command and indicates that the map specified is not currently loaded into memory. aaaaa = Name of map not found.
System Action:
None.
User Action:
Check that the correct map name was used on the SYSPARMS MAPDEL command. Use the SHOW MAPS command to display a list of maps currently loaded into memory.
Reason:
This message is issued in response to a SYSPARMS MAPLOAD=mapname command and indicates that the load failed completely.
aaaaa is the map name.
bbbbb is the reason.
System Action:
Map is not loaded.
User Action:
Look at reason (bbbbb), and investigate further. Possible reasons include:
Reason:
An attempt to connect an MDO to a map failed. The data in the map load records was invalid.
System Action:
Map connection fails.
User Action:
Recompile the map and retry.
Reason:
An error occurred while loading a map.
System Action:
Map load processing is not completed.
User Action:
Check the feedback code, correct and retry.
Reason:
An error occurred during a map load. The key for the record in error is dumped following this message.
System Action:
Map is not loaded.
User Action:
Recompile map and retry.
Reason:
An error occurred during a map load. aa = Reason code. bbbbbbbbb = Reason description
System Action:
Map connection or map load failed.
User Action:
Recompile or otherwise correct, and retry.
Reason:
issued when a mapping error occurs, and displays the name of the component of type definition that was in error.
System Action:
None.
User Action:
Recompile the map, or correct the problem, and retry
Reason:
Issued when a mapping error occurs, and indicates the offset within the particular map load record at which the error was detected.
System Action:
Map is not loaded.
User Action:
Use this combined with output from message N24Z02 to determine the error in the map definition record.
Reason:
This message is issued when an error occurs in a map definition. It displays the contents of the map load record that was in error.
System Action:
Map is not loaded.
User Action:
Use this in conjunction with messages N24Z03, and N24Z02 to determine the error within the map load record.
Reason:
An RETURN statement has specified an invalid variable name.
System Action:
The procedure terminates.
User Action:
Correct and re-enter.
Reason:
The specified keyword cannot be used on an &RETURN statement.
System Action:
The procedure terminates.
User Action:
See the NCL Reference for restrictions that apply to the use of this variable, then correct and retry.
Reason:
This message, together with messages N25004 and N25005 are issued when an NCL procedure (with CONTROL ENDMSG in effect) terminates as a result of the RETURN statement but there is no higher level procedure to return to, for example, the procedure was invoked from OCS. Message N25004 provides a heading for multiple occurrences of message N25005, each of which lists a variable specified on the RETURN statement together with its length and value.
System Action:
None.
User Action:
None.
Reason:
Refer to message N25003.
System Action:
None.
User Action:
None.
Reason:
Refer to message N25003.
System Action:
None.
User Action:
None.
Reason:
An &WRITE verb has specified an invalid list for the ROUTCDE operand.
System Action:
The procedure terminates.
User Action:
Correct the procedure and retry.
Reason:
An &WRITE verb has specified an invalid value for the AOMTIME operand.
System Action:
The procedure terminates.
User Action:
Correct the procedure and retry.
Reason:
An &WRITE verb has specified an invalid value for the AOMJOBID operand.
System Action:
The procedure terminates.
User Action:
Correct the procedure and retry.
Reason:
The &WRITE verb was issued with a type=req operand. This operand is mutually exclusive with display attribute operands such as COLOUR=, ALARM=, HIGHLIGHT=.
System Action:
The NCL procedure is terminated.
User Action:
Correct the WRITE NCL statement.
Reason:
An &WRITE verb has specified operands which are mutually exclusive. Only one of the SERVER, LUNAME, USERID or NCLID operands are permitted.
System Action:
The procedure terminates.
User Action:
Correct the procedure and retry.
Reason:
An &WRITE verb has specified either the LUNAME, USERID, SERVER or NCLID operand together with TERM=NO. If any of these operands are present, then TERM=YES must be specified (or allowed to default).
System Action:
The procedure terminates.
User Action:
Correct the procedure and retry.
Reason:
An &WRITE verb has specified either the LUNAME, USERID, NCLID or SERVER operand together with either MSGCODE, MON=YES, AOM=YES, FTS=YES or ALL=YES. These groups of operands are mutually exclusive.
System Action:
The procedure terminates.
User Action:
Correct the procedure and retry.
Reason:
An &WRITE verb has specified TERM=NO but no message destination is present. If TERM=NO is present, either LOG=YES, MON=YES, AOM=YES, FTS=YES or ALL=YES must be specified.
System Action:
The procedure terminates.
User Action:
Correct the procedure and retry.
Reason:
The AOM operands on an &WRITE indicate that the message is sourced from both VM and MVS systems. This is not possible.
System Action:
The procedure terminates.
User Action:
Correct the procedure and retry. Refer to the AOM Installation and Reference manual for a description of the &WRITE operands.
Reason:
An &WRITE verb has specified AOMUFLGS= as well as AOMUFLGn These operands are mutually exclusive.
System Action:
The procedure terminates.
User Action:
Correct the procedure and retry. Refer to the AOM Installation and Reference manual for a description of the &WRITE operands.
Reason:
The &PARSE statement is incorrect.
System Action:
The procedure terminates.
User Action:
Correct and retry. For a description of the &PARSE built-in function see the NCL Reference.
Reason:
The &PARSE statement has specified an invalid RANGE operand.
System Action:
The procedure terminates.
User Action:
Correct and retry. Refer to the NCL Reference for a description of the &PARSE function.
Reason:
The &PARSE statement has duplicate or inconsistent operands.
System Action:
The procedure terminates.
User Action:
Correct and retry. Refer to the NCL Reference for a description of the &PARSE function.
Reason:
The &PARSE statement does not have mandatory operands specified.
System Action:
The procedure terminates.
User Action:
Correct and retry. Refer to the NCL Reference for a description of the &PARSE function.
Reason:
The &PARSE statement variable prefix is too long for the specified, or default, RANGE suffix to be added.
System Action:
The procedure terminates.
User Action:
Correct and retry. Refer to the NCL Reference for a description of the &PARSE function.
Reason:
The &PARSE statement has no, or too many, characters in the DELIM= delimiter string.
System Action:
The procedure terminates.
User Action:
Correct and retry. Refer to the NCL Reference for a description of the &PARSE function.
Reason:
The variable name is invalid or is the name of a reserved keyword.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
The &PARSE statement does not have a DATA operand coded.
System Action:
The procedure terminates.
User Action:
Correct and retry. Refer to the NCL Reference for a description of the &PARSE function.
Reason:
The syntax in an &SECCHK statement is invalid.
System Action:
The NCL procedure terminates.
User Action:
Correct the statement and retry. Refer to the NCL User Reference for a description of the &SECCHK function.
Reason:
You may only specify your own userid on the &SECCHK CHANGE statement unless the procedure is being run from EASINET.
System Action:
The procedure terminates.
User Action:
See the NCL Reference for details and restrictions on the use of this facility.
Reason:
The &SECCHK CHECK statement is only valid in a procedure that is being run from EASINET.
System Action:
The procedure terminates.
User Action:
Refer to the NCL Reference for details and restrictions on the use of this facility.
Reason:
The syntax of the &MASKCHK statement is invalid.
System Action:
The procedure terminates.
User Action:
For information about the use of this statement, see NCL Reference Guide.
Reason:
The mask specified on the &MASKCHK statement must be a single character.
System Action:
The procedure is terminated in error.
User Action:
See the NCL Reference for details on the use of this statement.
Reason:
The &PROMPT statement is valid only for use with LU-1 type terminals.
System Action:
The procedure is terminated in error.
User Action:
See the NCL Reference for details on the use of this statement.
Reason:
An &LOCK statement contains duplicate or conflicting operands. The statement is invalid.
System Action:
The procedure terminates.
User Action:
Correct and retry. For a description of the &LOCK built-in function see the NCL Reference.
Reason:
The maximum number of LOCKs is already held. The &LOCK request is
System Action:
User Action:
Determine the number of currently active LOCKs using the &SHOW LOCKS command and determine if the number of requests is excessive.
Reason:
The &LOCK statement is incorrect.
System Action:
The procedure terminates.
User Action:
Correct the statement and retry.
Reason:
The &LOCK operand aaaaaaaa is invalid.
System Action:
The procedure terminates.
User Action:
Correct the statement and retry.
Reason:
The nominated &LOCK operand is required and must be coded.
System Action:
The procedure terminates.
User Action:
Correct the statement and retry.
Reason:
The &LOCK statement specifies a resource name that is too long.
System Action:
The procedure terminates.
User Action:
Resource names may be 1 to 16 characters. Correct the statement and retry.
Reason:
An &SMFWRITE NCL statement specified an invalid RECID value or invalid hexadecimal data.
System Action:
The procedure is terminated.
User Action:
Determine the cause of the error. Correct and retry.
Reason:
An unauthorized user or procedure attempted to issue an &SMFWRITE NCL statement.
System Action:
The procedure terminates unless the TEST option is specified or the SMFTRACE system parameter is set to YES. In TEST mode, the contents of the SMF record is written to the activity log instead of SMF.
User Action:
The &SMFWRITE statement is subject to an authorization check. The installation may have restricted its use to certain user IDs or from certain procedures.
See your systems administrator.
Reason:
An &SECCALL CHANGE=user has been issued for a user other than the user logged on or the user does not have UAMS authority to CHANGE another users password.
System Action:
None.
User Action:
Correct the userid specified and retry.
Reason:
An &SECCALL CHECK USER=user was issued for a user other than the user logged on, or an &SECCALL QUERY was issued from EASINET.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An &SECCALL DELETE USER=user has been issued by a user without UAMS authority.
System Action:
None.
User Action:
Contact your installation help desk if necessary.
Reason:
An &SECCALL CHANGE USER=user DETAILS=x has been issued. DETAILS=x (where 'x' must be Y(es) or N(o) ) or FIELDS=list operand must be specified.
System Action:
None.
User Action:
Correct the parameter and retry.
Reason:
An &SECCALL CHANGE USER=user has been issued by a UAMS authorized user to force change the password of another user. The password parameter is invalid on this operation.
System Action:
None.
User Action:
Correct the statement and retry.
Reason:
An &SECCALL CHANGE USER=user has been issued without a new password or the user details to be updated.
System Action:
None.
User Action:
Correct the statement and retry.
Reason:
This message indicates the outcome of a Password/details change for the indicated user.
The possible values for both P1 and P2 are :
UPDATED - the password/user details were updated
NOT UPDATED - the password/user details were not updated
UPDATE FAILED - the password/user details update failed
System Action:
None.
User Action:
None.
Reason:
The UAMS definition for the specified user has been successfully deleted.
System Action:
None.
User Action:
None.
Reason:
The field list specified in the FIELDS operand of an &SECCALL QUERY or &SECCALL CHECK is invalid.
System Action:
The procedure is flushed.
User Action:
Correct the FIELDS syntax and retry the operation.
Reason:
The field list that is specified in an &SECCALL function contains invalid fields.
If the request is &SECCALL QUERY, the list of valid fields is a subset of structured fields that are retained in storage for this user.
If the request is &SECCALL CHANGE, the list of valid fields is restricted to the user details and the user notification details.
For the list of valid fields, see NCL Reference Guide.
System Action:
The NCL procedure is flushed.
User Action:
Correct the field list, and retry the operation.
Reason:
An &SECCALL CHANGE USER=user FIELDS= has been issued. An error has been found in processing one or more structured fields. Refer to the log for details of the structured field in error.
System Action:
The NCL procedure is flushed.
User Action:
Correct the field and retry.
Reason:
The &SECCALL EXIT command was issued when there was no security exit installed.
System Action:
The NCL procedure is terminated.
User Action:
Correct and retry.
Reason:
An NCL statement required a call to the NCL authorisation exit NCLEX01 but there was insufficient storage to complete the linkage and call.
System Action:
The procedure is terminated.
User Action:
Investigate the reason for the storage shortage. Correct and retry.
Reason:
An NCL statement required a call to the NCL authorisation exit NCLEX01 but linkage to the module failed.
System Action:
The procedure is terminated.
User Action:
Determine the reason for failure from an accompanying message.
Reason:
The return code passed back from the NCL authorisation exit NCLEX01 was not one of the allowable values.
System Action:
The procedure is terminated.
User Action:
Correct the exit return code and retry the request.
Reason:
A call to the NCL authorisation exit NCLEX01 failed with the system abend code shown in the message.
System Action:
The procedure is terminated.
User Action:
Correct the problem in the exit and retry the request.
Reason:
An &SECCALL UPDATE/ADD USER=user has been issued by a user without UAMS authority.
System Action:
The NCL procedure is flushed.
User Action:
If necessary contact your systems administrator.
Reason:
An &SECCALL GET USER=user OPTION=opt has been issued. 'opt' must be KEQ (Key Equal), KGT (Key Greater Than) or KLT (Key Less Than).
System Action:
The NCL procedure is flushed.
User Action:
Correct the parameter and retry.
Reason:
An &SECCALL GET/UPDATE/ADD USER=user FIELDS= has been issued. A structured field 'xxxx' has been found in error.
System Action:
The NCL procedure is flushed.
User Action:
Correct the field and retry.
Reason:
An &SECCALL GET/UPDATE/ADD USER=user FIELDS= has been issued. An error has been found in processing one or more structured fields. Refer to the log for details of the structured field in error.
System Action:
The NCL procedure is flushed.
User Action:
Correct the field and retry.
Reason:
The FIELDS operand on the &SECCALL function contains an entry that is more than 256 characters.
System Action:
The NCL procedure is flushed.
User Action:
Correct the FIELDS operand and retry the procedure.
Reason:
An &SECCALL GET/UPDATE/ADD USER=user FIELDS=field has been issued. A field specified exceeded the maximum supported. Structured fields are normally represented as 4 hex characters and leading zeroes may be omitted.
System Action:
The NCL procedure is flushed.
User Action:
Correct the field and retry.
Reason:
An &SECCALL GET/UPDATE/ADD USER=user FIELDS=field has been issued. The specified field 'xxxx' is invalid as hexadecimal characters.
System Action:
The NCL procedure is flushed.
User Action:
Correct the field and retry.
Reason:
An &SECCALL GET/UPDATE/ADD USER=user FIELDS=xxxx has been issued. The specified field 'xxxx' is not a defined structured field.
System Action:
The NCL procedure is flushed.
User Action:
Correct the field and retry.
Reason:
An &SECCALL GET/UPDATE/ADD USER=user FIELDS=xxxx has been issued. The specified field 'xxxx' is processed by a feature that is not configured for this system.
System Action:
The NCL procedure is flushed.
User Action:
Correct the field and retry.
Reason:
An SECCALL ADD USER=user TYPE=type has been issued. 'type' must be either 'USER' to ADD a user definition, or 'GROUP' to ADD a group definition.
System Action:
The NCL procedure is flushed.
User Action:
Correct the type and retry.
Reason:
An &SECCALL ADD USER=user PASSWORD=pwd TYPE=GROUP has been issued. The password field is invalid as a group definition is not available for logon.
System Action:
The NCL procedure is flushed.
User Action:
Correct the type and/or the password and retry.
Reason:
An &SECCALL ADD USER=user TYPE=USER has been issued. A password must be supplied to add a user definition.
System Action:
The NCL procedure is flushed.
User Action:
Correct the statement and retry.
Reason:
An &SECCALL ADD USER=user has been issued. The add of the definition 'user' has completed successfully.
System Action:
The user details are stored on the UAMS file or via an external security manager. The user may be prompted to change their initial password when they logon.
User Action:
Inform the new user of the password to be used when they log on.
Reason:
An &SECCALL UPDATE USER=user has been issued. The update of the definition 'user' has completed successfully.
System Action:
None.
User Action:
None.
Reason:
The FIELDS operand on the &SECCALL function contains entries that are not contained within paired brackets. If there is more than one field to be processed by the &SECCALL function, then these must be contained within brackets.
System Action:
The NCL procedure is flushed.
User Action:
Correct the FIELDS operand and retry the operation.
Reason:
An &SECCALL ADD USER= has been issued. The user id specified contains characters that are invalid. Valid characters are A-Z, 0-9 and national characters @, # and $.
System Action:
The ADD operation is rejected, &RETCODE is set to 8.
User Action:
Correct the user id value and retry the ADD operation.
Reason:
The MDO supplied to an &ENCODE or &DECODE statement is invalid.
System Action:
None.
User Action:
Ensure that different source and target MDOs are used. Check the syntax of the MDO names and verify them against their respective MAP definitions.
Reason:
An internal MDS error has occurred.
System Action:
None.
User Action:
Contact your product support representative.
Reason:
The internal recursion stack limit was exceeded while processing an
&ENCODE or &DECODE operation, possibly caused by too many segments in a compound name.
System Action:
None.
User Action:
Reduce number of name segments in mdo name. May require redefinition of the map.
Reason:
An &ENCODE or &DECODE statement has invalid syntax.
System Action:
None.
User Action:
Check syntax.
Reason:
The TRANSLATE= operand supplied to an &ENCODE or &DECODE statement is invalid.
System Action:
None.
User Action:
Check supported TRANSLATE operands, e.g. ISO, DEC, ASCII...
Reason:
The encoded string cannot be assigned to the target MDO of an &ENCODE statement, possibly due to its defined type.
System Action:
None.
User Action:
Check the type definition of the target MDO and rectify as appropriate.
Reason:
The procedure has abended on an &ENCODE or &DECODE verb because an MDO was invalidly mapped because of one of the following:
- the map was not found on the mapping services database
- it failed to load
- it did not successfully attach to the MDO because it mismatched the data in the MDO.
System Action:
Procedure is flushed.
User Action:
Ensure map exists, loads and correctly maps the underlying MDO data.
Reason:
The specified target mdo contains invalid data.
System Action:
None.
User Action:
Delete the invalid component, or use a new MDO.
Reason:
An &ENCODE or &DECODE statement specified operands that indicate that ATF is to be used. However, ATF is not available or is not licenced on this SOLVE system.
System Action:
An error is indicated.
User Action:
Check your SOLVE licence for ATF support.
Reason:
An &ENCODE or &DECODE statement has a SRC_CHARSET operand that names a character set that is not recognized by ATF.
System Action:
An error is indicated.
User Action:
Check the character set name.
Reason:
An &ENCODE or &DECODE statement has a TGT_CHARSET operand that names a character set that is not recognized by ATF.
System Action:
An error is indicated.
User Action:
Check the character set name.
Reason:
Procedure name specified on PROC parameter of &CALL verb is invalid or missing.
System Action:
NCL procedure terminates.
User Action:
Correct NCL procedure and restart it.
Reason:
The system could not obtain storage for new control blocks.
System Action:
NCL procedure terminates.
User Action:
Determine the reason for storage shortage. Rerun the proc.
Reason:
&CALL PROC= statement contains invalid syntax.
System Action:
NCL procedure terminates.
User Action:
Correct NCL procedure and rerun it.
Reason:
An error was detected during an &OSCALL NCL request but the specific error condition could not be accessed.
System Action:
&SYSMSG is set to the error message and processing continues.
User Action:
Correct &OSCALL statement an re-run.
Reason:
An &OSCALL CONVERSE request SDU specified MODE=UNCONFIRMED. For the UNCONFIRMED requests, the receive end of the CONVERSE cannot process responses, hence the request is invalid.
System Action:
&SYSMSG is set to the message and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement and rerun procedure.
Reason:
An &OSCALL SEND or CONVERSE request specified a non-existant SDU.
System Action:
&SYSMSG is set to the message and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement and re-run procedure.
Reason:
A syntax error was detected in the PARM, ATTR, or NAME keyword of an &OSCALL SEND or CONVERSE statement.
System Action:
&OSCALL return code is set to 12, and SYSMSG is set to this message.
User Action:
Correct &OSCALL statement, and rerun.
Reason:
An MDS error occurred while attempting to process an &OSCALL SEND or CONVERSE keyword request.
System Action:
&SYSMSG is set to the message and processing continues with the next NCL procedure statement. &ZMDOFDBK and &ZMDORC are also set to indicate the MDS error.
User Action:
To determine cause of MDS check and correct procedure, review the MDS feedback variables. This error is most likely the result of an invalid data value that is specified for an SDU component.
Reason:
An object services internal storage request failed.
System Action:
The request return code is set to 16 and processing is terminated.
User Action:
Determine the reason for storage shortage. Restart SOLVE region with larger virtual address space size.
Reason:
This message indicates that an error occurred while attempting to map an object services object using mapped data services (MDS).
System Action:
The service fails, and the MDS return code is set.
User Action:
Determine the reason for the mapping error. Correct the request or the object map, and retry.
Reason:
An MDS error occurred when object services attempted to assign a mapped component. The MDS return code and feedback are set in the message.
System Action:
The request fails with return code 8.
User Action:
Diagnose the mapping error using the MDS return code and feedback information.
Reason:
An object services request did not contain a valid object name.
System Action:
The request fails with return code 4.
User Action:
Ensure the object name is correctly specified in the request.
Reason:
An object services create request specified an object name which already exists.
System Action:
The request fails with return code 4.
User Action:
Check that the object name does not already exist.
Reason:
The class specified for an object services request is not defined in the MIB or is invalid.
System Action:
The request is rejected.
User Action:
Specify the correct object class.
Reason:
An attempt was made to delete an object which is being updated by the same process.
System Action:
The delete request is rejected.
User Action:
Check the request.
Reason:
An MDS mapping error occurred while attempting to process an OSCALL RECEIVE statement. The message is returned to the NCL procedure in the &SYSMSG variable.
System Action:
NCL processing continues at the next statement. &ZMDORC and &ZMDOFDBK are set.
User Action:
To determine the reason for the MDS error, review the &ZMDORC and &ZMDOFDBK fields.
Reason:
An Object services reply SDU could not be parsed by MDS.
System Action:
NCL processing continues at the next statement.
User Action:
None.
Reason:
Object services could not build the reply SDU because of a mapping error during assignment.
System Action:
The reply is not built.
User Action:
Check the MDS maps for the request objects.
Reason:
An internal error occurred while processing an &OSCALL RECEIVE statement.
System Action:
NCL processing continues at the next statement. &ZMDORC and &ZMDOFDBK are set.
User Action:
To determine cause of MDS check, review &ZMDORC and &ZMDOFDBK values.
Reason:
MDO processing was unable to obtain enough storage from the system pool to satisfy the last MDO request.
System Action:
Procedure is flushed.
User Action:
Retry request later.
Reason:
An assign statement with an MDO= operand has invalid syntax.
System Action:
Procedure is flushed.
User Action:
Check syntax.
Reason:
An index was used in an MDO= operand where it wasn't expected, or the index value is out of range.
System Action:
Procedure is flushed.
User Action:
Check map definition, and see that this is a valid indexable component, and if so, check that the index does not exceed 32767, or any maximum imposed by a SIZE specification.
Reason:
An error occurred while trying to map an MDO's data during an MDO request.
System Action:
Procedure is flushed.
User Action:
Check program logic. Test that map connection has been performed, and that it was successful. Ensure correct map is in use.
Reason:
The internal recursion stack limit was exceeded while attempting to process an MDO request, possibly caused by having too many segments in a compound name.
System Action:
Procedure is flushed.
User Action:
Reduce number of name segments in MDO name. May require redefinition of the map.
Reason:
A variable indexed MDO name (e.g. MDO=a.b.{*}) was used invalidly.
System Action:
Procedure is flushed.
User Action:
Check use of index on MDO operand.
Reason:
Mutually exclusive operands were used on an &ASSIGN verb using MDO.
System Action:
Procedure is flushed.
User Action:
Check syntax.
Reason:
A feedback was returned during &ASSIGN processing of an MDO which was unexpected.
System Action:
None.
User Action:
Contact your product support representative.
Reason:
This message is only issued if &CONTROL MDOCHK is on. The message indicates a ZMDORC of 8 or 12 was obtained. MDO TYPE CHECK ERROR: ZMDORC=8, ZMDOFDBK=0 MDO DATA CHECK ERROR: ZMDORC=8, ZMDOFDBK=1 MDO NAME CHECK ERROR: ZMDORC=12,ZMDOFDBK=0
System Action:
Procedure is flushed.
User Action:
Determine the reason for the error. Type check: Attempt made to assign invalid data into or from an MDO. Data check: Physical limitations exceeded assigning data to an MDO. Name check: Component name used in MDO assign is not defined in the map.
Reason:
Message is only issued if &CONTROL MDOCHK is set. An attempt to attach a map to an MDO failed because:
- The map wasn't found on the map database.
- The map failed to load due to definition errors.
- The data in the mdo doesn't conform to the map definition.
System Action:
Procedure is flushed.
User Action:
Check that the map is defined, and loads ok, and that the data in the MDO agrees with the map definition. (Issue SYSPARMS MAPLOAD=mapname command to see if map loads ok.)
Reason:
An &OSCALL REGISTER statement was executed from a system procedure environment. This is not allowed.
System Action:
The procedure is terminated.
User Action:
Remove &OSCALL register statement from system level procedure.
Reason:
An &OSCALL deregistration statement was issued for an object which was not owned by the requestor.
System Action:
The procedure is terminated.
User Action:
Correct object definition for request.
Reason:
An NCL process can only register for a single server type. An &OSCALL REGISTER_SERVER statement was issued with a server type that conflicts with the server type specified on a previous registration.
System Action:
The server registration request is rejected and &SYSMSG set.
User Action:
Ensure that all server registration requests are for the same server type and correct the server registration.
Reason:
The name specified in the OBJECT operand of a REGISTER_SERVER request could not be parsed.
System Action:
The server registration request is rejected and SYSMSG set.
User Action:
Check the name assignment for the OBJECT MDO.
Reason:
An invalid internal SOLVE call was detected by the registration processor.
System Action:
The server registration request is rejected and &SYSMSG set.
User Action:
Note the module id and call your SOLVE support center.
Reason:
The dynamic storage available for internal processing was exhausted.
System Action:
The processing thread is terminated.
User Action:
Investigate the reason for the storage shortage, and increase the task region size if necessary.
Reason:
An &OSCALL TYPE=REGISTER-SERVER verb has been issued to register the NCL process as a server, but the base procedure of the process is not an NCL procedure. OML does not support server registration, thus the registration can only performed if the base procedure is NCL.
System Action:
The process is terminated.
User Action:
Convert the base procedure to NCL.
Reason:
An create request attempted to create an object for which the parent did not exist.
System Action:
The create request fails.
User Action:
Ensure the parent object exists before creating the child.
Reason:
An object services DELETE request failed because the object did not exist.
System Action:
No deletion takes place.
User Action:
Check the name specified in DELETE request.
Reason:
An attempt was made to delete an object with children.
System Action:
The delete request is rejected.
User Action:
Delete all of an object's children before issuing a DELETE request for the object.
Reason:
An attempt was made to create an object which already existed.
System Action:
The request is rejected.
User Action:
Ensure a unique object name is specified when creating an object.
Reason:
An &OSCALL RECEIVE request was issued when no client server conversation was active for the request.
System Action:
The procedure is terminated.
User Action:
Correct NCL processing logic to ensure Object Services conversation is active when receive is issued.
Reason:
An attempt to invoke an object method via the &OSCALL verb failed.
System Action:
&SYSMSG is set. Processing continues with next NCL statement.
User Action:
Check return code information to determine reason for failure to connect to method.
Reason:
An attempt by an object server to reply to a client failed. Either the server incorrectly sent the reply, or the client connection was broken during processing.
System Action:
&SYSMSG and return codes are set. Processing resumes at the next statement in the server procedure.
User Action:
Look for other APPC messages to find reason for conversation failure and retry.
Reason:
An &OSCALL request on the Client/Server conversation failed.
System Action:
&SYSMSG and return codes are set. Processing resumes at the next statement in the server procedure.
User Action:
Look for other APPC messages to find reason for conversation failure and retry.
Reason:
A server issued an &OSCALL REPLY but the client had already cancelled the request with an &OSCALL CANCEL.
System Action:
Server procedure continues at next NCL statement.
&RETCODE is set to 8. &ZFDBK is set to 5. &SYSMSG contains the message.
User Action:
The message may be the result of a desired client action.
Reason:
An &OSCALL RECEIVE statement was issued for a request after the final reply was detected. This condition indicates some internal logic error because the final reply always terminates the session.
System Action:
&SYSMSG, &RETCODE and &ZFDBK are set, and processing continues.
User Action:
Get the details of the procedure that issued the request, and report to CA Support.
Reason:
An APPC protocol violation occurred while attempting to process an &OSCALL request during backend processing.
System Action:
The error message is written to the SOLVE system log.
User Action:
Look for other APPC messages to find reason for conversation failure and retry.
Reason:
A storage shortage occurred while attempting to process the OSCALL backend transaction.
System Action:
The error message is written to the log. The object method fails.
User Action:
Investigate the reason for storage shortage. Correct and retry.
Reason:
The OSCALL backend transaction could not map the data received into an SDU. rc/fb represents the MDS RETCODE and FDBK values.
System Action:
The error message is written to the SOLVE system log and the OSCALL backend processing is terminated.
User Action:
Only data in valid SDU format should be sent to the OSCALL backend transaction. Ensure no errant APPC requests are processed.
Reason:
The request flag was not set in an SDU received by the OSCALL back-end transaction processor.
System Action:
The OSCALL backend transaction is terminated.
User Action:
Ensure the OSCALL transaction is only operated via a valid &OSCALL request.
Reason:
The request server located by the OSCALL back end transaction was not for a method or agent server. Requests for other server types are not supported.
System Action:
The OSCALL backend transaction is terminated.
User Action:
Ensure the object services configuration does not involve indirect system registrations.
Reason:
An MDS error occurred while attempting to process an &OSCALL error condition.
The MDS component name, retcode, and feedback are shown in the message.
System Action:
&SYSMSG is set to the message and processing continues with the next NCL procedure statement if NCL is executing.
User Action:
Check the MDS feedback variables to determine cause of MDS check. Verify the component is defined to the SDU map.
Reason:
An object services reply failed because the reply SDU was deleted.
System Action:
No reply is returned to the caller.
User Action:
Check the object methods do not delete the reply SDU.
Reason:
The keyword that is shown in the message is not a valid &OSCALL SEND or CONVERSE keyword.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun procedure.
Reason:
An &OSCALL SEND/CONVERSE statement specified an invalid object class.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun procedure.
Reason:
REQID is not a valid operand on the &OSCALL SEND/CONVERSE NCL statement.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun procedure.
Reason:
An &OSCALL SEND NCL statement specified an ACTION operand that was not valid, or was in conflict with the SERVICE keyword. ACTION can only be specified for SERVICE=ACTION, and the length must not exceed 12 bytes.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun the procedure.
Reason:
A &OSCALL SEND/CONVERSE statement contained an invalid or missing keyword.
System Action:
&SYSMSG is set to this message, and the RETCODE is set to 12. Processing continues at the next NCL statement.
User Action:
Correct the &OSCALL statement syntax.
Reason:
The &OSCALL SEND/CONVERSE MAP= operand, if specified, must be a valid MDS map name.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun procedure.
Reason:
The keyword that is named in the message text is mandatory, and was left out of the &OSCALL SEND or CONVERSE NCL statement.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun procedure.
Reason:
An &OSCALL NCL statement specified a duplicate keyword.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun procedure.
Reason:
An &OSCALL SEND/CONVERSE SERVICE=ACTION NCL statement did not specify an action keyword.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun procedure.
Reason:
An MDS error occurred while attempting to process an OSCALL SEND or CONVERSE keyword request.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement. &ZMDOFDBK and &ZMDORC are also set to indicate the MDS error.
User Action:
To determine cause of MDS check and correct procedure, review the MDS feedback variables. This error is most likely the result of an invalid data value that is specified for an SDU component.
Reason:
The object class that is specified on the &OSCALL NCL statement could not be mapped.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement. &ZMDOFDBK and &ZMDORC are also set.
User Action:
Check that the object class specified on the &OSCALL statement is a valid class and that an MDS map exists for it. Correct the &OSCALL statement, and rerun procedure.
Reason:
The SERVICE operand oooooooooooo on an &OSCALL SEND or CONVERSE NCL statement was not a valid object services SERVICE.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun procedure.
Reason:
The SCOPE operand on an &OSCALL statement is not supported.
System Action:
&SYSMSG is set to the message and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement and re-run procedure.
Reason:
An &OSCALL NCL statement specified an invalid SCOPE operand value.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun procedure.
Reason:
The PARMS keyword is only valid for ACTION service requests on the &OSCALL SEND and CONVERSE NCL statement.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun procedure.
Reason:
An &OSCALL SEND NCL statement specified an invalid NOTIFY operand value.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun procedure.
Reason:
An &OSCALL CONVERSE statement specified an invalid REPLYSDU operand value.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun procedure.
Reason:
An &OSCALL CONVERSE NCL statement specified the NOTIFY operand. This construction is not allowed.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun procedure.
Reason:
The &OSCALL SEND and CONVERSE NCL statements can specify the request in keyword form or as a predefined SDU MDO. These operands cannot be mixed.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun procedure.
Reason:
The &OSCALL NCL statement must specify an SDU MDO.
System Action:
&SYSMSG is set to the error message, and processing continues.
User Action:
Correct the &OSCALL statement, and rerun.
Reason:
The xxxxxx keyword is required for the &OSCALL REGISTER or DEREGISTER statement.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement, and rerun procedure.
Reason:
An &OSCALL send request specified a non-existant SDU.
System Action:
&SYSMSG is set to the message and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL statement and re-run procedure.
Reason:
The &OSCALL ACCEPT NCL statement is only valid from a registered agent server.
System Action:
&SYSMSG is set to the error message and processing continues.
User Action:
Correct &OSCALL statement an re-run.
Reason:
An &OSCALL NCL statement specification of the named operand was invalid.
System Action:
&SYSMSG is set to the error message, and processing continues.
User Action:
Correct &OSCALL statement, and rerun.
Reason:
An &OSCALL TYPE=XCTL verb has been issued to exchange control between the current method and another method. The current method contains active OML procedures, so the XCTL request is invalid. XCTL cannot be done unless all procedures in the method are NCL.
System Action:
The process is terminated.
User Action:
Make sure all procedures in the method are NCL.
Reason:
An &OSCALL TYPE=XCTL verb has been issued to exchange control between the current method and another method. The current method contains active OML procedures, so the XCTL request is invalid. XCTL cannot be done unless all procedures in the method are NCL.
System Action:
The process is terminated.
User Action:
Make sure all procedures in the method are NCL.
Reason:
The object that is specified on the &OSCALL DEREGISTER or REGISTER statement could not be parsed.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Check that the MDO for the object is valid, and rerun.
Reason:
A required SDU component was not present in the &OSCALL request.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the SDU build procedure to include the named component, and rerun request.
Reason:
An &OSCALL statement specified an SDU that contained the named component. The component value was not valid.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Correct the SDU component value, and rerun procedure.
Reason:
A mandatory request component was missing from an object services request.
System Action:
The missing component name is returned in the message.
User Action:
Correct the object services request SDU.
Reason:
The class specified by the &OSCALL request did not exist in the MIB.
System Action:
&SYSMSG is set to the message and processing continues with the next NCL procedure statement.
User Action:
Correct the class or ensure it is added to the system definition tables before re-running procedure.
Reason:
Scoped requests are not valid for the service requested by an &OSCALL.
System Action:
&SYSMSG is set to the message and processing continues with the next NCL procedure statement.
User Action:
Correct the &OSCALL request.
Reason:
The &OSCALL request for object class cccccccc could not proceed. The class was not initialized.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Ensure object services class is initialized before you rerun the request.
Reason:
An &OSCALL SERVICE=ACTION request could not be satisfied because the action was not valid for the specified object class.
System Action:
&SYSMSG is set to the message and processing continues with the next NCL procedure statement.
User Action:
Correct the action requested and re-run procedure.
Reason:
An Object Services request was received, but Object Services initialization failed.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Check the activity log to determine reason for initialization failure, and verify and that you are running with the correct version of the Object Services tables and maps.
Reason:
The requested method procedure was defined for an &OSCALL service request for class cccccccc.
System Action:
&SYSMSG is set to the message, and processing continues with the next NCL procedure statement.
User Action:
Ensure the &OSCALL request was correctly specified and that the class service definition is correct.
Reason:
An Object Services request was made before Object Services initialization was complete.
System Action:
Request is terminated.
User Action:
Ensure object services is initialized before re-issuing request.
Reason:
No selection method is defined for the Managed Object Class for which the Object Services selection request was issued.
System Action:
&SYSMSG is set to the message and processing continues with the next NCL procedure statement.
User Action:
Correct the request and re-run procedure.
Reason:
During logon process an error was encountered when the user record was being written to the user database.
System Action:
The logon is processed.
User Action:
None.
Reason:
An attempt was made to delete a user definition from the user database. The user's definition was not deleted. This message is issued if the security exit does not provide a specific reason for not deleting the user record from the user database.
System Action:
The user definition was not deleted.
User Action:
Determine if the required user record exists and retry operation.
Reason:
An error occurred whilst attempting to read a user from the user database. No specific reason applies.
System Action:
The user definitions was not read.
User Action:
Determine if the required user record is available and retry the operation.
Reason:
There is insufficient system storage available for SOLVE to complete the request. The request is either a LOGON or a READ of a user record.
System Action:
The user logon/read is failed.
User Action:
Determine the amount of storage available to SOLVE and retry the operation when there is storage available to complete the request.
Reason:
The user attempted a logon to SOLVE where a partial security exit was installed. The partial security exit provided a userid modelid whose user definition is to be used as a model for this user's logon.
System Action:
The logon is successful and a new user record is created.
User Action:
None.
Reason:
An attempt to logon has been rejected because the user attempted to logon from a terminal other than those to which the userid is restricted.
System Action:
The logon attempt is unsuccessful.
User Action:
Logon from an authorized terminal.
Reason:
If the system is in a shutdown-pending state, no further logons are allowed.
System Action:
The logon is rejected.
User Action:
The SHUTDOWN CANCEL command could be used to reverse the shutdown process and allow further logons.
Reason:
A logon attempt is denied because the maximum number of users as limited by a MAXUSERS command are already logged on.
System Action:
None.
User Action:
Retry later, or the maximum number of users may be increased with the MAXUSERS command.
Reason:
An attempt was made to log on by a user who is already logged on elsewhere. The user is not authorized for multiple logons.
System Action:
The logon is rejected.
User Action:
Determine why the userid is already in use.
Reason:
An attempt to logon has been rejected because the userid has been `suspended', that is, has been temporarily invalidated for use.
System Action:
The logon fails.
User Action:
Refer to your systems administrator.
Reason:
A logon attempt has been rejected by the security exit. No other information was supplied by the security exit.
System Action:
None.
User Action:
Contact your systems administrator.
Reason:
The logon request or password change was denied. The security exit did not provide a specific message indicating the reason for the failure.
System Action:
None.
User Action:
Logon again and change password if requested.
Reason:
A request to obtain userid information failed. The security exit did not provide a specific reason for the failure.
System Action:
The read request is rejected.
User Action:
Contact your systems administrator as this may indicate that the UAMS dataset is corrupted.
Reason:
An error occurred when attempting to update userid information on the UAMS dataset, or the security exit supplied by the system rejected the update request. No specific reason was provided by the security exit.
System Action:
None.
User Action:
Contact your systems administrator.
Reason:
An attempt to add a new user record has failed. No specific reason was provided by the security exit for the failure.
System Action:
The user record is not added.
User Action:
Contact your systems administrator for more information.
Reason:
This message reports a logon attempt that failed because the user entered their password in error more than the maximum number of times. It is sent to the system Log and to OCS operators who have monitor status.
System Action:
None.
User Action:
This may indicate an illegal attempt to gain access to the system. If the attempts continue you should report the matter to your systems administrator.
Reason:
The security exit has returned a non-zero return code. This return code is invalid. SHUTDOWN processing continues.
System Action:
Shutdown continues.
User Action:
None.
Reason:
The Access Control feature has denied access to this port.
System Action:
The logon is rejected.
User Action:
This may be a time restriction. Try again when access is allowed. If necessary contact your system administrator.
Reason:
The Access Control feature has denied remote host access.
System Action:
The logon is rejected.
User Action:
This may be a time restriction. Try again when access is allowed. If necessary contact your system administrator.
Reason:
The security subsystem has denied user P1 access to this port.
System Action:
The logon is rejected.
User Action:
Contact your system administrator to provide authorization.
Reason:
The security subsystem has denied user P1 host access.
System Action:
The logon is rejected.
User Action:
Contact your system administrator to provide authorization.
Reason:
You attempted to connect to the region while it is initializing.
System Action:
None.
User Action:
Wait until the region completes initialization, and then try again.
Reason:
An attempt to read a user record has failed because the user record 'uuuuuuuu' does not exist on the UAMS user database.
System Action:
The security function fails.
User Action:
Refer to your systems administrator.
Reason:
The user attempted a logon to SOLVE when there was no UAMS user record on the user database. However, a model user was defined to SOLVE using SYSPARMS MODLUSER=. The password that was provided by the user matches that of the model user and the logon proceeds. A user record is created for userid 'uuuuuuuu' based on 'modelid'.
System Action:
The logon is successful and a new user record is created.
User Action:
None.
Reason:
'modelusr' was specified as a model user through the SYSPARMS command. The model userid is not defined on the UAMS dataset.
System Action:
The logon is rejected.
User Action:
Define the required model userid to UAMS.
Reason:
The UDB record is stored in an encrypted form. Record retrieval was unable to decrypt the record. The wrong file may be in use or it contains invalid records.
System Action:
The function terminates.
User Action:
Refer this problem to your systems administrator for action.
Reason:
The UDB record is stored in an encrypted form. Record retrieval was unable to decrypt the record. The wrong file may be in use or it contains invalid records. The record key contains non-display characters and is displayed in hex format.
System Action:
The function terminates.
User Action:
Refer this problem to your systems administrator.
Reason:
An attempt was made to logon to a UAMS Group definition. Group definitions are not available for logon and the logon is rejected.
System Action:
The logon request is rejected.
User Action:
Logon to a valid user definition.
Reason:
An attempt was made to logon or retrieve a user definition from the UAMS database. The user definition has a group user defined; however, this group definition is not a valid group definition.
System Action:
The request is rejected.
User Action:
Contact your systems administrator.
Reason:
The UAMS dataset is full and the requested 'function' for userid 'uuuuuuuu' failed.
System Action:
The request is rejected.
User Action:
Contact your systems administrator to increase the size of the UAMS dataset or to delete obsolete user definitions.
Reason:
An I/O error occurred whilst performing security 'function' for the userid 'uuuuuuuu'. The request is rejected.
System Action:
The request is rejected.
User Action:
Refer the problem to your systems administrator to determine the reason for the error.
Reason:
An internal request to update a user definition resulted in the userid
uuuuuuuu being added to the UAMS dataset.
System Action:
The user definition was added to the UAMS database.
User Action:
None; the update request completed successfully.
Reason:
An attempt was made to add a new user definition to the UAMS database. The userid uuuuuuuu already exists is the UAMS database.
System Action:
The request to add the new user definition to the UAMS database is rejected.
User Action:
Correct the userid on the ADD function and retry.
Reason:
An attempt was made to delete a user record ('userid') from the UAMS database. The user record was not found.
System Action:
None.
User Action:
Correct the userid and retry the DELETE operation.
Reason:
An &SECCALL GET OPT=KGT or KLT command was issued. The next sequential record on the user database for userid uuuuuuuu was invalid and was ignored. The next sequential record following or preceding the invalid record was read. This message is written to the activity log.
System Action:
The next sequential record is read.
User Action:
Contact your systems administrator in order that the user record in error can be corrected.
Reason:
An attempt was made to change the password of the group definition 'groupname'. This is invalid as group definitions cannot be logged on.
System Action:
The password change terminates.
User Action:
Correct the userid and retry.
Reason:
A user 'uuuuuuuu' is defined as using the privileges of a group definition. The group definition is not available. The user's privileges have been reset to the defaults. The logon, or the read, continues.
System Action:
The user's privileges are reset. The logon, or read, continues.
User Action:
Contact your systems administrator.
Reason:
The structured field processor determined that one (or more) structured field(s) passed to, or returned from the security exit was in error. The details of the structured field(s) in error are written to the activity log.
System Action:
The structured field is ignored.
User Action:
Correct the structured field(s) in error and retry the operation.
Reason:
There was insufficient storage available to complete the security request.
System Action:
The request is not completed.
User Action:
Try the request later. If the problem persists, contact your product support representative.
Reason:
A security sub-system exit has passed an invalid structured field ( P1 ) or an invalid structured field was passed by an &SECCALL verb.
System Action:
This message is written to the activity log. The security request proceeds; however, the particular structured field in error is ignored.
User Action:
Identify the structured field in error and correct the error, either by correcting the NCL or the security exit.
Reason:
The NCL procedure bbbbbbb set a return code indicating that update of its target object instance was to be ignored. Execution of the system method routine is bypassed and the Object Instance is not updated in the repository.
System Action:
The message is returned to the client in the reply SDU.
User Action:
None.
Reason:
Object Services Framework generated reply to client failed.
System Action:
Message is logged.
User Action:
Check system log for possible causes.
Reason:
An Object Services request could not be processed due to insufficient virtual storage.
System Action:
The request is terminated.
User Action:
Look for possible causes of high storage utilisation. Increase virtual storage address space size.
Reason:
The Object Services Request Broker could not initialize the method for an object request. This usually indicates a problem with building the Mapped Data Objects (MDOs) or may indicate a resource shortage.
System Action:
The service routine is not executed.
User Action:
Reason:
The Object Services Data Domain aaaaaaaa open failed either because the file could not be opened, or the dataset keylength was invalid.
System Action:
The request is rejected.
User Action:
Verify that the repository data domain is correctly defined and available for the required access level.
Reason:
The instance name passed to the object services access method could not be parsed.
System Action:
Access to the system repository is rejected.
User Action:
Check the request parameters, and verify mds maps for object class.
Reason:
The object services repository access method could not acquire sufficient storage to process the request.
System Action:
The request is rejected.
User Action:
Check that sufficient storage has been allocated to the address space and that there are no errant processes holding excess storage.
Reason:
A request to CREATE an object instance was issued and an instance with the same name already exists.
System Action:
The request is rejected.
User Action:
Check the name passed in the request.
Reason:
An attempt to access the repository dataset failed with the VSAM FDBK bb. The access type is aaaa.
System Action:
The request is rejected.
User Action:
Review the VSAM FDBK for the function specified in the message.
Reason:
A CREATE request was issued for an object whose parent did not exist.
System Action:
The request is rejected.
User Action:
Review the service request parameters.
Reason:
The object instance specified in the service data unit did not exist.
System Action:
ERRORID of NOSUCHOBJECTINSTANCE is set in the reply SDU.
User Action:
Check the name specified in the Service Data Unit.
Reason:
An attempt was made to CREATE or update an object instance in the repository, and the maximum data domain record size was too small to contain the object.
System Action:
The request is rejected.
User Action:
Check the size requirements for the object instance.
Reason:
An update request was issued for a repository which was in read-only mode.
System Action:
The request is rejected.
User Action:
Check the access mode for the repository.
Reason:
A DELETE request was received for an object with dependant children.
System Action:
The request is rejected.
User Action:
Review the request.
Reason:
An attempt to maintain the data domain root record failed. This message usually indicates a logical error exists on the data domain data set.
System Action:
The request is rejected.
User Action:
Check the integrity of the data domain data set. If necessary, restore the data domain from backup.
Reason:
The data domain required to service the object services request is not available.
System Action:
The request is rejected.
User Action:
Look for other messages in the log to determine why data domain initialization failed.
Reason:
No reply is expected for an unconfirmed request. &OSCALL CONVERSE anticipates a reply, hence it is not valid to issue an unconfirmed request using &OSCALL CONVERSE.
System Action:
The request is rejected.
User Action:
Use &OSCALL SEND, or change the type to CONFIRMED.
Reason:
The object instance name passed in the service request could not be parsed.
System Action:
The request is rejected.
User Action:
Check the request parameters.
Reason:
An attempt to access the system directory failed because not enough storage was available to process the request.
System Action:
The request is rejected.
User Action:
Check your system storage utilisation.
Reason:
The object name specified in the service data unit could not be located in the system directory.
System Action:
The reply ERRORID is set to NOSUCHOBJECTINSTANCE.
User Action:
Check the instance name passed in the request.
Reason:
An attempt to compare an event to the filter specified on the Event Forwarding Discriminator (EFD) failed.
System Action:
Processing of the event continues with the next Event Forwarding Discriminator.
User Action:
Check the EFD filter is valid. It may also be necessary to check that the event mdo is correctly mapped.
Reason:
An object services selection request could not be processed for one of the following reasons:
- The request CMISFILTER parameters were invalid.
- The NAMEFILTER was invalid.
- A data domain for the object was not available.
System Action:
The request is rejected.
User Action:
Correct the request parameters depending on the reason for the failure.
Reason:
An Object Services selection method could not continue because the number of levels in the Base Object hierarchy exceeded 28.
As it is unusual to have this many levels in the naming hierarchy, this error may indicate a recursive naming structure.
System Action:
The selection method is terminated.
User Action:
Verify the integrity of the repository data structure.
Reason:
The Object Services Selection method detected an error while processing an internal mapped data structure. The component is: aaaaaaaaaaaaaaaaaaaaaa, mds retcode bb, mds fdbk is cc.
System Action:
Processing of the selection request is terminated.
User Action:
Verify the map definitions for all object classes which are the target of the request. Check the request parameters.
Reason:
The Object Services selection method could not acquire sufficient storage to process a request.
System Action:
The selection method is terminated.
User Action:
Check system storage utilisation.
Reason:
A system error occurred when the object services request broker attempted to access the class record aaaaaaaaaaaa.
System Action:
The request is rejected.
User Action:
Review the activity log to determine the cause of the class initialization failure. Particularly note any object services initialization errors that occurred during NetMaster initialization.
Reason:
An internal MDS assignment failed while processing an object services request.
System Action:
The request is rejected.
User Action:
Determine the reason for the MDS error from the return code, feedback and mapname in the message.
Reason:
The object instance named in the object services request could not be located in the system repository.
System Action:
The reply ERRORID is set to NOSUCHOBJECTINSTANCE.
User Action:
Check the request name parameters.
Reason:
A request was passed to the object services access method for an unsupported object data domain type.
System Action:
The request is rejected.
User Action:
Check the object class specification.
Reason:
A request was passed to the Object Services access method, which required access to an unavailable data domain.
System Action:
The request is rejected.
User Action:
Check the activity log for messages indicating why the data domain is not initialized.
Reason:
An update request was passed to the object services access method routines and the class for the managed object instance is not available for update.
System Action:
The request is rejected.
User Action:
Check request parameters.
Reason:
The object services access method could not parse the name of the object instance passed in the request.
System Action:
The request is rejected.
User Action:
Check the request name parameters.
Reason:
Lookup of the object class by the object services broker failed. Class aaaaaaaaaaaa was not defined to the MIB.
System Action:
The request is rejected.
User Action:
Check the class specification for the request.
Reason:
Object Services is disabled because system initialization failed.
System Action:
The request is rejected.
User Action:
Check the activity log for initialization messages that indicate why the initialization of Object Services failed.
Reason:
The system MIB object ZOSMIB load failed. This is the root object for the MIB.
System Action:
Object Services is disabled.
User Action:
Check the SOLVE activity log for other messages which indicate the reason for the load failure. Correct and re-start SOLVE.
Reason:
The Object Services kernel class aaaaaaaaaaaa could not be loaded. This is usually because the ZOSMIB data domain cannot be accessed or the MIB has not been created.
If initialization is unable to continue, the message says: OBJECT SERVICES INITIALISATION FAILED. If this is not present in the message, initialization proceeds using default values for the missing object.
Note: By default the ZOSMIB data domain is in the OSCNTL file.
System Action:
Initialization continues.
User Action:
If the error was due to file errors on the OSCNTL file, you must recover the OSCNTL file and restart SOLVE.
If your MIB has not been compiled, compile it before proceeding with Object Services initialization.
Reason:
The data domain definition for aaaaaaaaaaaa could not be loaded.
System Action:
Object Services is disabled.
User Action:
Check the SOLVE system log for the reason and re-start SOLVE.
Reason:
The action definition for aaaaaaaaaaaa cannot be loaded.
System Action:
Initialization continues. Some Object Services functions are disabled.
User Action:
Review the activity log for the reason for the failure.
Reason:
An system object map failed during Object Services initialization.
System Action:
Object Services is disabled.
User Action:
Ensure that the OSCNTL file has been correctly installed. It may be necessary to re-install and re-compile if the ZOSMIB map is invalid. Alternatively re-generate the ZOSMIB map from source and re-start system.
Reason:
There was insufficient storage to initialize Object Services.
System Action:
Object Services is disabled.
User Action:
Increase the SOLVE region size.
Reason:
Delivery of an event to server aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa failed for one of the following reasons:
- Insufficient Storage; MDS mapping error; The connection to the server failed.
System Action:
The event report is not delivered.
User Action:
Check the server specified on the EFD is active.
Reason:
An attempt to open the VSAM data set for repository data domain aaaaaaaa failed for reason bbbbbbbbbbbbbbbbbbbb.
System Action:
The data domain is unavailable and the data domain initialization action terminates.
User Action:
Review system log for reason for dataset open failure.
Reason:
The data domain attribute bbbbbbbbbbbbbb must be set before the data domain aaaaaaaaaaaa can be opened.
System Action:
The data domain is disabled.
User Action:
Ensure that the data domain is correctly specified. Recompile MIB if necessary.
Reason:
Dataset allocation failed for repository data domain.
System Action:
The data domain is disabled.
User Action:
Review allocation error messages in the activity log.
Reason:
A VSAM error occurred when the Object Services data domain initialization routine attempted to retrieve the data domain definition record.
System Action:
The data domain is disabled.
User Action:
Check dataset integrity for the data domain.
Reason:
The instance identifier set in the system is invalid. This indicates possible corruption of the repository data domain.
System Action:
The data domain root record is not updated.
User Action:
Verify integrity of the repository dataset.
Reason:
The dataset allocated to Data Domain aaaaaaaaaaaa was previously opened for a different Data Domain definition bbbbbbbbbbbb.
System Action:
The data domain is disabled.
User Action:
Ensure that each dataset is allocated to only one Data Domain.
Reason:
The object mdo specified for an object services method is invalid for one of the following reasons:
- OBJECT CLASS MISSING - CLASSID is required component of object.
OBJECT MDO NOT FOUND - The object mdo could not be found.
System Action:
The request is rejected.
User Action:
Correct the &OMCALL NCL statement.
Reason:
The object name specified for an object services method does not exist in the Object Instance Repository.
System Action:
The request is rejected.
User Action:
Verify the object name.
Reason:
The Managed Object Class aaaaaaaaaaaa has not initialized in the MIB.
System Action:
The request is rejected.
User Action:
Check the activity log for messages indicating why the MIB class build failed.
Reason:
The OIS method service routine was passed a request for an object which is not defined with OIS support.
System Action:
The request is rejected.
User Action:
This is a system error. Ensure that the class definitions have been specified correctly and that they have not been dynamically modified.
Reason:
An internal MDS assignment failed in the Object Services OIS method routine.
System Action:
The request is rejected.
User Action:
Use the MDS RETCODE and FDBK to determine the cause of the failure.
Reason:
The OBJECT operand was not specified on an &OMCALL statement and the $OSOBJECT MDO was not available in the NCL procedure.
System Action:
The &OMCALL statement is ignored.
User Action:
Specify the OBJECT operand on the &OMCALL statement, or ASSIGN an MDO to $OSOBJECT.
Reason:
A DELETE request for a Managed Object Instance was rejected by a the system resource manager. System methods may reject deletion requests for protected resources.
System Action:
The DELETION request is rejected.
User Action:
N/A
Reason:
An invalid object was passed to the Object Services ZOSEFD system method
System Action:
The request is rejected.
User Action:
Correct the EFD request SDU.
Reason:
The CMIS filter passed in an EFD service request could not be parsed.
System Action:
The EFD request is rejected.
User Action:
Correct the CMIS filter specification.
Reason:
An EFD service request contained more than the maximum number of destinations allowed.
System Action:
The EFD service request is rejected.
User Action:
Reduce the number of destinations for the EFD.
Reason:
The system object services selection method failed for the managed_ object_instance of managed_object_class.
System Action:
A message containing the reason for the failure is returned in the reply SDU.
User Action:
Check the reply SDU and correct the selection request.
Reason:
The Object Services system selection method could not process the CMIS filter against a selected object.
System Action:
Selection processing is terminated.
User Action:
Check the CMIS filter specified on the selection request.
Reason:
A nested NCL selection procedure was required to complete a selection request by the system selection routine. The NCL selection method execution failed.
System Action:
Processing of the selection request is terminated.
User Action:
Check that selection methods defined to the MIB are correctly installed.
Reason:
An attempt to return a selected object by the Object Services selection method failed because an MDS error occurred on the object assignment.
System Action:
Processing for the selection method is terminated.
User Action:
Check object maps are correctly defined.
Reason:
Object Services Selection method processing failed.
System Action:
Processing for the selection method is terminated.
User Action:
Check selection request parameters.
Reason:
An APPC protocol violation occurred while attempting to process a DIRECTORY_QUERY system transaction.
System Action:
The error message is written to the SOLVE system log.
User Action:
Look for other APPC messages to find reason for conversation failure and retry.
Reason:
A storage shortage occurred while attempting to process the DIRECTORY_QUERY APPC transaction.
System Action:
The error message is written to the log. The object method fails.
User Action:
Investigate the reason for storage shortage. Correct and retry.
Reason:
An MDS error occurred while the system action routine was attempting to build a request SDU.
System Action:
The system action request is not issued.
User Action:
Check the MDS feedback information to determine the cause of the mapping failure.
Reason:
During Object Services Termination, a system request could not be processed because there is insufficient storage.
System Action:
Object Services Termination can not continue.
User Action:
Ensure that sufficient Virtual Storage is allocated to the SOLVE address space.
Reason:
An attempted password change operation has been rejected because the password supplied as the CURRENT password was incorrect.
System Action:
None.
User Action:
Enter correct password.
Reason:
An installation defined minimum or maximum password length applies.
System Action:
None.
User Action:
Choose a password whose length conforms with you installation's security standards. If in doubt contact your systems administrator.
Reason:
In response to a request to change passwords a replacement password has been entered that is the same as the existing password. A replacement password must be different.
System Action:
None.
User Action:
Enter a different password.
Reason:
The field marked by the cursor is invalid. The only values that can be assigned are Y or N.
System Action:
None.
User Action:
Correct and re-enter.
Reason:
The field marked by the cursor is invalid.
System Action:
None.
User Action:
Correct and re-enter.
Reason:
If X were allowed as the initial command executed automatically on entry to Operator Control Mode it would cause immediate exit to the primary menu. For this reason it is not allowed.
System Action:
None.
User Action:
Correct the command field and retry.
Reason:
These two fields are mutually exclusive and cannot both be set to the same value.
System Action:
None.
User Action:
Correct the fields and retry.
Reason:
These two fields are mutually exclusive and cannot both be set to the same value.
System Action:
None.
User Action:
Correct the fields and retry.
Reason:
This message appears on the activity log only. Indicates that the system has initialized an empty VSAM dataset and shows the associated DD name ( P1 ).
System Action:
For a VSAM KSDS, a low key record x'00' is inserted and then deleted. For an ESDS, a record consisting of message N28510 is inserted as the first record in the dataset and remains in the dataset.
User Action:
None.
Reason:
A VSAM dataset failed to open in CREATE mode for the specified error reason code (P1), in the format X'xy'. The DD name associated with the dataset is shown (P2). Empty VSAM datasets are opened in CREATE mode in order to perform an initial load.
System Action:
The system terminates with a user abend code if the dataset is a system dataset. If the dataset is a User DataBase (UDB) processing continues but the dataset is not available for NCL procedure processing.
User Action:
Enter /VSAMRC at the command prompt to access NETINFO : Browse VSAM OPEN Macro Return Codes. Enter the ACB code value in the VSAM error code field and press Enter.
Refer to the appropriate VSAM Programming manual for an explanation of the error code.
Reason:
A VSAM dataset failed to open in UPDATE mode for the specified error reason code (P1), in the format X'xy'. The DD name associated with the dataset is shown (P2).
System Action:
The system terminates with a user abend code if the dataset is a system dataset; if the dataset is a User DataBase (UDB) processing continues but the dataset is not available for NCL procedure processing.
User Action:
Enter /VSAMRC at the command prompt to access NETINFO : Browse VSAM OPEN Macro Return Codes. Enter the ACB code value in the VSAM error code field and press Enter.
Refer to the appropriate VSAM Programming manual for an explanation of the error code.
Reason:
When a UDB is opened, it is tested to determine if it is empty (not previously loaded). If the dataset is empty, VSAM requires that it be loaded before it can be processed in update mode. In such cases the dataset is opened in create mode and inserts an initialization record. The attempt to do this has failed. The DD name (P1) is shown.
System Action:
The UDB is not available for further processing.
User Action:
Determine the cause of the error, correct and retry.
Reason:
An attempt to build an LSR pool, by calling module NMDEFLSR, resulted in the module returning the indicated value ( P1 ) in Register 15.
System Action:
The UDB requesting LSR processing will not be opened.
User Action:
Use the VSAM Programming Guide to determine the reason for the error, the R15 value is the return code from the BLDVRP macro.
Reason:
A UDB was opened requested LSR processing. The open request was the first that required the indicated LSR pool ( P1 ).
System Action:
The LSR pool has been built using the specifications as defined in the LSRPOOL command.
User Action:
None.
Reason:
The last UDB using the indicated LSR pool has been closed. The LSR pool ( P1 ) has been deleted.
System Action:
None.
User Action:
If necessary the format of the LSR pool can be changed by modifying the LSRPOOL command. Any such changes will be utilized when the next UDB is opened that requires LSR processing.
Reason:
During open processing a VSAM warning class message was detected. The warning code ( P1 ) is shown in the format X'xy'. The associated DD name is also shown ( P2 ).
System Action:
Processing continues and the dataset is classified as having been opened successfully.
User Action:
Investigate the reason for the error using the VSAM Programming Guide and determine if the error will impact processing. Take corrective action if necessary.
Reason:
This message is inserted as the first record in an ESDS UDB that required load processing. VSAM necessitates that new datasets be opened in create mode and a minimum of one record be inserted before the dataset can be shared. For KSDS datasets this record is later deleted. For ESDS datasets it is not possible to delete the record. The time ( P1 - hh.mm.ss) and date ( P2 -day-dd.mon-year) are included as part of the data.
System Action:
This record remains as the first record in the dataset and provides a record of the date and time the dataset was loaded.
User Action:
If not required in the dataset, this record can be dropped by using the VSAM IDCAMS utility to REPRO the dataset specifying the SKIP(1) operand to start the copy at the second record.
Reason:
An attempt to open a VSAM dataset, (DD name P1 ), has failed for the stated reason ( P2 ).
System Action:
If the dataset is a system dataset, for example the VFS, PANELS or USERIDS dataset, the region will abend with message N92049, abend code 285-09. If the dataset is a UDB (being opened by a UDBCTL command) the open fails.
User Action:
Examine the reason for the failure. Use Access Method Services to delete and redefine the dataset correctly.
Reason:
An error occurred trying to open an optional system dataset, and a subsequent attempt to close the VSAM ACB failed.
P1 = Return code from ACB CLOSE (X'xy').
P2 = Error Code from SHOWCB.
P3 = JCL DD name associated with the dataset.
System Action:
If the dataset is not a mandatory system dataset, then the system continues this dataset.
User Action:
Investigate why the dataset is in error.
Reason:
An attempt to invoke the VSAM utility program utilname failed.
System Action:
The system terminates with a user abend code.
User Action:
Determine the reason for the load failure and restart SOLVE.
Reason:
A request for an Extended Format / Extended Addressability ESDS has failed for the DD name indicated ( P1 ). ESDS support is limited to datasets below 4GB.
System Action:
The request fails.
User Action:
Change your NCL procedure to use either:
- a smaller ESDS
- a KSDS.
Reason:
This Monitor message indicates that one or more VSAM string or buffer shortages has occurred. In the message:
P1 is the shortage type, for example, STRING or BUFFER
P2 is the DD name.
The SHOW VSAM command can be used to determine the total number of string and buffer shortages that have occurred. A large number indicates that system tuning is required to avoid significantly impacting performance.
System Action:
Processing is suspended for that request until sufficient resources are available.
User Action:
If the LSR pool is indicated as the source of the problem, use the LSRPOOL command to provide more VSAM processing strings or buffers. For more information, see your systems administrator.
Reason:
When using deferred I/O an attempt to write a record has resulted in an error although the system previously indicated that the record was written successfully. In an MVS-type environment, message N28805 will follow with additional details. In the message:
P1 is the VSAM error code (X'xy')
P2 is the DD name.
System Action:
Processing continues.
User Action:
Refer to the VSAM Programmers Guide to determine the reason for the error and if it is likely to impact processing. Deferred I/O should not be used for critical datasets where errors of this nature could result in the loss of data. If necessary avoid using the DEFER option on the UDBCTL command when opening the dataset. Refer to your systems administrator.
Reason:
During processing of the VSAM file, described by the ddname in the message, a VSAM macro return code indicated a physical error had occurred. The message provides the corresponding RPL feedback code ( P1 ) and DD name ( P2 ).
System Action:
The file processing request fails.
User Action:
Refer to the VSAM Programming manual to determine the meaning of the feedback from the message and the appropriate course of corrective action. If the dataset with the I/O error has been opened using the LSR option, it should be closed and opened to free the LSR Buffer that was being used at the time of the error.
Reason:
This message is issued as a result of a physical I/O error on a VSAM dataset on an MVS (or equivalent) system. It will be preceded by message N28803. The information contained in the message is as returned by VSAM ( P1 ) in the form: yyddd,hhmmssth,rbaaddr ,d-or-i,volser,jobname ,j
System Action:
The file I/O request fails.
User Action:
Refer to message N28803.
Reason:
A &FILE verb has been issued using an invalid generic key length or with the GENLEN= parameter supplied with a null variable.
System Action:
The &FILE verb fails with &FILERC=8 and &SYSMSG set to the N28806 message text.
User Action:
Investigate the reason for the error and correct the NCL program logic as required.
Reason:
The failing statement contains invalid syntax.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
The required source data is missing from the failing statement.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
The failing statement does not contain a required keyword.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
The required source data for the function has been omitted from the failing statement.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
An invalid number has been specified on the failing statement.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
An invalid hexadecimal number has been encountered on the failing statement.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
An invalid hexadecimal string has been encountered on the failing statement.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
An invalid name has been encountered on the failing statement.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
An invalid variable name has been encountered on the failing statement.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
An invalid resource name has been encountered on the failing statement.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
An invalid data length is specified on the failing statement.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
A number has been specified on the failing statement which is outside of the range of expected values.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
A duplicate keyword has been encountered on the failing statement.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
The failing statement is either invalid or a required keyword is missing.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
A required keyword has been omitted from the failing statement.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
An invalid or reserved keyword has been encountered on the failing statement or command.
System Action:
The entered command or NCL procedure fails.
User Action:
Correct and retry.
Reason:
The failing statement cannot be processed because of conflicting keywords.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
Invalid range numbers have been found on the failing statement.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
Invalid range numbers have been found on the failing statement.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
A required keyword has been omitted from the failing statement.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
The failing statement has invalid syntax.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
The failing statement has a missing parenthesis or incorrectly paired parentheses.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
The failing statement requires one or more variables for the requested function.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
The failing statement contains an invalid variable name or generic prefix.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
The failing statement specifies a null variable.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
The failing statement contains a string enclosed in quotes but there is no closing quote to delimit the string.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
The failing statement contains a single quote that is neither enclosed in quotes itself nor is delimiting a string enclosed in quotes.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
The failing statement contains a domain name which does not comply with the syntax rules for domain names. That is, it is longer than 4 characters or contains invalid values.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
This message is produced while parsing a command or NCL verb when an invalid name pattern is found.
A name pattern must by a valid PDSNAME-format character string, where the first character is alphabetic or national, and the remaining characters alphanumeric or national.
The name pattern can have two additional characters in any position, the question mark (?) meaning a 1-character wildcard (matches any single pattern), and the asterisk (*), meaning that 0 or more characters will match at this point.
For example, ABC? matches ABCD, ABCX. ABC* matches ABC, ABCD, ABC1 *ABC matches ABC, XXABC, X7ABC
System Action:
The command or NCL statement is rejected.
User Action:
Correct the name pattern.
Reason:
The failing statement contains a character or hex data string which is longer than the maximum allowed.
System Action:
The procedure fails.
User Action:
Correct and retry.
Reason:
The operand in error requires an NCL prefix value. An NCL prefix value must start with a non-numeric and contain valid NCL naming characters.
System Action:
The function is terminated in error. Message N29549 is issued indicating the operand in error.
User Action:
Correct the operand indicated by message N29549.
Reason:
The failing statement has been signaled as being in error by a user exit.
System Action:
The procedure fails.
User Action:
Correct, and retry.
Reason:
This message will follow another N295xx message if the parameter that caused the error can be detected. parm displays up to 50 characters of the parameter in error.
System Action:
As for the preceding message.
User Action:
As for the preceding message.
Reason:
This message is issued when an attempt to connect to another region fails. It indicates that the outgoing connect request failed. The fields in the message are:
P1 - The target region's primary APPL name.
P2 - The failure reason:
UNABLE TO CHOOSE ACCESS METHOD The system was unable to pick an access method (eg VTAM) for the connection request; no access method was specified on the LINK START or DEFLINK command, and a domain definition (DOMAIN command) for the target prevented choice of an active access method.
REQUESTED ACCESS METHOD DENIED The connection request had a specific access method eg VTAM. However a DOMAIN DEFINE command has been entered for the target and that access method has been specified as NO.
System Action:
The connection is not started.
User Action:
Examine the reason. Common causes are having a wrong DOMAIN definition table entry (Wrong access methods enabled), or not having all the required access methods active (eg TCP/IP).
Reason:
An attempt was made to set the VTAM Generic Resource System Parameter (GENRSRC) while the region's primary VTAM ACB is open.
System Action:
The command is ignored.
User Action:
To change the GENRSRC parameter, the region's primary VTAM ACB must be closed. This parameter should be set either by the GENRSRC JCL parameter in your region's RUNSYSIN, or by setting the name in the $AC INIT parameter group and recycling this region.
Reason:
An attempt to set the VTAM Generic Resource system parameter (GENRSRC) to NO failed.
System Action:
The command is ignored.
User Action:
Refer to the activity log for details about this failure.
Reason:
An OPNDST command was rejected because your command authority restricts you to LU1 printers.
System Action:
The command is rejected.
User Action:
Contact your systems administrator.
Reason:
This message is issued in response to an APPLSTAT command and indicates that the request to monitor a VTAM application name ( P1 ) was accepted.
System Action:
The system monitors the application.
User Action:
None.
Reason:
This message is issued in response to an APPLSTAT command. The message indicates that the request to monitor a VTAM application name ( P1 ) failed because there is already an active request for this application.
System Action:
The request is ignored.
User Action:
Use the SHOW APPLSTAT command to list active monitoring requests.
Reason:
This message is the heading line for a SHOW APPLSTAT command. For more information, see message N29Y02.
System Action:
None.
User Action:
None.
Reason:
This message is the detail line for a SHOW APPLSTAT command. The following fields are displayed:
P1 - The VTAM application name
P2 - The current status
P3 - The time that the status was last updated
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW APPLSTAT command where one of the following applies:
- No application monitoring requests exist
- No definitions match the application name criteria provided
System Action:
None.
User Action:
If an application name pattern was provided, try using a different pattern.
Reason:
A DEBUG command has been entered but the keyword following the DEBUG keyword is not valid. This second keyword is used to identify the type of DEBUG command entered.
System Action:
The DEBUG command is rejected.
User Action:
Correct the DEBUG command and retry.
Reason:
A DEBUG START command has been entered with the DEBUGID operand to connect to a suspended debug session but no suspended debug session exists with the specified debugid.
System Action:
The DEBUG command is rejected.
User Action:
Correct the DEBUGID operand and retry. The SHOW DEBUG command can be used to obtain the debugid.
Reason:
A DEBUG START command has been entered with the NCLID operand to gain debug control over an executing NCL process. The NCL process is already under control of debug.
System Action:
The DEBUG command is rejected.
User Action:
The SHOW DEBUG command may be used to find out which user is debugging the NCL process.
Reason:
A DEBUG START command has been entered which has targeted exactly the same scope as another DEBUG START in the system. It is invalid for different debug scopes to specify exactly the same criteria.
System Action:
The DEBUG command is rejected.
User Action:
Correct the DEBUG command operands and retry. The SHOW DEBUG command can be used to find out which user has entered the identical DEBUG START command.
Reason:
A DEBUG START command has been entered with the NCLID operand to target a specific NCL process but the NCL process is not executing in the system.
System Action:
The DEBUG command is rejected.
User Action:
Correct the NCLID operand and retry.
Reason:
A DEBUG START command has been entered to debug NCL which is executing in another users region but the command issuer does not have sufficient authority to debug NCL owned by another user.
System Action:
The DEBUG command is rejected.
User Action:
None.
Reason:
A DEBUG START command has been entered but a storage shortage has prevented the system from starting the debug session.
System Action:
The DEBUG command is rejected.
User Action:
Investigate the reason for the storage shortage.
Reason:
A DEBUG START command has been entered with the DEBUGID operand to connect to a suspended debug session but the command issuer already has a debug session active.
System Action:
The DEBUG command is rejected.
User Action:
The DEBUG STOP command may be used to suspend the current debug session. The DEBUG START command may then be used to connect to the suspended debug session.
Reason:
A DEBUG START command has been entered and has successfully begun debug processing.
System Action:
Debug processing begins.
User Action:
Other DEBUG commands may be used to control the NCL processes which are being debugged.
Reason:
A DEBUG START command has been entered without the KEEP=YES operand and the targeted WINDOW/REGION/USER does not currently exist.
System Action:
The DEBUG command is rejected.
User Action:
The KEEP=YES operand may be entered to allow the debug to begin without the window/region/user existing. This allows debug to be started on user region such as APPC which are transient and to not exist for long periods of time.
Reason:
A DEBUG STOP command has been entered with the NCLID= operand to stop debug of a particular NCL process. The command has been successfully processed.
System Action:
Debug control has been removed from the specified NCL process.
User Action:
None.
Reason:
A DEBUG START command has been entered which specified the NCLID of a procedure which is not eligible for debug. This may be for one of the following reasons:
- the process is a LOCKPROC system process
- the process is a MSGPROC and the DEBUG START command was entered from the environment in which the MSGPROC is executing. This is invalid because if the process became suspended the debugging user would no longer be able to see command responses.
- the DEBUG START command was entered from within the dependent (&INTCMD) environment of the nominated process. This is invalid because if the process became suspended it could not enter any DEBUG commands to resume execution.
System Action:
The DEBUG START command is rejected.
User Action:
None.
Reason:
A DEBUG STOP command has been entered to stop all debugs owned by the command issuer. The command has been successfully processed.
System Action:
Debug control has been removed from all NCL processes which were under debug control from the command issuer's environment.
User Action:
None.
Reason:
A DEBUG START command has been entered with the REGION operand and no USER operand and without the KEEP=YES operand. To prevent the debug session maintaining control over NCL in the region for an excessive period of time and to increase security, the USER operand must be included on the DEBUG START command.
System Action:
The command is rejected.
User Action:
Specify a userid on the USER operand of the DEBUG START command.
Reason:
A DEBUG START command has been entered with the USER operand and no REGION operand and without the KEEP=YES operand. To identify which region is to be debugged the REGION operand must be included on the DEBUG START command.
System Action:
The command is rejected.
User Action:
Specify a region name on the REGION operand of the DEBUG START command.
Reason:
This message is sent to the SOLVE activity log when the environment (eg. OCS, dependent environment) which has an active debug session or the procedure terminates.
System Action:
The debug session is terminated.
User Action:
None.
Reason:
A DEBUG START or DEBUG STOP command has been entered with the DEBUGID operand to reconnect to or terminate a suspended debug session. The command issuer is not authorized to issue the command to action another users debug session.
System Action:
None.
User Action:
None.
Reason:
A DEBUG STOP TYPE=SUSPEND command has been issued to suspend a debug session and has completed successfully. A unique number, the 'DEBUGID', has been assigned to the suspended debug session. This number must be included on any DEBUG START or DEBUG STOP command which are to action the suspended debug session.
System Action:
The debug session has been suspended.
User Action:
None.
Reason:
A DEBUG STOP command was issued, and no previous DEBUG START command had been issued. No debug environment (established by a DEBUG START command) exists for the STOP command to terminate.
System Action:
None.
User Action:
None.
Reason:
This message is issued to the owner of a restarted debug session to document a process as being under debug control. This occurs when the DEBUG START command has been issued and the DEBUGID operand was specified. The message is issued for every NCL process that is under the previously suspended debug sessions control at the time the DEBUG START command is processed.
The NCL process remains under debug control until a DEBUG STOP command is issued, or the NCL process no longer satisfies the criteria specified on the DEBUG START command, or the NCL process terminates.
System Action:
None.
User Action:
The owner of the debug session may now issue DEBUG commands to debug the NCL process.
Reason:
A DEBUG STOP ID=nnnnnn TYPE=SUSPEND command has been issued to suspend the debug of a particular NCL process and has completed successfully. A unique number, the 'DEBUGID', has been assigned to the suspended debug session. This number must be included on any DEBUG START or DEBUG STOP command which are to action the suspended debug session. The NCL ID of the process that was targeted is nnnnnn.
System Action:
The debug for the NCL process has been suspended.
User Action:
None.
Reason:
A DEBUG BREAKPOINT command has been omitted but the breakpoint type cannot be determined. One of the breakpoint type operands (STMT, ARGS, VARS, VERB, EXEC) must be entered.
System Action:
The command is rejected.
User Action:
Enter one of the breakpoint operands required to identify the breakpoint type.
Reason:
A DEBUG BREAKPOINT command has been entered to set a variable breakpoint but the variable name specified is invalid.
System Action:
The command is rejected.
User Action:
Change the name of the variable and retry.
Reason:
A DEBUG BREAKPOINT command has been entered to set a variable breakpoint but the variable is not one which can support a breakpoint (e.g. system variable, global variable).
System Action:
The command is rejected.
User Action:
Change the name of the variable and retry.
Reason:
A DEBUG BREAKPOINT command has been entered which specified a generic variable prefix. The length of the prefix plus the length of the numeric suffix determined by the specified or default range produces a variable name which is longer than the maximum allowed.
System Action:
The command is rejected.
User Action:
Correct the prefix or range.
Reason:
A DEBUG BREAKPOINT command has been entered which specifies a generic variable prefix of ARGS or VARS=*. The specified or default range starts at 0 which produces a variable name of 0, which is invalid.
System Action:
The command is rejected.
User Action:
Correct the prefix or range.
Reason:
A DEBUG HOLD command has been issued which specified an NCL process which is already in a suspended state due to DEBUG HOLD command, DEBUG STEP command which stepped the procedure and it has reached the step statement limit, profile NEWHOLD=YES setting or a breakpoint being hit.
System Action:
The command is rejected.
User Action:
None.
Reason:
A DEBUG RESUME command was entered which specified an NCL process which is not in a suspended state.
System Action:
The command is rejected.
User Action:
None.
Reason:
A DEBUG HOLD command has been entered to halt execution of an NCL process and has been successfully processed.
System Action:
Execution of the NCL process will be suspended when the next statement in the currently executing procedure is encountered.
User Action:
None.
Reason:
A DEBUG RESUME command has been entered to resume execution of an NCL process and has been successfully processed.
System Action:
Execution of the NCL process will be resume at the next statement.
User Action:
None.
Reason:
A DEBUG SET command has been entered to modify the debug profile for a debug session. This message confirms the success of the profile modification.
System Action:
None.
User Action:
None.
Reason:
A DEBUG STEP command has been entered to invoke statement level stepping or NCL process execution until the next procedure entry or exit, and the command has been successfully processed.
System Action:
Execution of the NCL process will be suspended after the specified number of statements have been executed or when the next procedure entry or procedure exit occurs.
User Action:
None.
Reason:
This message is the heading message for the display of a debug profile. A DEBUG SET command that is entered with no operands specified is interpreted as a request to display the current debug profile. When the debug profile is displayed the first message issued is a heading and subsequent messages describe each individual profile option.
System Action:
None.
User Action:
None.
Reason:
This message is issued as a result of a DEBUG SET command. It indicates the current setting for the NEWHOLD debug profile option. The valid values are YES or NO. If NEWHOLD=YES is set then all NCL processes which come under debug control will be suspended immediately. If NEWHOLD=NO is indicated then 'bbb' will be 'NOT' to indicate that NCL processes will not be suspended when they come under debug control.
System Action:
None.
User Action:
None.
Reason:
This message is issued as a result of a DEBUG SET command. It indicates the current setting for the LOG debug profile option. The valid values are YES or NO. If LOG=YES is set then messages issued by debug will also be sent to the activity log. If LOG=NO is indicated then 'bbb' will be 'NOT' to indicate that debug messages will not be logged.
System Action:
None.
User Action:
None.
Reason:
This message is issued as a result of a DEBUG SET command. It indicates the current setting for the NCLTRACE debug profile option. The valid values are YES or NO. If NCLTRACE=YES is set then NCL trace messages issued by any process under the control of this debug session will be sent to the debugger. The trace messages will be issued if the NCL procedure has either CONTROL TRACE, CONTROL TRACELAB or CONTROL TRACEALL set. Alternatively the NCLTRACE command can be issued to set the tracing on for a particular process. If NCLTRACE=NO is indicated then 'bbb' will be 'NOT' to indicate that NCL trace messages will not be sent to the debugger.
System Action:
None.
User Action:
None.
Reason:
This message is issued as a result of a DEBUG SET command with no operands specified. It indicates the end of the debug profile display.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display which is produced when a DEBUG SET command is entered with no other operands. This display shows the current profile settings for the debug session. This message shows the setting of the CALLTRC option (YES or NO).
System Action:
None.
User Action:
None.
Reason:
A DEBUG CALLTRC command has been entered to change the 'call trace' status of an NCL process. This message confirms the change in status (ccc = ON or OFF).
System Action:
None.
User Action:
None.
Reason:
This message is the title line for the DEBUG TRACE display. The DEBUG TRACE display shows the procedure calls and subroutine calls which resulted in execution of the NCL process reaching its current state.
Refer to message N2A505 for a description of the display.
System Action:
The DEBUG TRACE display will follow this message.
User Action:
None.
Reason:
This message is part of the DEBUG TRACE display. The message shows information about the NCL process that is shown in the display.
Is the unique NCL ID of the NCL process.
Is the name of the base procedure in the NCL process.
Is the window in which the NCL process is executing (1 or 2).
Identifies the type of NCL process (for example, MSGPROC).
Is the initiator of the NCL process. This value is a user ID or the NCL ID of the process that started this one.
Is the user ID of the user whose region contains the executing NCL process.
Indicates if the process is ACTIVE or if the process has been SUSPENDED due to user command or a breakpoint being hit.
System Action:
None.
User Action:
None.
Reason:
This message is the title line for the call trace display of an NCL process and is part of the DEBUG TRACE display. This display shows all NCL procedure calls and subroutine calls which were made for the NCL process to reach its current state.
System Action:
None.
User Action:
None.
Reason:
This message is the detail display for the call trace display which is part of the DEBUG TRACE display. This display shows all NCL procedure calls and subroutine calls which were made for the NCL process to reach its current state. The field meanings are as follows:
procname - the name of the NCL procedure
ddname - the ddname of the library from where the NCL procedure was loaded from
s - the status of the loaded NCL procedure. The following values are possible:
A - AUTOSHR, C - CMDREPL, L - PRELOADED, N - NCLTEST, O - LOADING, P - PRIVATE, R - RETAINED, U - P-UNLOAD
ll - the nesting level of the procedure
mm - the subroutine call level within the procedure
line no - the line number from which the EXEC/FSPROC or &GOSUB was executed
statement - the first 256 bytes of the statement
System Action:
None.
User Action:
None.
Reason:
This message is the detail display for the DEBUG SOURCE display. It shows the line number containing the source, and the first 256 bytes of the statement on that line. the '*' indicator is present on the current statement if it is displayed.
System Action:
None.
User Action:
None.
Reason:
This message is issued when a DEBUG SOURCE command is issued and the statement number entered on the STMT= operand is greater than the statement number of the last line in the procedure. If the statement number does not exist but would be before the last line in the procedure the display starts at the next line.
System Action:
The command is rejected.
User Action:
Correct the statement number and retry.
Reason:
This message is the summary line for the DEBUG SOURCE display and shows how many lines of source were displayed and which procedure and NCL process they came from.
System Action:
None.
User Action:
None.
Reason:
This message is issued when a DEBUG SOURCE command is issued without the STMT= operand (which indicates the display is to start at the current statement) and the procedure has no current statement.
System Action:
The command is rejected.
User Action:
This indicates that the procedure has completed execution. Specify the STMT= operand on the DEBUG SOURCE command to nominate the statement which the display should start at.
Reason:
A DEBUG MODIFY command has been entered to modify the contents of one or more variables but the data supplied contains invalid hex characters or is not an even number of characters.
System Action:
The command is rejected.
User Action:
Correct the data supplied.
Reason:
A DEBUG MODIFY command has been entered to modify the contents of one or more variables but the data supplied exceeds the maximum allowable amount of data which can be assigned to a variable.
System Action:
The command is rejected.
User Action:
Correct the data supplied.
Reason:
A DEBUG MODIFY command has been entered to modify the contents of one or more variables but one or more of the variables specified are currently in use by a verb which will update the variable when it completes (eg. INTREAD, MSGREAD). When the verb completes any data assigned to the variable would be destroyed.
System Action:
The command is rejected.
User Action:
Modify the variables after the current verb completes.
Reason:
A DEBUG MODIFY command has been entered to update MDO contents but the data does not adhere to the format defined for the specified MDO structure.
System Action:
The command is rejected.
User Action:
Correct the data format and retry.
Reason:
A DEBUG DISPLAY or DEBUG MODIFY command has been entered with a generic variable prefix. The length of the prefix plus the length of the numeric suffix determined by the specified or default range produces a variable name which is longer than the maximum allowed.
System Action:
The command is rejected.
User Action:
Correct the prefix or range.
Reason:
A DEBUG DISPLAY or DEBUG MODIFY command has been entered with a generic variable prefix of ARGS or VARS=*. The specified or default range starts at 0 which produces a variable name of 0, which is invalid.
System Action:
The command is rejected.
User Action:
Correct the prefix or range.
Reason:
This is the title line for the display produced by the DEBUG DISPLAY command. The procedure name and NCLID of the NCL procedure are shown.
System Action:
None.
User Action:
None.
Reason:
A DEBUG MODIFY command has been entered and the variables or MDO specified on the command have been successfully updated.
System Action:
None.
User Action:
None.
Reason:
A DEBUG DISPLAY command has been entered to display the contents of an MDO and the MDO exists but the length of the data contained within the MDO is zero.
System Action:
None.
User Action:
None. The DEBUG MODIFY command may be used to modify the MDO.
Reason:
This message is the title line for the character and hex dump format display produced by the DEBUG DISPLAY command when a single variable name or MDO name is entered. The display shows the contents of the variable or MDO in hexadecimal and character format. Refer to the description of message N2A611 for more information.
System Action:
None.
User Action:
None.
Reason:
This message is produced by the DEBUG DISPLAY command when the FORMAT=DUMP operand is specified. The message contains a hex and character dump format display of the data in the variable. The meanings of the fields are as follows:
+ooo - shows the offset into the variable at which the data starts
xxxxxxxx - the hexadecimal format of the data
cccccccc - the character format of the data
System Action:
None.
User Action:
None.
Reason:
A DEBUG DISPLAY command has been entered to display the contents of an MDO but the MDO does not exist.
System Action:
The command is rejected.
User Action:
Correct the MDO name and retry. This message could indicate that the map in which the MDO name belongs has not been loaded and assigned correctly.
Reason:
A DEBUG DISPLAY command has been entered to display the names (and maybe contents) of an MDO. This message displays the name of the MAP which has been used to map the MDO structure.
System Action:
None.
User Action:
None.
Reason:
A DEBUG DISPLAY or DEBUG MODIFY command has been entered which specified an invalid MDO name on the MDO= or MDONAME= operand.
System Action:
The command is rejected.
User Action:
Correct the MDO name and retry.
Reason:
A DEBUG DISPLAY command has been entered which specified a variable indexed MDO name and a range which specified zero as the starting value in the range (eg MDO=AAAA.BBBB{*} RANGE=(0,4)). A value of zero is invalid as the start of a range.
System Action:
The command is rejected.
User Action:
Correct the range start value on the RANGE= operand and retry.
Reason:
A DEBUG MODIFY command has been entered to modify the contents of an MDO but the command has been rejected. 'reason' indicates why. The modification of MDOs is valid only whilst the procedure is suspended by DEBUG and not after the procedure has terminated (abnormally or due to normal end of procedure condition).
System Action:
The command is rejected.
User Action:
None.
Reason:
SOLVE was unable to obtain storage for a DEBUG DISPLAY command.
System Action:
The display command is ignored.
User Action:
Contact your systems administrator and examine the reason for the storage shortage.
Reason:
This message is part of the DEBUG DISPLAY MDO=/MDONAMES= display and shows the name of an MDO which satisfied the criteria specified on the DEBUG DISPLAY command. In the case of a DEBUG DISPLAY MDO= command, this message is followed by the data contents of the named MDO.
System Action:
None.
User Action:
None.
Reason:
A DEBUG DISPLAY command has been entered with the FMT=MDO option specified, but the display requested is not a single MDO stem display.
System Action:
The command is rejected.
User Action:
The FMT=MDO option is only valid for DEBUG DISPLAY MDO=aaaaaa where aaaaaa is a single (ie. not compound such as aa.bb.cc) MDO stem name. Re-enter the command with a single MDO name.
Reason:
A DEBUG DISPLAY or DEBUG MODIFY command specified an invalid variable or MDO name for an NCL procedure.
System Action:
The command is rejected.
User Action:
Correct the variable name and retry. To display global OML variables, debug an OML procedure.
Reason:
A DEBUG DISPLAY or DEBUG MODIFY command specified an invalid variable name on the VARS= operand.
System Action:
The command is rejected.
User Action:
Correct the variable name and retry.
Reason:
A DEBUG BREAKPOINT command has been entered but the operands conflict with (are the same as or specify variables in common with) another breakpoint (breakpoint number 'nnnn'). Each breakpoint created within a debug session must be unique.
System Action:
The command is rejected.
User Action:
None.
Reason:
A DEBUG BREAKPOINT command has been entered with the VERB= operand but the verb name entered is not a valid verb.
System Action:
The command is rejected.
User Action:
Correct the verb name and retry. This may mean that the verb specified does not exist because the verb belongs to a feature which is not licensed on the system.
Reason:
A DEBUG CLEAR command has been entered to clear a breakpoint but no breakpoint exists with the specified breakpoint number.
System Action:
The command is rejected.
User Action:
Obtain the correct breakpoint number and retry. The DEBUG LIST BREAKPOINTS command can be used to list all breakpoints within a debug session.
Reason:
A DEBUG CLEAR command has been entered to clear a breakpoint and has been processed successfully.
System Action:
The breakpoint is cleared.
User Action:
None.
Reason:
A DEBUG BREAKPOINT command has been entered to create a breakpoint and has been processed successfully. The breakpoint has been assigned a number 'nnnn' which is unique within a debug session called the breakpoint number. The breakpoint number must be entered on the DEBUG CLEAR command to clear the breakpoint.
System Action:
The breakpoint is set.
User Action:
None.
Reason:
A DEBUG CLEAR command has been entered to clear breakpoints within a debug session. This message confirms successful processing of the command and shows how many breakpoints were reset.
System Action:
The specified number of breakpoints have been cleared.
User Action:
None.
Reason:
A DEBUG BREAKPOINT command has been entered to create a breakpoint but a storage shortage has prevented successful processing of the command.
System Action:
The breakpoint has not been set.
User Action:
Investigate the cause of the storage shortage.
Reason:
This message is the title line of the DEBUG LIST BREAKPOINTS display. This display lists all breakpoints within a debug session.
Refer to message N2A709 for a description of the display.
System Action:
None.
User Action:
None.
Reason:
This message is the detail line of the DEBUG LIST BREAKPOINTS display. This display lists all breakpoints within a debug session. The meanings of the fields are as follows:
nnnnnn - the unique breakpoint number of the breakpoint
procname - the name of the procedure to which the breakpoint applies
nclid - the nclid of the process to which the breakpoint applies
type - the type of breakpoint
STMT - a statement breakpoint
VAR - a variable breakpoint
VERB - an NCL verb breakpoint
EXEC - an ENTRY or EXIT breakpoint
description - shows the criteria which were specified on the DEBUG BREAKPOINT command (statement number, variables names or verb name)
System Action:
None.
User Action:
None.
Reason:
This message is the summary line of the DEBUG LIST BREAKPOINTS display. It shows how many breakpoints were displayed ('nnnn') and how many exist within the debug session ('mmmm').
System Action:
None.
User Action:
None.
Reason:
A DEBUG LIST BREAKPOINTS command has been entered but no breakpoints exist within the debug session.
System Action:
None.
User Action:
None.
Reason:
A DEBUG BREAKPOINT command has been entered to set a breakpoint. The breakpoint specification is valid in OML but not in NCL, so this warning message is sent to notify that the breakpoint will only be applied to OML procedures, not NCL. For example, VARS=A.B.C is a valid breakpoint specification in OML, but not NCL (NCL does not support compound vars).
System Action:
The breakpoint is set as requested but will only be applied to OML procedures.
User Action:
None.
Reason:
A DEBUG BREAKPOINT command has been entered to create a breakpoint but the data supplied for the conditional breakpoint which was specified in hexadecimal format contains invalid hexadecimal characters or is not of even length.
System Action:
The command is rejected.
User Action:
Correct the data and retry.
Reason:
A DEBUG BREAKPOINT command has been entered to create a breakpoint but the length of the data supplied for the conditional breakpoint exceeds the maximum allowed for an NCL variable.
System Action:
The command is rejected.
User Action:
Correct the data and retry.
Reason:
A &DEBUG BREAKPOINT command has been entered to set a breakpoint. The verb named in the breakpoint is a known verb but is not suitable for a breakpoint because it is not executable.
System Action:
The command is rejected.
User Action:
None.
Reason:
A &DEBUG BREAKPOINT command has been entered to set a breakpoint. The breakpoint specification is valid in NCL but not in OML, so this warning message is sent to notify that the breakpoint will only be applied to NCL procedures, not OML. For example, VERB=NDBADD is a valid breakpoint specification in NCL, but not OML (OML does not have an NDBADD verb).
System Action:
The breakpoint is set as requested but will only be applied to NCL procedures.
User Action:
None.
Reason:
A statement type breakpoint which was set on procedure 'name' at statement 'mmmmmmmm' has been hit. The next statement to be executed will be the specified statement.
System Action:
Execution of the NCL process has been suspended.
User Action:
Other DEBUG commands may be used to obtain information about the NCL process. The DEBUG STEP and DEBUG RESUME commands may be used to allow execution of the NCL process to continue.
Reason:
A variable type breakpoint which was set on variable 'varname' in procedure 'name' has been hit. The variable has been updated. If the breakpoint was conditional, the variable now contains the value specified on the DEBUG BREAKPOINT command.
System Action:
Execution of the NCL process has been suspended.
User Action:
Other DEBUG commands may be used to obtain information about the NCL process. The DEBUG STEP and DEBUG RESUME commands may be used to allow execution of the NCL process to continue.
Reason:
A variable type breakpoint which was set on verb 'verbname' in procedure 'name' has been hit. The next statement to be executed contains the specified verb.
System Action:
Execution of the NCL process has been suspended.
User Action:
Other DEBUG commands may be used to obtain information about the NCL process. The DEBUG STEP and DEBUG RESUME commands may be used to allow execution of the NCL process to continue.
Reason:
A procedure ENTRY breakpoint has been set to cause suspension of the specified NCL procedure. The procedure has begun execution and has been suspended due to the breakpoint setting.
System Action:
Execution of the NCL process has been suspended.
User Action:
Other DEBUG commands may be used to obtain information about the NCL process. The DEBUG STEP and DEBUG RESUME commands may be used to allow execution of the NCL process to continue.
Reason:
A procedure EXIT breakpoint has been set to cause suspension of the specified NCL procedure. The procedure has completed execution and has been suspended due to the breakpoint setting.
System Action:
Execution of the NCL process has been suspended.
User Action:
Other DEBUG commands may be used to obtain information about the NCL process. The DEBUG STEP and DEBUG RESUME commands may be used to allow execution of the NCL process to continue.
Reason:
A breakpoint has been set on the statement number and procedure or NCLID specified in this message but when an attempt was made to apply the breakpoint the specified statement number could not be found in the procedure 'procname'.
System Action:
The breakpoint is not applied.
User Action:
Correct the statement number or procedure name/nclid on the breakpoint definition and retry.
Reason:
A statement type breakpoint has been set on the procedure or NCL ID specified in this message. When an attempt was made to apply the breakpoint, it was found that the procedure was not a private copy. The statement type breakpoint can only be applied to a procedure that was loaded privately or under the NCLTEST option. The breakpoint remains valid for future occurrences of the procedure.
System Action:
The breakpoint is not applied.
User Action:
Determine why the procedure was not privately loaded. If the breakpoint is set before the procedure begins execution, the region loads the procedure automatically privately.
Reason:
A SHOW DEBUG command has been entered but there are no active debug sessions in the system.
System Action:
None.
User Action:
None.
Reason:
This message is the title line for the SHOW DEBUG display. The SHOW DEBUG command is used to list the debug sessions active in the system and the scope over which the debug session has control.
See the description of message N2AA03 for the meanings of the column headings.
System Action:
None.
User Action:
None.
Reason:
This message is the detail line for the SHOW DEBUG display. The SHOW DEBUG command is used to display the active debug sessions and the scope over which each session has control. The information in each field is as follows:
Shows the user ID of the user who owns the debug session.
Shows the KEEP option on the DEBUG START command.
Indicates the status of the debug session:
Shows the NCLID specified on the DEBUG START command.
Shows the USERID specified on the DEBUG START command.
Shows the REGION specified on the DEBUG START command. This value is a region name or a link name.
Shows the WINDOW specified on the DEBUG START command.
Shows the PROCEDURE specified on the DEBUG START command.
Is the identification number that is assigned to the suspended debug session when the DEBUG STOP TYPE=SUSPEND command is issued to suspend a debug session.
System Action:
None.
User Action:
None.
Reason:
This message terminates the SHOW DEBUG display. It shows the total number of debug sessions active in the system (nnnn) and the number displayed (mmmm).
System Action:
None
User Action:
None
Reason:
This message is the title line for the NCL display of the SHOW DEBUG display. If the SHOW DEBUG command requests a specific NCLID a display of the NCL process is appended to the SHOW DEBUG DISPLAY. If the NCL=YES operand is entered on SHOW DEBUG a detailed display is produced of all NCL within the debug sessions displayed. See the description of message N2AA06 for details about this display.
System Action:
None
User Action:
None
Reason:
This message forms the detail display for one NCL process of the NCL display in the SHOW DEBUG display. The NCL display is produced when a specific NCLID is entered on the SHOW DEBUG command or when the NCL=YES operand is entered on the SHOW DEBUG command. The meanings of the fields are as follows:
nclid - the NCLID of the NCL process
baseproc - the name of the base procedure in the NCL process
current - the name of the procedure which is the currently executing nesting level
lv - the number of active nesting levels in the process
w - the window in which the ncl process is executing (1 or 2)
type - the type of ncl process eg. MSGPROC
init - the initiator of the NCL process. This may be a userid or the NCLID of the process which started this one
owner - the userid of the user whose region contains the executing NCL process
status - shows if the process is currently ACTIVE or has been SUSPENDED due to user command or a breakpoint being hit
System Action:
None
User Action:
None
Reason:
If the SHOW DEBUG command is entered with a specific NCLID or with the NCL=YES operand, a detailed display of each NCL process under the control of the debug scopes displayed is produced. This message is a summary of the NCL display, stating how many NCL processes were displayed.
System Action:
None
User Action:
None
Reason:
This message is issued to the owner of a debug session when an NCL process is placed under debug control. This is either when a DEBUG START command is issued or subsequently when a procedure starts which satisfies the scope specified on the DEBUG START command.
The NCL process remains under debug control until a DEBUG STOP command is issued, or the NCL process no longer satisfies the criteria specified on the DEBUG START command, or the NCL process terminates.
System Action:
The NCL process is placed under control of the NCL debug facility.
User Action:
The owner of the debug session may now issue DEBUG commands to debug the NCL process.
Reason:
This message is issued when the NCL debug facility relinquishes debug control over an NCL process. This could occur because of a DEBUG STOP command being issued, or because the NCL process no longer satisfies the criteria on the DEBUG START command, or because the NCL procedure has terminated.
System Action:
Debug control over the NCL process is removed.
User Action:
No more DEBUG commands can be applied to this process.
Reason:
An NCL process has matched the criteria specified on a DEBUG START command but has not been placed under debug control for one of the following reasons:
- the process is a LOCKPROC system process.
- the process is a MSGPROC and the DEBUG START command was entered from the environment in which the MSGPROC is executing. This is invalid because if the process became suspended the debugging user would no longer be able to see command responses.
- the DEBUG START command was entered from within the dependent (&INTCMD) environment of the nominated process. This is invalid because if the process became suspended it could not enter any DEBUG commands to resume execution.
- The NCL process is executing as a command replacement (see SYSPARMS CMDREPL=xxxx), and debug has been refused for security reasons.
System Action:
The NCL process is not placed under debug control.
User Action:
None.
Reason:
This message is sent to the owner of a debug session when the scope of a DEBUG START was a specific NCL process ID and the process has ended.
System Action:
The debug scope is terminated.
User Action:
None.
Reason:
This message is sent to the owner of a debug session which has a debug scope which targets a specific environment (eg. OCS or dependent environment) and the environment terminates.
System Action:
The debug scope is terminated.
User Action:
None.
Reason:
This message is sent to the owner of a debug session when the scope of a DEBUG START was a specific window within a region and the window which was specified has terminated.
System Action:
The debug scope is terminated.
User Action:
None. The KEEP=YES operand on DEBUG START can be used to prevent the debug scope from terminating when the window terminates.
Reason:
This message is sent to the owner of a debug session when the scope of a DEBUG START was a specific region and the region has terminated.
System Action:
The debug scope is terminated.
User Action:
None. The KEEP=YES operand on the DEBUG START command can be used to prevent the termination of the debug scope when the region terminates.
Reason:
This message is sent to the owner of a debug session when the scope of a DEBUG START was a specific user in a specific region and the user has signed off.
System Action:
The debug scope is terminated.
User Action:
None. The KEEP=YES operand on the DEBUG START command can be used to prevent termination of the debug scope when the user signs off.
Reason:
This message is sent to the owner of a debug session when the scope of a DEBUG START was a specific user and the user has just signed off. The user is no longer signed on in any region so the debug scope has been terminated.
System Action:
The debug scope is terminated.
User Action:
None. The KEEP=YES operand on the DEBUG START command can be used to prevent termination of the debug scope when the last occurrence of the userid signs off.
Reason:
A DEBUG command has been entered which should have targeted a procedure which is currently being debugged by the environment issuing the DEBUG command. The environment does not have any active debug scopes.
System Action:
The DEBUG command is rejected.
User Action:
None. The DEBUG START command can be used to place procedures under debug control.
Reason:
A DEBUG command has been entered which specified an NCLID but there is no NCL procedure active in the system with this NCLID.
System Action:
The DEBUG command is rejected.
User Action:
Obtain the correct NCLID and retry the command.
Reason:
A DEBUG command has been entered which specified an NCLID and the specified NCL process is active in the system but is not currently being debugged by any user.
System Action:
The DEBUG command is rejected.
User Action:
The DEBUG START command can be used to place the process under debug control.
Reason:
A DEBUG command has been entered which specified an NCLID and the specified NCL process is active in the system and is being debugged but the debug session which is debugging it is currently suspended.
System Action:
The DEBUG command is rejected.
User Action:
The SHOW DEBUG command can be used to obtain the 'debugid' of the suspended debug session. A DEBUG START DEBUGID=nnnn command can be used to obtain debug control over the suspended session.
Reason:
A DEBUG command has been entered which specified an NCLID and the specified NCL process is active in the system but is being debugged by another user.
System Action:
The DEBUG command is rejected.
User Action:
The SHOW DEBUG command can be used to find out which user is debugging the process. Only the environment which issued the DEBUG START command to obtain debug control over the NCL process may issue this DEBUG command to control the process.
Reason:
A DEBUG command has been entered which specified an NCLID and the specified NCL process is active in the system and is being debugged by this user but the environment from which the command was issued is not the environment which has debug control over the process.
System Action:
The DEBUG command is rejected.
User Action:
None. Only the environment which issued the DEBUG START command to obtain debug control over the process may issue this DEBUG command to control the debugged NCL process.
Reason:
A DEBUG command has been entered which did not specify an NCLID or procedure name and no default NCLID or NCL process exists for the debuggers environment. Therefore the NCL process to which the command is to be applied cannot be determined.
System Action:
The DEBUG command is rejected.
User Action:
Enter the NCLID or PROCEDURE operand on the DEBUG command to identify which NCL process is to be targeted by the command.
Reason:
A DEBUG command has been entered which requires the target NCL process to have an active nesting level. The command has been rejected because the NCL process is currently dormant (ie. has no NCL procedure executing).
System Action:
The command is rejected.
User Action:
The command entered requires an NCL procedure to be executing at the time the command is processed (for example, DEBUG DISPLAY requires some NCL variables or MDOs to be associated with the NCL process, but if the NCL process is dormant then no variables or MDOs exist). Re-enter the command when the NCL process becomes active.
Reason:
A DEBUG command has been entered which specified the NCLID and PROCEDURE operands but the specified procedure does not exist at the required levels in the specified NCL process. Most commands require the procedure to exist only at base or current level, DEBUG DISPLAY and DEBUG MODIFY allow the procedure to exist at any level.
System Action:
The DEBUG command is rejected.
User Action:
Correct the NCLID or PROCEDURE operand and retry the command.
Reason:
A DEBUG command has been entered which specified the PROCEDURE operand but the specified procedure does not exist at the required nesting level any NCL process under debug control from that environment. Most commands require the procedure to exist only at base or current level, DEBUG DISPLAY and DEBUG MODIFY allow the procedure to exist at any level.
System Action:
The DEBUG command is rejected.
User Action:
Correct the PROCEDURE operand and retry the command.
Reason:
A security sub-system exit has passed an invalid structured field to SOLVE or an invalid structured field was passed by an &SECCALL verb.
System Action:
This message is written to the SOLVE activity log. The security request proceeds however, the particular structured field in error is ignored.
User Action:
Identify the structured field in error and correct the error, either by correcting the NCL or the security exit.
Reason:
A security sub-system exit has passed an invalid structured field to SOLVE or an invalid structured field was passed by an &SECCALL verb.
System Action:
This message is written to the SOLVE activity log. The security request proceeds however, the particular structured field in error is ignored.
User Action:
Identify the structured field in error and correct the error, either by correcting the NCL or the security exit.
Reason:
A security sub-system exit has passed an invalid structured field to SOLVE or an invalid structured field was passed by an &SECCALL verb.
System Action:
This message is written to the SOLVE activity log. The security request proceeds however, the particular structured field in error is ignored.
User Action:
Identify the structured field in error and correct the error, either by correcting the NCL or the security exit.
Reason:
A security sub-system exit has passed an invalid structured field to SOLVE or an invalid structured field was passed by an &SECCALL verb.
System Action:
This message is written to the SOLVE activity log. The security request proceeds however, the particular structured field in error is ignored.
User Action:
Identify the structured field in error and correct the error, either by correcting the NCL or the security exit.
Reason:
A security sub-system exit has passed an invalid structured field to SOLVE or an invalid structured field was passed by an &SECCALL verb.
System Action:
This message is written to the SOLVE activity log. The security request proceeds however, the particular structured field in error is ignored.
User Action:
Identify the structured field in error and correct the error, either by correcting the NCL or the security exit.
Reason:
This message is issued after a DCOM CONNECT or a DCOM DISCONNECT command has been issued to indicate a change to the connection status of the Datacom interface. P1 may be CONNECTED or DISCONNECTED.
System Action:
None.
User Action:
Issue the DCOM CONNECT or DCOM DISCONNECT command if the updated status is not desired.
Reason:
This message is issued after a DCOM CONNECT or a DCOM DISCONNECT command has failed. P1 is either CONNECT(OPEN) or DISCONNECT(CLOSE).
System Action:
None.
User Action:
Consult the CA Datacom/DB Message Reference Guide for an explanation of the return code and internal return code.
Reason:
This message is issued in response to a SHOW DCOM command to display the status of the OML/DATACOM interface. P1 may be "UNAVAILABLE", "SHUTDOWN", "CONNECTED", "CONNECTING", "DISCONNECTED", or "DISCONNECTING".
System Action:
None.
User Action:
None - this is informational only.
Reason:
This message is issued in response to a SHOW DCOM=USERS command to display the list of users currently connected to DATACOM via the OML/DATACOM interface. This is a heading which will be followed by N2D803 detail lines.
System Action:
None.
User Action:
None - this is informational only.
Reason:
This message is issued in response to a SHOW DCOM=USERS command to display the list of users currently connected to DATACOM via the OML/DATACOM interface. P1 is the NCLID and P2 is the owing user ID of the process.
System Action:
None.
User Action:
None - this is informational only.
Reason:
This message is issued in response to a DCOM CONNECT or DCOM DISCONNECT command to indicate that the desired connection state is already in effect. P1 may be either CONNECTED or DISCONNECTED.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a DCOM DISCONNECT command. The message acknowledges that a DISCONNECT of the OML/DATACOM interface is to be performed and displays how many users are currently connected. The DISCONNECT will not complete until all OML/DATACOM users have terminated their connection.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a DCOM CONNECT or DCOM DISCONNECT command to indicate that a previous DCOM command is being acted upon. P1 will be CONNECTING if the prior command is DCOM DISCONNECT, else it will be DISCONNECTING.
System Action:
None.
User Action:
None.
Reason:
This message is issued to indicate a DCOM CONNECT or DCOM DISCONNECT command has been accepted for processing.
System Action:
None.
User Action:
None.
Reason:
The UNIX server failed to initialize. The process of spawning an address space can fail any of the following three phases:
The return code consists of 3 bytes of hexadecimal digits: cause, qualifier1 (Q1), and qualifier2 (Q2). The following causes are possible:
00 BLDL failure
Q1 - BLDL macro R15 value Q2 - BLDL macro R0 value
01 BLDL result
Q1 - 00 Server in private library
01 Server in linklist
02 SWAREQ failure
Q1 - SWAREQ macro R15 value Q2 - SWAREQ macro R0 value
03 ASCRE failure
Q1 - ASCRE macro R15 value Q2 - ASCRE macro R0 value
04 Not authorized 05 A/S terminated 06 Server system ABEND 07 Server user ABEND 10 Init 1 ASEXT failure
Q1 - ASEXT macro R15 value Q2 - ASEXT macro R0 value
11 Init 1 IEANTCR failure
Q1 - IEANTCR macro R15 value
20 Init 2 IEANTRT failure
Q1 - IEANTRT macro R15 value
21 Init 2 parms
Q1 - 00 Missing slash
01 Missing DSN
02 Missing member name
22 Init 2 DYNALLOC failure
Q1 - DYNALLOC R15 value Q2 - DYNALLOC R0 value
23 Init 2 OPEN failure
Q1 - OPEN macro R15 value Q2 - OPEN macro R0 value
24 Init 2 ATTACH failure
Q1 - ATTACH macro R15 value Q2 - ATTACH macro R0 value
25 Init 2 RACROUTE VERIFY failure
Q1 - RACROUTE VERIFY R15 value Q2 - RACROUTE VERIFY R0 value
26 Init 2 RACROUTE AUTH failure
Q1 - RACROUTE AUTH R15 value Q2 - RACROUTE AUTH R0 value
System Action:
In all cases, server initialization is retried in 30 seconds, during which time any UNIX verb calls are delayed.
User Action:
For causes 04, 25, or 26, review the security settings for the address space. For all other causes, contact CA Support.
Reason:
The UNIX server address space terminated.
System Action:
Server initialization is retried in 30 seconds, during which time any UNIX verb calls are delayed.
User Action:
See the UNIX syslog for messages indicating a possible cause.
Reason:
The UNIX server has abended with the provided ABEND code and reason code. 1 is "S" for a system ABEND or "U" for a user ABEND.
System Action:
The UNIX server is restarted in 30 seconds.
User Action:
For a system ABEND, see the MVS system codes. For a user ABEND, contact CA Support.
Reason:
The UNIX server has terminated unexpectedly, pending restart.
System Action:
The UNIX server is restarted in 30 seconds.
User Action:
See preceding messages for actions.
Reason:
An attempt has been made to read the general broadcast from the VFS file but an error has occurred and the broadcast cannot be read.
System Action:
None.
User Action:
Determine the cause of the failure.
Reason:
This message shows the user ID that last modified the broadcast that is stored on the VFS file. The message appears as a result of the SHOW BRO command, or when you update the broadcast text of a primary menu or general broadcast.
Is the type of broadcast:
Is the last action on the broadcast:
Is the user ID of the person who set or reset the broadcast.
Is the time that the broadcast was set or reset in the format HH.MM.SS.
Is the date that the broadcast was set or reset in the format DD-MM-YYYY.
System Action:
If you entered the SHOW BRO command, the text of the new broadcast (if set) follows this message.
User Action:
None.
Reason:
This message shows each line of general broadcast text stored on the VFS file. It is issued as a result of the broadcast being set or reset or a SHOW BRO command.
System Action:
None.
User Action:
None.
Reason:
An error occurred when attempting to store a broadcast message in the VFS dataset.
System Action:
None.
User Action:
Retry. If the condition persists, check the status of the VFS dataset.
Reason:
A request was made to display the stored logo or primary menu broadcast, but no broadcast has been stored.
System Action:
None.
User Action:
None.
Reason:
An I/O error occurred while attempting to read broadcast information from the VFS dataset.
System Action:
The broadcast function is terminated.
User Action:
Retry. If the condition persists, refer the error to your systems administrator.
Reason:
The SHOW BRO command lists the contents of the general and primary menu broadcasts stored on the VFS file. This heading message precedes the primary menu broadcast text in the SH BRO display.
System Action:
None.
User Action:
None.
Reason:
The general broadcast or primary menu broadcast saved on the VFS file has been updated.
System Action:
None.
User Action:
None.
Reason:
The session with the LU1 device indicated in the message has been terminated following a CLSDST WAIT=YES command.
System Action:
None.
User Action:
None.
Reason:
The luname shown in the message was the target of a CLSDST WAIT=YES command, but the CLSDST has been ignored due to the subsequent arrival of more messages for the terminal.
System Action:
The CLSDST command is ignored.
User Action:
None.
Reason:
The processing of NCL procedures in a fullscreen mode may cause messages to be generated that cannot be displayed on the screen because it has been taken over for fullscreen displays. Such messages may originate from error conditions or as a result of commands issued within the procedure. When possible all such messages are listed in the order in which they were generated, on multiple screen pages if necessary. This message acts as a heading for that list.
System Action:
None.
User Action:
Review the messages displayed as appropriate. The messages may indicate a possible processing problem and need to be reported to your installations help desk facility.
Reason:
Input was received (eg: Clear key was pressed) when the window was executing an NCL procedure in fullscreen mode, but the procedure was not expecting input.
System Action:
The input is ignored and the keyboard unlocked.
User Action:
Wait for the procedure to display a panel and accept input. An authorized user may wish to swap to the other window and use a 'SHOW NCL=REGION' command to determine the reason for the delay in &PANEL output. If necessary 'FLUSH' the process or use 'CANCEL WINDOW'.
Reason:
SOLVE could not obtain storage to queue an event to an NCL procedure which is processing with an asynchronous panel. The procedure may be executing any NCL statement following the &PANEL statement.
System Action:
The procedure terminates.
User Action:
Contact your systems administrator.
Reason:
The INMC/EF option of System Support Services was selected but the load module required for this function could not be loaded.
System Action:
Processing is terminated.
User Action:
Contact your systems administrator.
Reason:
A LINK START=linkname command was requested for a link that has not been started before and has no link definition on the VFS database. The APPLID operand was not included on the command, and the APPLID has defaulted to the linkname.
System Action:
Further messages will follow regarding the status of the link.
User Action:
None.
Reason:
The APPLID operand must specify a resource not already in session with this system.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
A storage shortage prevented successful completion of the LINK START command.
System Action:
The command fails.
User Action:
Retry. Determine the cause of the storage shortage condition.
Reason:
A LINK START= command has completed successfully. The link will be activated automatically when the remote system is available.
System Action:
None.
User Action:
Wait for the remote system to become active.
Reason:
A LINK START=linkname command was requested for a link that has not been started before and no INMC/EF definition exists on VFS. The MSGID operand was not included within the command, and the MSGID has defaulted to the first four characters of the linkname.
System Action:
Link activation continues.
User Action:
None, unless the MSGID operand has been accidentally omitted.
Reason:
The APPLID specified cannot be the name of an APPL definition used by this region.
System Action:
None.
User Action:
Correct and retry.
Reason:
APPLID or MSGID operands specified on a LINK START= command are ignored if the link definition exists on VFS.
System Action:
Link activation continues.
User Action:
None.
Reason:
The INMC/EF definition for the specified link could not be retrieved from the VFS database due to an I/O error.
System Action:
The command fails.
User Action:
Contact your systems administrator.
Reason:
A LINK START= command was issued in a system configured for INMC/EF, but no record was found of the definition on the VFS database. The system will build a simple-mode link definition.
System Action:
None.
User Action:
None.
Reason:
A LINK START= command was issued to start an INMC link but the link type is invalid. Valid values are INMC, APPC and NVC. Note: TYPE=NVC is only valid if the region is configured with the NetView Connect option.
System Action:
None.
User Action:
Correct the TYPE= operand and retry. If you require connections to NetView regions, contact your Systems Administrator to reconfigure the region with the NetView Connect option (PROD=NVC).
Reason:
A LINK START command was entered and has been rejected because the name of the link matches the application name in use for a dynamic link.
System Action:
The command is rejected.
User Action:
Use a different link name, or change the identifier of the dynamic link.
Reason:
A link has been created for a remote application using the indicated DEFNAME entry.
P1 identifies the link.
P2 identifies the remote application.
P3 identifies the DEFNAME entry.
System Action:
Attributes from the P3 definition are used to complete the link details.
User Action:
Use /INMCDEF to verify that the link attributes used are correct. If necessary, modify the DEFNAME used on the LINK START command or modify the definition used.
Reason:
An INMC link was starting and the INMCEX01 exit was to be loaded, but the load failed. The link has been disabled.
System Action:
Link activation will not continue for security reasons.
User Action:
Refer this problem to your systems administrator for resolution. The nominated link module may not be available in SOLVE's load library.
Reason:
The BIND resulting from a LINK command to another region contains an RUSIZE value less than 256 (X'80') or greater than 65535 (X'FFFF').
luname is the name of the primary ACB that sent the BIND.
System Action:
The BIND is rejected with a sense code of 08210000.
User Action:
Verify the logmode of the region primary ACB. Take a VTAM buffer trace, and review the BIND. Ensure that the RUSIZES values are within limits.
Reason:
An OPN or CLS command was issued specifying the ACBNAME of a remote SOLVE system with which this system has a connection. Control of links to remote SOLVE systems is handled only by the LINK command.
System Action:
The command is rejected.
User Action:
Use the LINK command to control the link to the remote SOLVE system.
Reason:
The BIND resulting from a LINK command from another region contains an RUSIZE value less than 256 (X'80') or greater than 65535 (X'FFFF').
luname is the name of the primary ACB that sent the BIND.
System Action:
The BIND is rejected with a sense code of 08210000.
User Action:
Verify the logmode of the region primary ACB. Take a VTAM buffer trace, and review the BIND. Ensure that the RUSIZES values are within limits.
Reason:
A serious error has occurred on INMC link linkname , from which it cannot recover automatically. The error-type in the message will be either SNA Sense codes, or an explanatory message.
System Action:
The link is forced inactive, and put into 'failed' status.
User Action:
If the error-type consists of SNA sense information, the sense codes should be checked to see what type of network problem occurred. An error-type of 'INVALID DATA RECEIVED' on an NMPC link may mean there is a hardware problem on the PC. The link can be restarted using a 'LINK START=linkname' command. If this error recurs, contact your product support representative.
Reason:
The INMC link AAAAA has failed due to a lack of storage.
System Action:
The link is forced inactive and placed in 'failed' status.
User Action:
When the storage shortage is relieved, the link may be restarted by entering 'LINK START=linkname'.
Reason:
The link from this system (systemid) to the remote system known as linkname is inactive.
System Action:
If the link has become inactive as a result of an earlier LINK STOP=linkname command, the link will remain inactive until a subsequent LINK START=linkname command. Otherwise, the system will attempt to re-establish the link at regular intervals.
User Action:
Determine the cause of link deactivation if no LINK STOP=linkname was entered. Possible causes may be a failure of the network path between the two systems or the remote system may have terminated.
Reason:
Issued when the connection from this SOLVE system (systemid) to the remote SOLVE system (linkname) has been established.
System Action:
None.
User Action:
The Remote Operator Facility may now be used to route commands and enquiries to the remote system using the ROUTE command.
Reason:
Confirms successful processing of an earlier LINK RESET=linkname command issued to delete the definition of the remote SOLVE system linkname.
System Action:
None.
User Action:
A LINK START= command will have to be entered to redefine the remote system linkname before connection can be re-established.
Reason:
The system has stopped all further attempts to establish session number nn with the remote SOLVE system linkname , where the remote system was to be the secondary end of the session.
System Action:
No retries will be performed.
User Action:
This message is followed by message N35005 indicating the reason for the disabling of the session definition. If the fault indicated by N35005 is correctable, correct it, then reset and redefine the link.
Reason:
This message identifies the reason why the system issued message N35004. Possible reasons are `INVALID LOGMODE TABLE' or `PARALLEL SESSION REFUSED'.
System Action:
None.
User Action:
Report the failure to your system administrator.
If INVALID LOGMODE TABLE, correct the DLOGMOD operand specified on the APPL definition statement used by the remote system. If PARALLEL SESSION REFUSED then if the level of VTAM being used supports parallel sessions check the APPL definition statements of both systems to ensure that they include the PARSESS operand. If the level of VTAM being used does not support parallel sessions ignore this message; the system will operate satisfactorily with one session between the two systems.
Reason:
This message is issued to all Monitor status operators when a session request to a remote system fails for any reason. The message is issued only if the SYSPARMS LNKTRACE=YES command has been entered. The text bbbbbbbbbbbb describes the error which has occurred.
System Action:
None.
User Action:
This trace message may be of use to systems administrator if difficulty is experienced in establishing a connection between two systems.
Use the SYSPARMS LNKTRACE=NO command to reset the trace option that produces this message when the cause of the error has been established.
Reason:
If the SYSPARMS SESSMSG=YES option is in effect the system will report the loss or establishment of all sessions on INMC links. If INMC/EF is in use the session number specified corresponds to the session number displayed on the link status panels available through System Support Services.
System Action:
None.
User Action:
None.
Reason:
This message is issued during link activation. It indicates that at least one VTAM session has been established between this system and the system known as linkname. The initial handshaking is now taking place. When it is complete, message N35002 is logged.
System Action:
Link initialization continues.
User Action:
None.
Reason:
This message indicates that a serious error has occurred on the INMC link to the system known as linkname . The link is now inoperative and will remain in 'failed' status until a 'LINK START' command is entered to restart it.
System Action:
The link is inactivated and put into 'failed' status. All sessions of the link are terminated.
User Action:
Other messages should precede this message indicating the cause of the original error. Refer to these messages to see what corrective action is necessary. When the error condition has been corrected, issue a 'LINK START' command to reactivate the link.
Reason:
During session establishment for one of the sessions making up an INMC link, a VTAM RESETSR operation failed, giving error code and sense information as listed.
System Action:
The link will attempt to operate without this session. If no other sessions are available, the link will be inoperative.
User Action:
Check the sense information to see why the RESETSR failed, and whether corrective action is possible. If the condition persists, contact your product support representative.
Reason:
This message is issued to all Monitor status operators when a session request to a remote system fails with sense 080A permission denied. The P2 text describes the error.
This error indicates that the remote partner has no LINK or DEFLINK that matches this system's LU. This may be a temporary condition while the remote system is initializing.
System Action:
The session is retried, based on the link retry interval.
User Action:
Ensure that a LINK START or DEFLINK command is issued in the remote system for the local system's application name.
Note: Do not use VTAM USERVARs in link definitions. The application name is presented to the logon exit, not the USERVAR value.
Reason:
A serious error has occurred on INMC link linkname , from which it cannot recover automatically.
System Action:
The link is forced inactive, and put into 'failed' status.
User Action:
The link can be restarted using a 'LINK START=linkname' command. This error should be reported to your product support representative.
Reason:
A protocol error has occurred on link linkname, from which automatic recovery is not possible. The reason for the data being invalid may be one of: INVALID SEQUENCE NUMBER, SEGMENTATION ERROR or LENGTH ERROR.
System Action:
The link is forced inactive, and put into 'failed' status.
User Action:
The link can be restarted using a 'LINK START=linkname' command. This error should be reported to your product support representative.
Reason:
A protocol error has occurred on link linkname, from which automatic recovery is not possible. The error-type may be one of: INVALID RESPONSE SEQUENCE or LOST OMR.
System Action:
The link is forced inactive, and put into 'failed' status.
User Action:
The link can be restarted using a 'LINK START=linkname' command. This error should be reported to your product support representative.
Reason:
A LINK START command has failed because loadmodule NM030 could not be loaded. The reason for the failure to load NM030 may be determined by the values of r15 and r1.
System Action:
The LINK command fails.
User Action:
Ensure load module NM030 is in a library accessible to SOLVE.
Reason:
This message is issued when link linkname becomes active. The offset (aaaa seconds) is the difference between the hardware clock values (STCK values) on this system and the remote system, expressed relative to this system. This offset will not necessarily match the apparent difference between the time-of-day clocks on the two systems. The propagation delay (bbbb seconds) is the average time taken for a message to be sent one-way between the two systems, as measured during link activation.
System Action:
None.
User Action:
None.
Reason:
During INMC link activation, the values of the hardware clocks on each end of the link are compared, and the difference calculated. This 'time offset' is used to correlate network information containing timestamps, which may be propagated across the INMC link. Link activation of aaaaaa could not calculate the time offset, perhaps because one end of the link is running a back-level SOLVE system, or is not an IBM compatible mainframe system.
System Action:
The time offset for link aaaaaa is set to zero.
User Action:
None.
Reason:
An attempt to establish an INMC link to P1 has been disallowed. Remote region P1 was successfully contacted, but the products licensed in the remote region are not compatible with this region.
System Action:
The INMC link is flagged as DISABLED.
User Action:
The INMC link cannot be used.
Reason:
This message is logged to all monitor status users when a session is established with a NMPC user. userid the userid at the PC.
linkname the name of the link to the PC. username the name of the user taken from their UAMS definition.
System Action:
None.
User Action:
None.
Reason:
An NMPC user has attempted to establish a session on link linkname , however during userid/password validation the maximum number of password retries was exceeded.
System Action:
The session is rejected.
User Action:
See your systems administrator.
Reason:
Confirms a successful change of password for user uuuuuuuu during session establishment from an NMPC system.
System Action:
None.
User Action:
The new password will be required the next time the userid uuuuuuuu is used.
Reason:
During session establishment, an NMPC user has attempted unsuccessfully to change his password.
System Action:
The session is rejected.
User Action:
For more information on the cause of the failure, refer to the journal file on the PC.
Reason:
This message is issued when link linkname becomes active. It indicates that the INMC access method used to transport APPC conversations over an INMC link could not connect. The LU name and SOLVE version of the other system is shown. The reason indicates why the connection could not be established:
NO DTE FOUND - the target SOLVE system is possibly extremely back-level. UNSUPPORTED SOLVE VERSION - the target SOLVE system does not support the INMC/AM facility
STORAGE SHORTAGE - a storage shortage occurred.
System Action:
INMC/AM facilities are not available to this system.
User Action:
If a storage shortage is the reason, increase the storage available to the SOLVE region.
Reason:
This message is issued when the INMC/AM (for APPC) initiated contact over a starting INMC link.
The linkname, domain id, and LUname are shown.
System Action:
INMC/AM link initiation starts.
User Action:
none.
Reason:
This message is issued when the INMC/AM (for APPC) completes contact over an INMC link.
The linkname, domain id, and LUname are shown. The SOLVE version is also displayed.
System Action:
INMC/AM link initiation is complete. APPC sessions may use INMC as an access method.
User Action:
none.
Reason:
This message is issued when the INMC/AM (for APPC) loses contact over an INMC link.
The linkname, domain id, and LUname are shown.
System Action:
The INMC/AM link is closed.
User Action:
Confirm that the INMC link was supposed to be stopped.
Reason:
This message is issued when the INMC/AM (for APPC) tried to initiate contact over a starting INMC link. The target SOLVE system does not support the INMC access method for APPC.
System Action:
INMC/AM link initiation terminates.
User Action:
If the target SOLVE system is back-level, consider upgrading it.
Reason:
This message indicates that the INMC/AM access method was unable to process input from the indicated INMC source node due to a storage shortage.
System Action:
The session is closed.
User Action:
ensure that the SOLVE region has sufficient storage available.
Reason:
An attempt to establish as session using INMC/AM failed due to a lack of storage.
System Action:
The session establishment fails.
User Action:
Ensure that the SOLVE region has sufficient storage.
Reason:
INMC/AM session connection failed for the indicated target system name. The specific type of processing is indicated (the ffffffff operand), and a reason is displayed.
For each processing type, the possible reasons are:
-type- -reason... ACCEPT INTERNAL ERROR - UNKNOWN EPS CID ACCEPT STORAGE SHORTAGE ACCEPT INTERNAL ERROR - INVALID USERDATA LENGTH REJECT INTERNAL ERROR - UNKNOWN EPS CID REJECT STORAGE SHORTAGE REJECT INTERNAL ERROR - INVALID USERDATA LENGTH
System Action:
The session establishment fails.
User Action:
Examine the reason and if possible, correct the problem.
Reason:
An attempt to establish a session using INMC/AM failed due to a lack of storage.
System Action:
The session establishment fails.
User Action:
Ensure that the SOLVE region has sufficient storage.
Reason:
An attempt to send data across an INMC/AM session failed due to a lack of storage.
System Action:
The send fails.
User Action:
Ensure that the SOLVE region has sufficient storage.
Reason:
An attempt to send data across an INMC/AM session failed. The target SOLVE system name is shown. The reasons are:
INTERNAL ERROR - INVALID CID
STORAGE SHORTAGE
INTERNAL ERROR - INVALID USERDATA LENGTH
REQUEST GAVE RC nnnnnnnn
System Action:
The send fails.
User Action:
Correct the problem if possible. It is possible that the target SOLVE system has terminated or INMC contact was lost. If the problem persists, contact your SOLVE product support office.
Reason:
An attempt to establish an APPC session using INMC failed due to a lack of storage.
System Action:
The session establishment fails.
User Action:
Ensure that the SOLVE region has sufficient storage.
Reason:
A INMC/AM (APPC) connection to the named SOLVE system has been lost
System Action:
Any active INMC/AM (APPC) sessions are terminated.
User Action:
Determine why the INMC/AM connection was lost and reestablish it if possible.
Reason:
This message indicates that the INMC/AM access method was unable to process input from the indicated INMC/AM source node due to a storage shortage.
System Action:
The session is closed.
User Action:
ensure that the SOLVE region has sufficient storage available.
Reason:
The NEWS feature was unable to open the CNM ACB for the specified reason code.
System Action:
None.
User Action:
Refer to the appropriate VTAM Programming Guide for an explanation of the error code specified. When the condition has been corrected NEWS recording may be started from within the NEWS option of the System Support Services function.
Reason:
NEWS recording could not be started because of a storage shortage.
System Action:
None.
User Action:
Increase the SOLVE region size.
Reason:
Confirms that NEWS has opened its CNM ACB and that the CNM interface is available.
System Action:
None.
User Action:
None.
Reason:
NEWS encountered a RECEIVE error attempting to receive CNM records from the network.
System Action:
The CNM ACB is closed.
User Action:
Refer to the appropriate VTAM Programming Guide for an explanation of the error codes. Re-opening the CNM ACB may be attempted from the NEWS System Support panel.
Reason:
Notifies all Monitor status Operator Control Services users that the NEWS feature has stopped recording.
System Action:
None.
User Action:
None.
Reason:
The NEWS CNM exit exitname has abended or terminated prematurely.
System Action:
The exit can no longer process CNM records.
User Action:
Refer this to your systems administrator for problem determination.
Reason:
An attempt to send data across the CNM interface failed with the stated sense and feedback codes. If known, a brief explanation of the sense code is also provided.
System Action:
NEWS continues processing.
User Action:
Determine the meaning of the sense codes to diagnose why the failure occurred.
Reason:
Confirms that the message sent across the CNM interface has been received by the target device.
System Action:
NEWS continues processing.
User Action:
None.
Reason:
This message is part of a CNM trace display and supplies the sense code when a CNM RECEIVE macro completes with a negative response returned.
System Action:
NEWS continues processing.
User Action:
Determine the meaning of the sense information to diagnose the reason for the negative response.
Reason:
This message is part of a CNM trace display and indicates that a CNM RECEIVE has completed with a positive response.
System Action:
NEWS continues processing.
User Action:
None.
Reason:
Solicited data returned through the CNM Interface as the result of a REQMS command being issued.
System Action:
None.
User Action:
None.
Reason:
No CNM exit name has been specified.
System Action:
NEWS continues processing with no CNM exit.
User Action:
Provide an exit name if required.
Reason:
Communication with the CNM exit was prevented by a lack of storage.
System Action:
NEWS continues processing with no CNM exit.
User Action:
Increase the SOLVE region size.
Reason:
NEWS has received a CNM record to be processed by CNMPROC but the number of records in the queue waiting to be processed has reached it's maximum.
System Action:
The record is discarded.
User Action:
The queue may be full for several reasons. Use the SH NCL command to determine if a CNM processing procedure is hung on an xxxREAD ( INTREAD, for example) or an FILExxx ( FILEADD, for example). You may find that one of the CNM processing procedures has begun looping or that a resource contention of some sort has halted processing. An NCL procedure producing alerts using CNMALERT may be looping. It is also possible that a device in the network is producing large volumes of CNM records due to an error. If there is a high volume of ISR traffic, the ISR queue limit may have been reached. If you wish to clear the backlog, simply use the SYSPARMS CNMPROC= command to stop and restart CNMPROC.
Reason:
The data supplied on an &CNMSEND statement was not valid hexadecimal display data.
System Action:
The procedure is terminated.
User Action:
Correct the error and retry the request.
Reason:
No data was specified on an &CNMSEND statement.
System Action:
The procedure is terminated.
User Action:
Correct the error and retry the request.
Reason:
An attempt has been made using &CNMALERT or &CNMSEND to deliver a CNM record to a local or remote NEWS system for processing, but has failed due to one or more error conditions.
System Action:
The issuing NCL procedure continues, with &RETCODE set to 8 to indicate that the send has failed.
User Action:
Check that the INMC link to the remote host has been activated, and that the NEWS facilities in ISR (Inter-System Routing) have been enabled using the ISR command, from both the remote and local ends of the link. Also check that the NEWS ACB at the remote end has been opened, and (for
&CNMALERT) that the CNMPROC in the destination host is active.
Reason:
An attempt has been made using &CNMSEND to send a CNM record to VTAM through the CNM interface for processing, but the NEWS ACB is not open and the record cannot be sent.
System Action:
The send fails, and the NCL procedure is notified by setting the &RETCODE system variable to a value of 8.
User Action:
The NEWS ACB should be opened, using the CNM START command or through the $SN CNM parameter group.
Reason:
The CNM request failed because of a storage shortage.
System Action:
NEWS continues processing.
User Action:
Determine the cause of the storage shortage. If necessary increase the SOLVE region or partition size.
Reason:
Each CNM request is assigned a unique number from 1 to 4095. This message indicates that a number could not be assigned because there were already 4095 requests outstanding.
System Action:
The request is rejected, and the NCL procedure is notified with a return code of 8 in the RETCODE system variable.
User Action:
Retry the request. If the condition persists, the queue has become clogged for some reason. Attempt to find out why the queue has become full. If you require assistance, contact your product support representative.
Reason:
VTAM has rejected a CNM record sent by NEWS across the CNM interface and has supplied information in the RPL to describe the reason(s) for the rejection.
System Action:
NEWS extracts the information from the RPL and attempts to interpret it to supply a meaningful explanation for the failure of the send.
User Action:
Take action depending on the explanation given. For example, the rejection may indicate that the targeted resource does not exist or does not support the function you have requested. More information about the Return Code, Feedback and Sense codes may be found in the VTAM Programming Guide for your release of VTAM.
Reason:
A &CNMSEND was used to deliver a CNM record to a remote SOLVE system for processing but before a reply was received the communication between the local and remote systems failed, preventing the reply from being returned.
System Action:
The NCL procedure is notified by a value of 8 in the &RETCODE system variable and SOLVE will automatically try to re-establish contact with the remote system.
User Action:
If the INMC link to the remote system does not recover, you may find that another user has deliberately disabled the INMC link between the local and remote systems, or a permanent hardware or software error has occurred in the communications between the two hosts. Contact your systems administrator.
Reason:
VTAM has rejected the send of a CNM record by NEWS, but has given no explanation for the rejection. No Return code, Feedback or Sense code has been supplied in the RPL to explain the reason for the rejection.
System Action:
The NCL procedure is notified by setting the RETCODE system variable value to 8.
User Action:
None.
Reason:
An attempt to queue a CNM alert to CNMPROC using &CNMALERT MODE=INSERT has been rejected because either the NCL procedure which issued the
&CNMALERT was not CNMPROC or executed by CNMPROC, or the context of the current record has been lost due to a CNMDEL or a non-specific
&CNMCONT.
System Action:
The NCL procedure is flushed.
User Action:
Remove the MODE=INSERT parameter from the &CNMALERT statement, or issue the &CNMALERT before issuing a &CNMCONT or &CNMDEL.
Reason:
An &CNMSEND or &CNMALERT statement has been rejected because the length ( aaaa ) found in the DELIVER RU supplied was greater than the imbedded RU which followed and whose length it represents.
System Action:
&RETCODE is set to 8 and processing of the NCL procedure continues. This message is available in the SYSMSG variable.
User Action:
Correct the CNM request data specified on the &CNMALERT or &CNMSEND statement.
Reason:
A CNM record passed on an &CNMALERT or &CNMSEND statement could not be processed because its format was invalid.
System Action:
The message is returned in the &SYSMSG NCL variable, and the statement completes with RETCODE 8.
User Action:
Correct the data passed on the &CNMALERT or &CNMSEND statement.
Reason:
This message is written to the SOLVE activity log if an NCL procedure issues a &CNMREAD verb to receive a solicited reply from the CNM interface and a storage shortage condition has prevented the successful processing of the reply.
System Action:
The NCL procedure waiting for the reply is notified by a value of 8 in the &RETCODE system variable and message N37801 in the &SYSMSG variable.
User Action:
Contact your product support representative and report the storage shortage condition.
Reason:
A message received by a &CNMREAD statement contained invalid CNM format data.
System Action:
Processing continues with error data.
User Action:
Investigate cause of possible invalid CNM format record.
Reason:
The MDO supplied to an &CNMPARSE statement is invalid.
System Action:
None.
User Action:
Check the syntax of the MDO name and verify it against its corresponding MAP definition.
Reason:
An internal error has occurred while processing Mapping Services.
System Action:
None.
User Action:
Contact you product support representative.
Reason:
The internal recursion stack limit was exceeded while processing an &CNMPARSE operation.
System Action:
None.
User Action:
Contact your product support representative.
Reason:
This message contains the destination/origin, type and status of a CNM record captured by the CNMTRACE command and is issued immediately prior to message(s) N38002.
System Action:
Processing continues.
User Action:
None.
Reason:
This message contains the hexadecimal data captured when the CNMTRACE command is in effect.
System Action:
None.
User Action:
None.
Reason:
Required operands on the DEFALIAS, REPALIAS or DELALIAS command were omitted.
System Action:
The command is rejected.
User Action:
Correct the error and retry the command. For a description of the commands refer to the command help.
Reason:
An attempt was made to provide an invalid value to the operand described in the message.
System Action:
The command is rejected.
User Action:
Determine the correct value and retry the command.
Reason:
An attempt was made to provide an invalid value to the operand described in the message.
System Action:
The command is rejected.
User Action:
Determine the correct value and retry the command.
Reason:
When specifying a generic alias name (or real name) on the DEFALIAS command a generic real name (or alias name) must also be provided to preserve the single name-to- name mapping of the Alias Name Translation Facility.
System Action:
The command is rejected.
User Action:
Correct the error and retry the command.
Reason:
The alias name, previously defined by a DEFALIAS command, has been either deleted or replaced following a DELALIAS or REPALIAS request.
System Action:
As described above.
User Action:
None.
Reason:
An invalid operand was specified on the command.
System Action:
The command is rejected.
User Action:
Correct the error and retry the command.
Reason:
This is a warning message indicating that the DEFALIAS command just processed refers to a real name and network previously allocated an alias name. This may be intentional.
System Action:
Processing continues.
User Action:
Ensure that the result was intentional, otherwise delete one of the alias name definitions (using the DELALIAS command) as the reverse name mapping (real to alias) is no longer unique.
Reason:
A REPALIAS or DELALIAS command referenced an alias name and network which was not defined.
System Action:
The command is ignored.
User Action:
Determine the correct action and retry.
Reason:
An attempt was made to define an alias name/network pair but a previous DEFALIAS command had already defined this name and network.
System Action:
The command is rejected.
User Action:
Correct and retry the command if necessary.
Reason:
This message provides details solicited with the SHOW DEFALIAS command. Refer to message N38304 which provides the column headings for more details on the contents.
System Action:
None.
User Action:
None.
Reason:
An attempt was made to use the invalid operand described in the message on the SHOW DEFALIAS command.
System Action:
The command is rejected.
User Action:
Correct the error and retry the command.
Reason:
An invalid operand was specified on the SHOW DEFALIAS command.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
This message provides the heading describing the line contents for a SHOW DEFALIAS command. Following this message one or more N38301 messages will format the details of those DEFALIAS entries selected by the SHOW DEFALIAS. ALIAS and NET define the resource as known in this system. RNAME and RNET describe the real name of the resource and the network which owns that resource. For a TYPE=LU display the RCDRM field indicates the owning CDRM if known.
System Action:
None.
User Action:
None.
Reason:
This message terminates a SHOW DEFALIAS display. count provides the total number of DEFALIAS entries selected for display, and type describes the type of entries selected and may be either LU, MODE or COS.
System Action:
None.
User Action:
None.
Reason:
This message is in response to a SHOW CNMTRACE command when no CNM traces are active.
System Action:
None.
User Action:
None.
Reason:
This message provides the heading describing the line contents for a SHOW CNMTRACE display. Following this message one or more messages N38308 will format the details of those CNMTRACE entries selected by the SHOW CNMTRACE. USERID is the user starting the trace. ID# is the unique trace identification number. COUNT is the number of traces matching this trace request that have been counted. RU-TYPE is the RU type (if any is specified) that the trace request is tracing. RESOURCE is the network name of the PU to be traced. I-O is 'Y' or 'N' to indicate if inbound and/or outbound RUs are being traced. L-R is 'Y' or 'N' to indicate whether or not tracing is being performed for local and/ or remote systems. If tracing is performed for a remote system, LINK may contain the name of a specific remote system being traced.
System Action:
None.
User Action:
None.
Reason:
This message provides details solicited with the SHOW CNMTRACE command. Refer to message N38307 which provides the column headings for more details on the contents.
System Action:
None.
User Action:
None.
Reason:
This message terminates a SHOW CNMTRACE display. 'aaaaaaaa' provides the total number of active CNMTRACE entries, and 'bbbbbbbb' shows the number of CNMTRACE entries displayed.
System Action:
None.
User Action:
None.
Reason:
A parameter has been used twice on the SHOW CNMTRACE command.
System Action:
None.
User Action:
Review SHOW CNMTRACE command usage.
Reason:
An invalid operand was specified on the SHOW CNMTRACE command.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
An alias name translation request failed because of a storage shortage.
System Action:
The request is not processed.
User Action:
Determine the cause of the storage shortage. If necessary increase the SOLVE region or partition size.
Reason:
One or more operands required on the XLATE command were omitted.
System Action:
The command is rejected.
User Action:
Correct and retry the command.
Reason:
An invalid operand was specified on the XLATE command.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
An attempt was made to specify an invalid value for the XLATE command operand described in the message.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
This message displays the results of an XLATE command. The name1/net1 provide the name and network of the input resource requiring translation, which may be an LU, COS or MODE name of type ALIAS or REAL. The name2/net2 are the names that the name1/net1 pair would be translated to in the target network as specified on the XLATE command.
System Action:
None.
User Action:
None.
Reason:
The name1/net1 input to an XLATE command was not successfully translated by the Alias Name Translation Facility. The sense code shown was returned.
System Action:
None.
User Action:
None.
Reason:
The TARGNET operand of the XLATE command must be specified unless the input name is an LU and alias to real name conversion was requested explicitly or by default.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
The CNM START command has been issued to start CNM processing.
System Action:
NEWS will attempt to open the CNM ACB and start receiving records across the CNM interface from the local SSCP.
User Action:
None.
Reason:
The CNM STOP command has been issued to stop CNM processing.
System Action:
NEWS will close the CNM ACB and CNM records will no longer be received from the local SSCP.
User Action:
None.
Reason:
The CNM or CNMTRACE command has been issued but the required operands have been omitted or are invalid.
System Action:
The command is rejected.
User Action:
The CNM command accepts two operands, START and STOP. You should have only one of these operands on the command (not both). The CNMTRACE command also accepts a CANCEL=id operand (id must be in the range 1 - 999999).
Reason:
The CNM START command has been issued but CNM processing has already been activated.
System Action:
The command is rejected.
User Action:
None.
Reason:
The CNM STOP command has been issued but CNM processing was not active and hence cannot be stopped.
System Action:
The command is rejected.
User Action:
None.
Reason:
An attempt to open the CNM ACB failed, for the specified reason code.
System Action:
None
User Action:
Refer to the appropriate VTAM Programming Guide for an explanation of the error code specified.
Note: A common error code is x'5A', which indicates that the ACB name is not defined to VTAM. Correct the name, or define the ACB name to VTAM, and retry.
Reason:
An invalid operand was specified on the CNMTRACE command.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
A CNMTRACE command has been issued to start CNM record tracing. aaaaa is the identifier for the trace initiated.
System Action:
NEWS will begin tracing CNM records of the type specified by the CNMTRACE command.
User Action:
None.
Reason:
A CNMTRACE CANCEL=n or CNMTRACE STOP command has been issued where aaaaaaaa is the number of CNMTRACE requests terminated (if greater than 1).
System Action:
The specified CNM trace(s) will terminate.
User Action:
None.
Reason:
A CNMTRACE STOP command has been issued but no CNM traces were active at the time.
System Action:
None.
User Action:
None.
Reason:
Duplicate operands were entered for a CNMTRACE command.
System Action:
The CNMTRACE command is rejected.
User Action:
Correct the error and retry the command.
Reason:
A CNM record matching a CNMTRACE request mask arrived but insufficient storage was available to process the trace.
System Action:
The request is not processed.
User Action:
Determine the cause of the storage shortage. If necessary increase the SOLVE region or partition size.
Reason:
A CNMTRACE CANCEL=n command has been issued but no CNM trace with an identifier matching that specified by 'n' was found.
System Action:
The command is rejected.
User Action:
Check that the correct identifier was specified and re-issue the command.
Reason:
The CNM ACB was in retry mode and a CNM STOP command was issued.
System Action:
The open retry against the CNM ACB is cancelled.
User Action:
N/A
Reason:
This message is part of a CNM trace display and indicates that a CNM RECEIVE or SEND has completed on a remote SOLVE system with a positive response.
System Action:
NEWS continues processing.
User Action:
None.
Reason:
This message is part of a CNM trace display and indicates that a CNM RECEIVE or SEND has completed on a remote SOLVE system with a negative response.
System Action:
NEWS continues processing.
User Action:
Determine the meaning of the sense information to diagnose the reason for the negative response.
Reason:
An invalid NEWS record was received across ISR on link name AAAAAAAAAA.
System Action:
The LINK is stopped and processing on the record ignored.
User Action:
Correct source of invalid ISR format input.
Reason:
This message is written to the activity log to indicate that NEWS is initiating the establishment of ISR communication with the indicated remote SOLVE system.
System Action:
Establishment of the ISR connection is initiated.
User Action:
None. This message is informational only.
Reason:
This message indicates the successful establishment of ISR communication with the indicated remote SOLVE system.
System Action:
The NEWS ISR facilities are enabled.
User Action:
Proceed to use the NEWS ISR facilities.
Reason:
This message indicates that the NEWS ISR facilities have been disabled. Communication between the local SOLVE system and the indicated remote SOLVE system has been interrupted.
System Action:
An attempt is made to re-establish INMC contact at regular intervals if the link has actually failed. It is possible that the link was deliberately shut down by an operator.
User Action:
Take no immediate action. It is possible for the INMC link to recover automatically from most communications failures. Normally, a communications line has had an error and as soon as the line is restarted, INMC will be able to recover the link.
Reason:
The installation provided NEWS exit (exitname) could not be loaded. Possible reasons are that it was not available in the SOLVE STEPLIB DD, or there was insufficient storage to load the exit into the SOLVE address space.
System Action:
No calls will be made to the exit.
User Action:
Check the system log and SOLVE job log for possible causes. Correct and attempt to reinitialize the exit.
Reason:
The installation provided NEWS exit (load module name module) has abended with the specified abend code. If the abend was a system abend, xxx is set to SYS; for a user abend xxx will be set to USR. This message is issued during system initialization only.
System Action:
No further calls are made to the exit.
User Action:
Identify and correct the abend cause. The exit may be restarted from the NEWS option of System Support Services.
Reason:
The operand xxxxxxxx of the SYSMON command is not recognized.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
No PU name was specified on the SYSMON command.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
The PU name specified on the SYSMON command is longer than 8 characters.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
A lack of storage prevented successful execution of the SYSMON command.
System Action:
The command is rejected.
User Action:
If the condition persists, consider increasing the SOLVE region size.
Reason:
No text to be sent to the PU was supplied on the SYSMON command.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
The data supplied on the REQMS command either was not an even number of characters long or contained other than hexadecimal characters.
System Action:
The command is rejected.
User Action:
The data on a REQMS command must be character format hexadecimal, where each two characters represents one hexadecimal byte. The characters can only be A to F and 0 to 9. Correct the error and retry.
Reason:
The data supplied on the REQMS command cannot exceed 512 characters in length.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
No data was supplied on the REQMS command.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
The data supplied on a REQMS command must be at least 32 characters in length.
System Action:
The command is rejected.
User Action:
Correct the error and retry.
Reason:
The REQMS command cannot be processed because of a storage shortage.
System Action:
NEWS continues processing.
User Action:
If necessary increase the SOLVE region or partition size.
Reason:
NEWS was unable to allocate a correlator number to a request to be sent to VTAM across the CNM interface. All available correlator numbers were in use by outstanding requests.
System Action:
The command is rejected.
User Action:
Wait, then retry the command.
Reason:
NEWS was unable to send a request to VTAM across the CNM interface because the NEWS CNM ACB was not open.
System Action:
The command is rejected.
User Action:
Review the log for the $SN CNM parameter group (CNM Interface Details). If necessary, update the details and action the parameter group to activate the CNM ACB used by the NEWS component.
Reason:
NEWS was unable to send a request to VTAM across the CNM interface because a VTAM SEND macro failed.
System Action:
The command is rejected.
User Action:
xx, yy and zzzzzzzz are, respectively, the VTAM return code, feedback and sense information which may be interpreted from the VTAM Programming Guide .
Reason:
This message is part of a CNM trace display and supplies the sense code when a CNM SEND macro completes with a negative response returned.
System Action:
NEWS continues processing.
User Action:
Determine the meaning of the sense information to diagnose the reason for the negative response.
Reason:
This message is part of a CNM trace display and indicates that a CNM SEND has completed with a positive response.
System Action:
NEWS continues processing.
User Action:
None.
Reason:
Data received in reply to a SYSMON command is not of the correct format.
System Action:
The data is ignored.
User Action:
This could be a problem with the generation of the data by the controller from which the data was received. A VTAM buffer trace of the NEWS VTAM ACB will show the data received, which should be a RECFMS type 4 response.
Reason:
A negative response was received in reply to the data sent to VTAM as a result of a SYSMON command. puname is the name of the PU to which the data was sent, ssssssss is the sense code returned, and reason text is the meaning of the sense code, if known.
System Action:
Processing of the SYSMON command ends.
User Action:
Interpret the meaning of the sense code, and retry the command if appropriate.
Reason:
Confirms the successful sending of a message to the control operator of the 3600/4700 controller xxxxxxxx via a SYSMON TYPE=MSG command.
System Action:
None.
User Action:
None.
Reason:
This is the reply to a REQMS command. The data is exactly as received across the CNM interface. Multiple N39701 messages will be returned if the data received is longer than 60 bytes, each message formatting 60 bytes into character format hexadecimal.
System Action:
None.
User Action:
Refer to the REQMS command description.
Reason:
A negative response was received in reply to the data sent to VTAM as a result of a REQMS command. ssssssss is the sense code returned, and reason text is the meaning of the sense code, if known.
System Action:
Processing of the REQMS command ends.
User Action:
Interpret the meaning of the sense code, and retry the command if appropriate.
Reason:
Signifies the end of N39701 messages received in reply to a REQMS command.
System Action:
None.
User Action:
None.
Reason:
This message is received when the positive response from the network resource is received following the sending of CNM data using the REQMS command and where the data content indicated that no solicited data was expected in reply.
System Action:
None.
User Action:
None.
Reason:
Issued in response to the STATUS command to show that this SOLVE is configured with the NEWS feature, which is at release level nlvl.
System Action:
None.
User Action:
None.
Reason:
Issued in response to the STATUS command to show the status of the CNMPROC procname.
System Action:
None.
User Action:
None.
Reason:
Issued in response to the STATUS command to show whether the NEWS VTAM ACB is open.
System Action:
None.
User Action:
None.
Reason:
Issued in response to a SYSPARMS CNMPROC=FLUSH command if a CNMPROC is not currently active, or is not currently waiting on an CNMREAD statement.
System Action:
None.
User Action:
Retry the command. If a CNMPROC is active, this condition could indicate that it has not been written to always loop around to an
&CNMREAD statement, as should be the case.
Reason:
Issued in response to a SYSPARMS CNMPROC=procname command if a CNMPROC is already active.
System Action:
None.
User Action:
If you wish to invoke a new CNMPROC, the active one must first be flushed using the SYSPARMS CNMPROC=FLUSH command.
Reason:
To change the NEWS ACB name the ACB must be closed first using the NEWS option of the System Support Services function.
System Action:
None.
User Action:
Close the NEWS ACB then retry.
Reason:
A MODCB macro for the acbname shown failed with the return codes shown.
System Action:
None.
User Action:
Determine the cause of the error. Correct and retry.
Reason:
Issued in response to the STATUS command to show that this SOLVE system is configured with the XIS feature, which is at release level nlvl.
System Action:
None.
User Action:
None.
Reason:
A NEWS security structured field value was invalid.
System Action:
The value is ignored.
User Action:
Correct the security exit value returned and restart the exit.
Reason:
A SOLVE:Attach for Netware security structured field value was invalid.
System Action:
The value is ignored.
User Action:
Correct the security exit value returned and restart the exit. Check the processing for SF x'0535'.
Reason:
An NCL procedure has tried to use the &CNMCONT verb but permission has been denied. Use of the &CNMCONT verb is only valid from CNMPROC or from an NCL procedure executed by CNMPROC.
System Action:
The procedure is flushed.
User Action:
Remove the &CNMCONT statement from the procedure, or ensure the procedure is executed as or by CNMPROC. Normally only CNMPROC would ever issue a &CNMCONT, unless it is required by a CNM processing procedure executed by CNMPROC to re- route the record to a remote system for processing.
Reason:
A CNM reply message cannot be processed because of a storage shortage.
System Action:
NEWS continues processing.
User Action:
If necessary increase the SOLVE region or partition size.
Reason:
A negative response was received across the CNM interface specifying the nominated sense and feedback information.
System Action:
NEWS continues processing.
User Action:
Determine the meaning of the sense code to diagnose the reason for the negative response.
Reason:
A CNM read failed for the stated reason codes.
System Action:
NEWS continues processing.
User Action:
Determine the meaning of the RPL return and sense code information.
Reason:
An NCL procedure has issued the &CNMREAD verb but due to an error the read has failed. The text aaaa explains the reason for the failure.
System Action:
The failure is indicated by a value of 8 in the &RETCODE system variable.
User Action:
The message text should explain the reason for the failure - take action to correct the cause of the failure.
Reason:
Current release of SOLVE:LINK for TCP/IP does not support VARS and ARGS operands on &SOCKET verb.
System Action:
NCL procedure terminates.
User Action:
Correct NCL procedure.
Reason:
This message is issued when a socket error occurs after a TCP/IP call. It is a translation of the errno number to the errno returned from the call.
System Action:
Dependent on the calling program.
User Action:
A more specific error message should precede this. See the "NCL REFERENCE" for a list of errno values.
Reason:
The heading displayed in response to a SHOW TCPIP USERS command. This information is used to determine who is using TCP/IP services and how many sockets are in use.
System Action:
None.
User Action:
None.
Reason:
A detail line displayed in response to the SHOW TCPIP USERS command. The fields are as follows:
userid The ID of the user of TCP/IP services.
nclid The ID of the NCL process using TCP/IP services.
procname The name of the NCL procedure using TCP/IP services.
luname The user region name.
soc The number of open sockets used by the NCL process.
System Action:
None.
User Action:
None.
Reason:
The heading is displayed in response to a SHOW SOCKETS command.
System Action:
None.
User Action:
For more information, see help for messages N3AF04 and N3AF42.
Reason:
A detail line displayed in response to the SHOW SOCKETS command. The fields are as follows:
Displays the ID of the socket used internally.
Displays the type of socket, for example, RAW, UDP, TCP. A TCP Listener is TCPL and TCPI is an associated inbound connection. TCPO is an outbound connection.
Displays the ID of the NCL process using TCP/IP services.
Displays the ID of the socket used by the TCP/IP stack.
Displays the local port number assigned to the socket.
Displays the port number of a peer host if the socket is a TCP connection. Also, the last sent to or received from port for a UDP socket.
Displays the IP address of the peer host.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW TCPIP STATUS command. The fields are as follows:
ACTIVE—The TCP/IP sockets interface is active, and TCP/IP requests can be issued.
INACTIVE—The TCP/IP sockets interface is inactive.
STARTING—The TCPIP START command has been issued, and the sockets interface is initializing.
STOPPING—The TCPIP STOP command has been issued and the sockets interface is terminating.
All CA NetMaster TCP/IP functions use the primary TCP/IP sockets interface, for example, IP Node Monitor and IP Diagnostics. This interface is also the default interface that a TCPIP STOP command stops and a TCPIP MODIFY command alters.
4 indicates that the sockets interface uses IPv4 sockets and 6 indicates that the interface uses IPv6 sockets.
When using IPv4 sockets, CA NetMaster can communicate with IPv4 partner applications only. When using IPv6 sockets, CA NetMaster can communicate with IPv4 and IPv6 partner applications.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW TCPIP STATUS command.
string is the options string specified following the OPTIONS operand of the TCPIP START, TCPIP DEFINE, or TCPIP MODIFY command.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW TCPIP STATUS command. The fields are as follows:
ipaddress The IP address of the local host.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW TCPIP STATUS command. The fields are as follows:
hostname The short name of the local host.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW TCPIP STATUS command. It shows the server's type and port number. The fields are as follows:
type is either INMC or APPC.
port is the server's port number.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW TCPIP STATUS command.
status specifies the trace settings for the TCP/IP sockets interface. Possible values are:
NO—The TCP/IP trace is not active.
SUMMARY—The TCP/IP trace is active, summary trace data is written the log.
YES—The TCP/IP trace is active, all trace data is written to the log.
ASCII—The TCP/IP trace is active, all trace data is written to the log, character data is assumed to be ASCII.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW TCPIP STATUS command. The fields are as follows:
hostname The full name of the local host.
System Action:
None.
User Action:
None.
Reason:
This message is displayed in response to a SHOW TCPIP STATUS command. The fields are as follows:
ACTIVE—The TCP/IP shared server is active.
INITIALISING—The TCP/IP shared server is initializing.
INACTIVE—The TCP/IP shared server is inactive.
System Action:
None.
User Action:
None.
Reason:
A detail line displayed in response to the SHOW TCPIP LINKS command. The fields are as follows:
luname The user's LU name (logical user name).
pid Unique process number. A process number is allocated when the &SOCKET ALLOCATE verb is executed.
last-request The last function executed by TCP/IP services.
soc The number of open sockets used by the process.
System Action:
None.
User Action:
None.
Reason:
This message is displayed in response to a SHOW TCPIP AM command. It provides the following headings for the individual TCPIP AM sessions.
The headings are:
UNKNOWN—The session type has not yet been determined.
AM- PRI—A TCPIP AM (INMC/APPC) session, primary (connector).
AM-SEC—A TCPIP AM (INMC/APPC) session, secondary (acceptor).
TELNET—A TCPIP Telnet session, under negotiation.
TELNET-3270—A TCPIP TN3270 session.
TELNET-3270E—A TCPIP TN3270E terminal session.
TELNET-PRINT—A TCPIP TN3270E printer session (LU1 printer).
TELNET-NVT—A TCPIP NVT session (treated as LU1).
System Action:
None.
User Action:
None.
Reason:
This message is displayed in response to a SHOW TCPIP AM command. The message displays the session information for the individual TCPIP AM sessions.
For more information, see message N3AF15.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW TCPIP STATUS command.
status is one of the following:
VENDOR - TCP/IP domain name lookup is using the vendor supplied interface.
SOLVE - TCP/IP domain name lookup is using the SOLVE domain name resolver (DNR).
System Action:
None.
User Action:
None.
Reason:
This heading is displayed in response to a SHOW SOCKETS command.
System Action:
None.
User Action:
For more information, see the online help for messages N3AF19 and N3AF46.
Reason:
This message displays a detail line in response to the SHOW SOCKETS command. The fields are as follows:
socket displays the ID of the socket used internally.
type displays the type of socket (for example, RAW, UDP, and TCP). A TCP listener is TCPL, and TCPI is an associated inbound connection. TCPO is an outbound connection.
owner displays the ID of the NCL process using the TCP/IP services.
clientid displays the ID of the socket used by the TCP/IP stack.
lpath displays the local UNIX path assigned to the socket.
ppath displays the UNIX path of a peer host if the socket is a TCP/IP connection.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW TCPIP STATUS command.
type is the type of TCP/IP sockets interface.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW TCPIP STATUS command. The message text identifies the type and version of SOLVE's TCP/IP interface. The following message identifies the host operating system TCP/IP software.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW TCPIP STATUS command. The message text comes directly from the vendor stack.
System Action:
None.
User Action:
None.
Reason:
The heading displayed is in response to a SHOW TCPIP STATUS command.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW TCPIP SERVER command. It is a heading line preceding msg N3AF31.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW TCPIP SERVER command. ssssssssssssssss is the server name ppppp is the port number cccccc is the socket ID ttt is either YES or NO indicating if this is a TAKEOVER server.
System Action:
None.
User Action:
None.
Reason:
The heading displayed is in response to a SHOW SOCKETS command.
System Action:
None.
User Action:
For more information, see the help for messages N3AF04 and N3AF42.
Reason:
This heading is displayed in response to a SHOW SOCKETS command.
System Action:
None.
User Action:
For more information, see the help for messages N3AF04 and N3AF42.
Reason:
A detail line displayed in response to the SHOW SOCKETS command.
server-name is the CA NetMaster server name.
System Action:
None.
User Action:
None.
Reason:
The heading displayed is in response to a SHOW SOCKETS command.
For more information, see the online help for messages N3AF19 and N3AF46.
System Action:
None.
User Action:
None.
Reason:
This heading is displayed in response to a SHOW SOCKETS command.
For more information, see the online help for messages N3AF19 and N3AF46.
System Action:
None.
User Action:
None.
Reason:
This heading is displayed in response to a SHOW SOCKETS command.
System Action:
None.
User Action:
None.
Reason:
This message displays a detail line in response to the SHOW SOCKETS command.
server-name is the name of the CA NetMaster server.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW TCPIP or SHOW SOCKETS command.
It indicates that the command cannot be processed because an invalid or unknown operand was specified.
operand is the invalid or unknown operand.
System Action:
The SHOW TCPIP or SHOW SOCKETS command is ignored.
User Action:
Correct or remove the invalid operand and reenter the command.
Reason:
This message is issued in response to a SHOW TCPIP or SHOW SOCKETS command.
It indicates that the NAME operand of the command specified the name of a TCP/IP sockets interface that is not defined.
The fields are as follows:
System Action:
The SHOW TCPIP or SHOW SOCKETS command is ignored.
User Action:
Correct or remove the NAME operand and reenter the command.
Reason:
Execution of a TCP/IP request has failed. The fields are as follows:
request is the TCP/IP request that failed.
rc is the return code.
rsn is the reason code.
err is the error code as set by the TCP/IP API.
pid is the process ID.
sid is the socket ID.
System Action:
The APPC server terminates.
User Action:
Contact your technical support helpdesk.
Reason:
The address space could not allocate a TCP/IP subtask.
System Action:
APPC server terminates.
User Action:
Check system log for additional error messages.
Reason:
The APPC server has stopped. No further APPC TCP/IP connections are possible.
System Action:
Connect request to APPC server port are rejected.
User Action:
None.
Reason:
An attempt to modify a TCP/IP SYSPARM was made when the TCP/IP access method was not active.
System Action:
The command is ignored.
User Action:
Ensure the TCP/IP access method is active.
Reason:
You attempted to modify the IPPORT SYSPARM value. However, the new port number is presently defined as a TELNET port (via the TNCTL command).
System Action:
The command is ignored.
User Action:
Select a port number that is not the same as a defined TELNET port.
Reason:
The TCP/IP shared port/path server is active.
type identifies whether pppp is a port number or path.
pppp is the server port number or path.
ssss is the server socket number.
System Action:
None.
User Action:
None.
Reason:
The TCP/IP shared port/path server was unable to register the port or path. The error information is displayed.
Additional information follows this message.
System Action:
The server will retry registration in 30 seconds.
User Action:
Check the error information. If ERRNO indicates that the port or path is in use, change it using the SOCKETS parameter group.
Reason:
The TCP/IP shared port/path server has an error on ACCEPT. The error information is displayed.
Additional information follows this message.
System Action:
The server terminates. It restarts when the primary TCP/IP sockets interface is restarted.
User Action:
Usually, no user action is required. It is likely that a TCP/IP sockets interface problem has occurred. When the primary TCP/IP sockets interface restarts, the server restarts.
Reason:
A TCP/IP error occurred when negotiating an incoming connection request. The error information relates to the &SOCKET NCL verb.
System Action:
The connection is not accepted.
User Action:
Review the error information to identify the problem and correct it.
Note: For information about the &SOCKET return code, feedback code, and error number, see the Network Control Language Reference Guide.
Reason:
An error occurred when negotiating an incoming connection request.
This message may be followed by the N3AO87 message, which dumps the incoming data buffer.
System Action:
The connection is not accepted.
User Action:
Review the error information, and correct the problem.
Reason:
This message follows an N3AO86 message and contains the dump of an incoming connection request.
It is followed by N3ZJ91 messages that display the incoming data buffers, which may help you diagnose the problem.
System Action:
None.
User Action:
See N3AO86.
Reason:
An attempt to connect to another CA NetMaster system using the TCP/IP access method failed. The fields are as follows:
This message is logged and precedes N3ZJ91 messages that contain an incoming data buffer that may help diagnose the error.
System Action:
None.
User Action:
Dependant on the error description in the message.
Reason:
This message is logged following an N3AP90 message and contains a dump of an incoming data buffer.
This message is logged, and precedes N3ZJ91 messages containing an incoming data buffer that may help diagnose the error.
System Action:
None.
User Action:
Dependant on N3AP90
Reason:
Execution of a TCP/IP request has failed. The fields are as follows:
request is the TCP/IP request that failed.
rc is the return code.
rsn is the reason code.
err is the error code as set by TCP/IP API.
pid is the process ID.
sid is the socket ID.
System Action:
Connect processing terminates.
User Action:
Contact your technical support help desk.
Reason:
The address space could not allocate a TCP/IP subtask.
System Action:
Connect processing terminates.
User Action:
Check system log for additional error messages.
Reason:
Execution of a TCP/IP request has failed. The fields are as follows:
request is the TCP/IP request that failed.
rc is the return code.
rsn is the reason code.
err is the error code as set by TCP/IP API.
pid is the process ID.
sid is the socket ID.
System Action:
The error is handled by the calling service.
User Action:
Contact your technical support help desk.
Reason:
This message is issued in response to a TCPIP command.
It indicates that the command has been processed.
'option' is the command option that was specified.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a TCPIP command. It indicates that the command was not processed because the TCP/IP sockets interface that the command was directed to is in a status that prevents processing, for example, a TCPIP START command when the TCP/IP sockets interface is already active.
The fields are as follows:
System Action:
The TCPIP command is ignored.
User Action:
Determine if the TCPIP command is needed.
Reason:
This message is issued in response to a TCPIP START command. It indicates that the command was not processed because the command operand PRIMARY=YES was specified or was selected by default, and a primary TCP/IP sockets interface is already active.
System Action:
The TCPIP START command is ignored.
User Action:
Determine if the TCPIP START command is needed.
Reason:
This message is issued in response to a TCPIP command. It indicates that the command cannot be processed because the TYPE operand specified an unknown TCP/IP sockets interface.
The fields are as follows:
IBM: Interfaces to IBM Communications Server using IPv4 HPNS (High Performance Native Sockets).
IBMV4: Interfaces to IBM Communications Server using IPv4 HPNS. IBMV4 is a synonym for IBM.
IBMV6: Interfaces to IBM Communications Server using IPv6 HPNS.
TCPAXS: Interfaces to CA TCPaccess Communications Server 5.2 or later.
VM: Interfaces to IBM VM TCP/IP.
XNFTCP: Interfaces to Hitachi XNF/TCP.
TISP: Interfaces to Fujitsu TISP.
In most cases, the TYPE operand can be omitted. CA NetMaster selects the correct TCP/IP sockets interface based on the current environment.
System Action:
The TCPIP command is ignored.
User Action:
Correct or remove the TYPE operand and reenter the command.
Reason:
This message is issued in response to a TCPIP command. It indicates that the command cannot be processed because the TYPE operand specified a TCP/IP sockets interface that is not supported in this environment.
The fields are as follows:
IBM: Interfaces to IBM Communications Server using IPv4 HPNS (High Performance Native Sockets).
IBMV4: Interfaces to IBM Communications Server using IPv4 HPNS. IBMV4 is a synonym for IBM.
IBMV6: Interfaces to IBM Communications Server using IPv6 HPNS.
TCPAXS: Interfaces to CA TCPaccess Communications Server 5.2 or later.
VM: Interfaces to IBM VM TCP/IP.
XNFTCP: Interfaces to Hitachi XNF/TCP.
TISP: Interfaces to Fujitsu TISP.
In most cases, the TYPE operand can be omitted. CA NetMaster selects the correct TCP/IP sockets interface based on the current environment.
System Action:
The TCPIP START command is ignored.
User Action:
Correct or remove the TYPE operand and reenter the command.
Reason:
This message is issued in response to a TCPIP command. It indicates that the command cannot be processed because the TYPE operand was omitted from the command and CA NetMaster was unable to determine a default TCP/IP sockets interface to use.
option is the command option specified.
System Action:
The TCPIP command is ignored.
User Action:
Determine the correct TCP/IP sockets interface and reenter the TCPIP command, with the TYPE=type operand.
Reason:
This message is issued in response to a TCPIP command.
It indicates that the command could not be processed as a temporary storage shortage was encountered.
System Action:
The TCPIP command is ignored.
User Action:
Determine why a storage shortage condition exists.
Reason:
This message is issued in response to a TCPIP DEFINE command. It indicates that the command cannot be processed because a TCP/IP sockets interface is already defined with the same name specified by the NAME operand or selected by default.
name is the sockets interface name specified or selected by default.
System Action:
The TCPIP DEFINE command is ignored.
User Action:
Determine if the TCPIP DEFINE command is needed.
Reason:
This message is issued in response to a TCPIP command. It indicates that the command cannot be processed because the NAME operand specified a reserved name.
The fields are as follows:
System Action:
The TCPIP command is ignored.
User Action:
Correct the NAME operand and reenter the command.
Reason:
This message is issued in response to a TCPIP MODIFY command. It indicates that the command cannot be processed because an operand was specified that is allowed only when the TCP/IP sockets interface is inactive.
name is the name of the operand that is not allowed.
System Action:
The TCPIP MODIFY command is ignored.
User Action:
Use the TCPIP STOP command to stop the TCP/IP sockets interface, reissue the TCPIP MODIFY command, and then use the TCPIP START command to restart the TCP/IP sockets interface.
Reason:
This message is issued in response to a TCPIP command. It indicates that the command cannot be processed because the NAME operand was omitted and a primary TCP/IP sockets interface is not active.
option is the command option specified.
System Action:
The TCPIP command is ignored.
User Action:
Reissue the TCPIP command with the NAME=name operand.
Reason:
This message is issued in response to a TCPIP command. It indicates that the command cannot be processed because the NAME=ALL operand was specified but no TCP/IP sockets interfaces are defined.
option is the command option specified.
System Action:
The TCPIP command is ignored.
User Action:
Determine if the TCPIP command is needed.
Reason:
This message is issued in response to a TCPIP command. It indicates that the command cannot be processed because the TCP/IP sockets interface is not defined with the name specified by the NAME operand.
The fields are as follows:
System Action:
The TCPIP command is ignored.
User Action:
Correct the NAME operand and reenter the command.
Reason:
This message is issued in response to a TCPIP command. It indicates that the command cannot be processed because the NAME=ALL operand was specified but no TCP/IP sockets interfaces are active.
option is the command option specified.
System Action:
The TCPIP command is ignored.
User Action:
Determine if the TCPIP command is needed.
Reason:
This message is issued in response to a DNR command.
It indicates that the command has been processed.
'option' is the command option that was specified.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a DNR command with the PURGE operand.
count is the number of DNR cache entries deleted.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a DNR command with the STATIC operand. The fields are as follows:
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a DNR command.
It indicates that at least one of the TIMELIM, RETRY, and NS operands was specified, and that the calculated maximum time needed to query all name servers in turn (allowing for retries) exceeds the specified (or current) TIMELIM setting.
System Action:
This is a warning. The command is still processed and the requested values are set.
User Action:
You may wish to adjust the values of the TIMELIM and RETRY operands (taking into account the number of name servers) to be consistent.
For example, if you have 2 name servers (NS=(ns1,ns2)) and wish to have 2 retries, the first after 5 seconds, the second after 10, then you could specify:
DNR SET NS=(addr1,addr2) RETRY=(2,5,5,0)
(This assumes an additive delay. The last delay would be 15 seconds)
This means that for each name server, the resolver would issue sends as follows:
NS1 send 1 wait 5 seconds NS1 send 2 wait 10 seconds NS1 send 3 wait 15 seconds <start NS2 sends)
For each name server, this is a total of 30 seconds. With 2 name servers, the total required time to satisfy the RETRY specification would be 60 seconds.
If you specify (or currently have) a TIMELIM value less than 60, this message is issued in response to the DNR command as a warning. You may then decide to adjust either the TIMELIM value or the RETRY settings.
Reason:
This message is issued in response to a DNR command.
It indicates that the named operand is invalid.
'ooooo' is either DOMAIN or RETRY.
System Action:
The command is ignored.
User Action:
Correct the indicated operand and reissue the command.
Reason:
A DNR command is entered with an obsolete operand.
The P1 operand is obsolete and is ignored.
System Action:
The obsolete operand is ignored, and command processing continues.
User Action:
Remove the obsolete operand from the command string.
Reason:
The heading displayed in response to a SHOW DNR command. This information is used to determine the parameter settings of the SOLVE Domain Name Resolver (DNR). It also displays current statistics.
The current setting of the TCPIP START or MODIFY command DNR operand is shown (in the 'type' field). It will be VENDOR or SOLVE.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, displays various DNR parameter names and their current settings.
The following names are displayed:
DOMAIN The current setting of the DOMAIN operand, showing the domain suffix that will be applied to names with no fullstops.
MAXSTG The current setting of the MAXSTG operand, showing the maximum amount of storage that will be used for the DNR dynamic cache.
TIMELIM The current setting of the TIMELIM operand, showing the absolute time limit that will be applied to a DNR request.
CNRSP The current setting of the CNRSP operand, showing the time (in seconds) that the results of a request that received no answer (in the timeout period) will be cached.
CNFND The current setting of the CNFND operand, showing the time (in seconds) that the results of a request that was answered with no relevant information (and no cache timeout information) will be cached.
RETRY The current settings of the RETRY operand, will display as 'NO' or a list of 4 numbers, representing the retry count, initial timeout, additive timeout, and timeout multiplier.
TRACE The current settings of the TRACE operand.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW DNR command. The fields are as follows:
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, indicates that there are presently no name servers defined.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW DNR command. The fields are as follows:
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, indicates that DNR statistics follow.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command indicates that DNR request statistics follow.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, provides column headings for the following N3AW33 message.
Column meanings are:
TOT-RCVD The total number of requests received by the SOLVE DNR. GHBN The number of GetHostByName requests received. GHBA The number of GetHostByAddr requests received. NSLOOKUP The number of NSLOOKUP requests received. DNR- CTL The number of DNR control requests received.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, provides request statistics.
Refer to message N3AW32 for the meanings of each number.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, provides column headings for the following N3AW35 message.
Column meanings are:
FND-CACH The number of GetHostByName and GetHostByAddr requests that were satisfied from the cache. (%) The percentage of (total) requests that were satisfied from the cache.
ATTACH The number of new requests that were attached to an in-progress search.
NEW-SCH The number of new requests that caused a new search (that is, query to a name server) to be started. (NSLOOKUP requests always cause a new search; they are never cached and do not attach to in-progress requests).
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, provides request statistics.
Refer to message N3AW34 for column meanings.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, provides column headings for the following N3AW37 message.
Column meanings are:
TOT-CMPL The total number of requests that have completed. FOUND The total number of requests that completed with a 'found' result. TIMEOUT The total number of requests that completed with a 'timeout' result. N-FOUND The total number of requests that completed with a 'not found' result.
Note: These statistics include requests that were satisfied from the DNR cache. The cache will remember searches that timed out or received a not-found response.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, provides result statistics.
Refer to message N3AW36 for column descriptions.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, provides column headings for the following N3AW39 message.
Column meanings are:
BAD-NAME The total number of requests that were rejected because the supplied domain name was invalid.
OPN-ERR The total number of requests that were rejected because the DNR was unable to open a UDP socket.
SND-ERR The total number of requests that were rejected because a UDP SEND to a name server failed.
RCV-ERR The total number of requests that were rejected because a UDP RECEIVE failed.
STG- ERR The total number of requests that were rejected due to a storage shortage.
NNS- ERR The total number of requests that were rejected because the current DNR parameter settings did not provide any name server addresses.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, provides request statistics.
Refer to message N3AW38 for column descriptions.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, indicates that DNR cache statistics follow.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, provides column headings for the following N3AW42 messages.
Column meanings are:
TYPE The type of cache entries that this line applies to, either STATIC or DYNAMIC. COUNT The number of cache entries. STG (K) The number of Kbytes of storage currently used. ADDED The number of cache entries added. DELETED The number of cache entries deleted. DEL-T/O The number of cache entries deleted due to the entry time-to- live expiry (timeout). DEL-S/O The number of cache entries deleted due to the allowed cache storage limit being exceeded
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, provides cache statistics.
Refer to message N3AW41 for column headings.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, indicates that DNR I/O statistics follow.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command provides column headings for the following N3AW47 messages.
Column meanings are:
SENDS The number of UDP sends issued. S-ERRS The number of send errors. RECEIVES The number of UDP receives processed. R-ERRS The number of receive errors R-DISC The number of received buffers that were discarded due to format errors. R-NOMT The number of received buffers that were discarded because they could not be matched to any in-progress search requests (the request may have timed out).
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, provides I/O statistics.
Refer to message N3AW46 for column descriptions.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, indicates that DNR name server statistics follow.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command provides column headings for the following N3AW52 messages.
Column meanings are:
SERVER-ADDRESS—The IP address of a name server.
SENDS—The number of sends to the name server.
RESENDS—The number of resends to the name server.
RECEIVES—The number of receives from the name server.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command provides name server statistics.
For more information, see message N3AW51.
System Action:
None.
User Action:
None.
Reason:
This response message to a SHOW DNR command, indicates that DNR statistics could not be displayed, as the current TCP/IP interface is not using the SOLVE DNR (Domain Name Resolver).
System Action:
The command is ignored.
User Action:
None. DNR statistics are only available if using the SOLVE DNR.
Reason:
Execution of a TCP/IP request has failed. The fields are as follows:
request is the TCP/IP request that failed.
rc is the return code.
rsn is the reason code.
err is the error code as set by TCP/IP API.
pid is the process ID.
sid is the socket ID.
System Action:
APPC link manager terminates.
User Action:
Contact your technical support help desk.
Reason:
The address space could not allocate a TCP/IP subtask.
System Action:
APPC link manager terminates.
User Action:
Check system log for additional error messages.
Reason:
An attempt was made to establish a new connection by a remote system on a link that is already connected or local system does not allow connections from the remote address aaa.aaa.aaa.aaa .
bbbbbb is the remote system's APPC server port number.
System Action:
Session terminates.
User Action:
Check the link definitions of local and remote systems.
Reason:
This is a TCP/IP trace message. The fields are as follows:
P1 - TCP/IP request
P2 - Socket ID
P3 - Return code
P4 - Reason code
P5 - TCP/IP API error code
P6 - TCP/PI API vendor error information
P7 - Length of data in decimal
P8 - Length of data in hexadecimal
The message is logged if TCP/IP services have been started with the TRACE=YES, TRACE=ASCII, or TRACE=SUMMARY option, and a call has been made to the TCP/IP API that required data exchange on the connection.
System Action:
None.
User Action:
None.
Reason:
This is a TCP/IP datastream trace message containing the dump format of the data sent/received.
P1 - is the hexadecimal offset of the data
P2
P3
P4
P5 - are the hexadecimal dump of the data
P6 - is the character representation of the data
System Action:
None.
User Action:
None.
Reason:
This is a TCP/IP trace message. The fields are as follows:
P1 - TCP/IP request
P2 - Socket ID
P3 - Return code
P4 - Reason code
P5 - TCP/IP API error code
P6 - TCP/PI API vendor error information
The message is logged if TCP/IP services have been started with the TRACE=YES, TRACE=ASCII, or TRACE=SUMMARY option, and a call has been made to the TCP/IP API that required data exchange on the connection.
System Action:
None.
User Action:
None.
Reason:
This is a TCP/IP trace message. The fields are as follows:
P1 - TCP/IP request
P2 - Socket ID
P3 - Return code
P4 - Reason code
P5 - TCP/IP API error code
P6 - TCP/PI API vendor error information
P7 - Length of data in decimal
P8 - Length of data in hexadecimal
P9 - IP address of remote host
The message is logged if TCP/IP services have been started with the TRACE=YES, TRACE=ASCII, or TRACE=SUMMARY option, and a call to the TCP/IP API has been made that required data exchange on the connection.
System Action:
None.
User Action:
None.
Reason:
A TCP/IP sockets interface has been activated by the TCPIP START command.
The fields are as follows:
System Action:
None.
User Action:
None.
Reason:
Execution of a TCP/IP request has failed. The fields are as follows:
rc is the return code.
rsn is the reason code.
err is the error code as set by TCP/IP API.
System Action:
TCP/IP services are not available.
User Action:
Contact your technical support help desk.
Reason:
A TCP/IP sockets interface is automatically restarting after being stopped by a vendor stack shutdown (for example, TCP/IP started task termination).
The fields are as follows:
System Action:
The TCP/IP sockets interface attempts to restart.
User Action:
None.
Reason:
The TCP/IP sockets interface cannot be started by the TCPIP START command. A soft or retriable failure occurred (messages preceding this describe the error).
A retry occurs in the indicated interval. To stop retry, issue a TCPIP STOP command.
The fields are as follows:
System Action:
After the indicated interval, initialization of the TCP/IP sockets interface is retried.
User Action:
Determine the reasons for the failure and correct them if required.
Reason:
A TCP/IP sockets interface cannot be started by the TCPIP START command.
The fields are as follows:
Is the type of TCP/IP sockets interface.
Is the name assigned to the TCP/IP sockets interface.
Is the reason code associated with the failure.
Is the reason information associated with the failure.
The reason code and information is as follows:
Indicates that CA NetMaster is unable to load the named module for the indicated sockets interface type. Load error information is displayed.
Indicates that CA NetMaster is unable to attach the named sockets interface module. For more information, see the CA NetMaster log.
Indicates that the identified subtask abended or unexpectedly terminated. For more information, see the CA NetMaster log.
Indicates that the identified subtask cannot perform basic initialization.
Indicates that the identified subtask cannot perform subtask engine initialization. The RC values are as follows:
1: STQE eye-catcher invalid (internal error)
2: Engine already active (internal error)
3: Engine previously active (internal error)
4: No shared subpool available (internal error)
5: Initial GETMAIN failed
6: Initial ESTAE failed
7: 31 bit support not available
8: Caller not AMODE 31
9: FD WAIT support not available in this O/S
If a return code other than GETMAIN failure occurs, contact CA Support.
Indicates that the identified sockets interface module returned a non-zero return code.
Indicates that the identified sockets interface module cannot initialize. The message preceding this describes the specific problem.
Indicates that the identified sockets interface module returned an invalid information vector header.
Indicates that the identified sockets interface module returned an invalid information vector.
Indicates that the identified sockets interface module has errors in the returned capability list. For assistance, contact CA Support at http://ca.com/support.
Indicates that insufficient storage is available to complete initialization.
Indicates that an attempt to attach a required secondary subtask failed.
Indicates that a secondary subtask abended. For more information, see the CA NetMaster log.
Indicates that a secondary subtask failed to initialize. The codes (aa-bb) are as follows:
1-0: Unable to obtain storage
2-x: Internal initialization error
3-y: TCP/IP sockets interface initialization error. An additional message is displayed. y is the return code from the TCP/IP sockets interface.
Indicates that there is insufficient storage to obtain a pool of receive buffers.
System Action:
Initialization of the TCP/IP sockets interface fails.
User Action:
Determine the reasons for the failure and correct them if required.
Reason:
A TCP/IP sockets interface initialization was terminated by a TCPIP STOP command.
The fields are as follows:
System Action:
Initialization of the TCP/IP sockets interface stops.
User Action:
None.
Reason:
The TCP/IP sockets interface cannot determine the local host name. The value LOCALHOST is used to let the sockets interface initialize.
The fields are as follows:
System Action:
Initialization of the TCP/IP sockets interface completes.
User Action:
Determine why the correct host name is not available.
Reason:
A TCP/IP sockets interface cannot determine the local host IP address. The LOOPBACK address is used to let the sockets interface initialize.
The fields are as follows:
System Action:
Initialization of the TCP/IP sockets interface completes.
User Action:
Determine why the correct host address is not available.
Reason:
Execution of a TCP/IP request has failed. The fields are as follows:
request is the TCP/IP request that failed.
rc is the return code.
rsn is the reason code.
err is the error code as set by TCP/IP API.
pid is the process ID.
sid is the socket ID.
System Action:
INMC link manager terminates.
User Action:
Contact your technical support help desk.
Reason:
The address space could not allocate a TCP/IP subtask.
System Action:
INMC link manager terminates.
User Action:
Check system log for additional error messages.
Reason:
An attempt was made to establish a new connection by a remote system on a link that is already connected or local system does not allow connections from the remote address aaa.aaa.aaa.aaa .
bbbbbb is the remote system's INMC server port number.
System Action:
Session terminates.
User Action:
Check the link definitions of local and remote systems.
Reason:
A TCP/IP sockets interface enters shutdown.
The fields are as follows:
Valid values are:
An FSTOP or SHUTDOWN command has caused CA NetMaster to commence shutdown.
The TCP/IP vendor stack (interface/job/etc) has shut down or abended.
The CA NetMaster TCP/IP sockets interface subtask has ABENDED. For more information, see the log.
A TCPIP STOP command was entered
System Action:
The TCP/IP sockets interface enters shutdown.
User Action:
None.
Reason:
A TCP/IP sockets interface has shut down.
The fields are as follows:
System Action:
None.
User Action:
None.
Reason:
A socket open request has completed successfully. The UDP Port Number
P2 is now in use by the socket P1 .
System Action:
None.
User Action:
None.
Reason:
A socket open-raw request has completed successfully.
System Action:
None.
User Action:
None.
Reason:
A socket close request has completed successfully.
System Action:
None.
User Action:
None.
Reason:
A socket register request has completed successfully. The TCP Port Number P2 is now in use by the socket P1 .
System Action:
None.
User Action:
None.
Reason:
A socket accept request has completed successfully. The TCP Port Number
P2 has accepted a new TCP connection using local TCP port P4 . The peer host address is P3 .
System Action:
None.
User Action:
None.
Reason:
A socket connect request has completed successfully. The TCP Port Number
P2 is now connected to the peer host address P3 .
System Action:
None.
User Action:
None.
Reason:
This message is written to the SOLVE log only if TCP/IP tracing is enabled (Summary or Yes).
It is written when a SOCKET RECEIVE operation with a length prefix length of 1 to 4 has received sufficient data to analyze the length prefix value on the incoming data.
The socket ID, length prefix length (1 to 4), and length prefix value (from the incoming data) are displayed.
The incoming length prefix value is displayed in both decimal and hexadecimal notations.
System Action:
None.
User Action:
If the SOCKET RECEIVE does not complete, this message may show an expected length that is too long. SOLVE is waiting for more data but the sender is not sending it. This could indicate a problem with the length prefix length.
For example, if the SOCKET RECEIVE specified LENGTH=4, but the sender used LENGTH=3, and the length of the buffer was data (x'0400'), the 3-byte length prefix sent would be X'000400'. The receiver would receive X'000400??' (where ?? represents the first actual data byte) and expect a buffer approximately 240K bytes long. This may not be satisfied for quite a while!
Note: If an invalid length prefix is received, then this message is not produced. Messages N3BH90 and N3BH91 are produced instead.
Invalid length prefix values are 0, negative values (for LENGTH=4 only), or greater than 16,777,215.
Reason:
This message is written to the SOLVE log when a SOCKET RECEIVE operation fails due to a bad length prefix detected on incoming data.
The length prefix is 0, negative (for LENGTH=4 only), or greater than 16,777,215.
The socket ID, length prefix length (1 to 4), and length prefix value are shown.
Messages N3BH91 will follow, containing a dump of the received data.
System Action:
The SOCKET RECEIVE operation fails with a feedback code of 17.
User Action:
Check the prefix length specification on the SOCKET RECEIVE and the associated sending application SOCKET SEND (or equivalent).
You can examine the data by looking at the following N3BH91 messages.
Reason:
This message is written to the SOLVE log following an N3BH90 message. It contains a hexadecimal/character dump of the received data, up to 64 bytes.
System Action:
See the preceding message N3BH90.
User Action:
See the preceding message N3BH90.
Reason:
Execution of a TCP/IP request has failed. The fields are as follows:
request is the TCP/IP request that failed.
rc is the return code.
rsn is the reason code.
err is the error code as set by TCP/IP API.
pid is the process ID.
sid is the socket ID.
System Action:
INMC server terminates.
User Action:
Contact your technical support help desk.
Reason:
The address space could not allocate a TCP/IP subtask.
System Action:
INMC server terminates.
User Action:
Check system log for additional error messages.
Reason:
The INMC server has stopped. No further INMC TCP/IP connections are possible.
System Action:
Connect request to INMC server port are rejected.
User Action:
None.
Reason:
A SOCKET verb failed when attempting to assign data to an MDO.
xxxxxxxx - The session SOLVE primary APPL name.
aaaaaa - the TCP/IP IP address of the session.
ppp - the TCP/IP port of the session.
sss - the assigned socket number of the session.
rr - the socket return code (normally 8)
The most likely cause of an error is a TCPIP STOP or the other SOLVE region has terminated the connection.
System Action:
The SOCKET call is rejected.
User Action:
Check that the MDO specified is correct.
Reason:
A SOCKET verb specified an invalid IP address value.
xxxxxxxx - The session SOLVE primary APPL name.
aaaaaa - the TCP/IP IP address of the session.
pppp - the TCP/IP port of the session.
sss - the assigned socket number of the session.
rr - the socket return code (normally 8)
The most likely cause of an error is a TCPIP STOP or the other SOLVE region has terminated the connection.
System Action:
The SOCKET call is rejected.
User Action:
Check the IP address specified in the ADDRESS= operand.
Reason:
A SOCKET NSLOOKUP verb specified an invalid HOSTNAME value.
The hostname contains invalid characters or is not formatted correctly.
Hostnames must consist of the A-Z, 0-9, -, and . (fullstop) characters, and cannot have more than 63 characters between fullstops, and 2 adjacent fullstops are not permitted.
System Action:
The SOCKET call is rejected.
User Action:
Check the hostname specified in the HOSTNAME= operand.
Reason:
A SOCKET NSLOOKUP verb specified an invalid name server IP address value.
System Action:
The SOCKET call is rejected.
User Action:
Check the IP address specified in the NSADDRESS= operand.
Reason:
A SOCKET PING or SOCKET TRACEROUTE verb specified an invalid source IP address value.
System Action:
The SOCKET call is rejected.
User Action:
Correct the IP address specified in the SRCIP= operand.
Reason:
TAKEOVER=YES must be specified explicitly on a SOCKET REGISTER call if SERVER= and PATH= are also specified.
System Action:
The SOCKET call is rejected.
User Action:
Specify TAKEOVER=YES on the SOCKET REGISTER call.
Reason:
An attempt to open a raw TCP/IP socket to process SOCKET PING and SOCKET TRACEROUTE requests failed. The sockets interface name, protocol (RAW, ICMPV4, or ICMPV6), return code, reason code, errno, and vendor error information are shown.
System Action:
The current PING or TRACEROUTE request fails with an error.
User Action:
Examine the error codes and determine why the open failed. Often it is because the CA NetMaster region is not authorized to open RAW sockets.
For more information about the socket error code (ERRNO=eee), see the NCL Reference Guide.
For more information about the Vendor Error Code (VERRIN=xxx), see the appropriate TCP/IP error codes reference guide.
Reason:
A receive operation on a raw TCP/IP socket used to process SOCKET PING and SOCKET TRACEROUTE has failed. The sockets interface name, return code, reason code, errno, and vendor error information are shown.
System Action:
The current PING or TRACEROUTE request fails with an error.
User Action:
Examine the error codes and determine why the receive failed. It may be transient (for example, TCP/IP shutdown).
Reason:
A send operation on a raw TCP/IP socket used to process a SOCKET request has failed. The request type P1 can be PING or TRACEROUTE. The sockets interface name, return code, reason code, errno, vendor error and destination IP address information are shown.
System Action:
The current PING or TRACEROUTE request fails with an error.
User Action:
Examine the error codes and determine why the send failed. It may be transient (for example, TCPIP shutdown).
Reason:
This message is issued to the NetMaster log when the NetMaster DNR is tracing activity.
It is only issued if NetMaster DNR tracing is activated. This will only be done when requested by a NetMaster Support Engineer.
System Action:
None.
User Action:
Provide the trace information to Technical Support as requested.
Reason:
A socket request has failed for the CA NetMaster DNR socket. The request type, sockets interface name, return code, reason code, errno, and vendor error information are shown.
System Action:
DNR requests can be rejected (typically with a timeout error).
User Action:
Examine the error codes and determine why the request failed.
Reason:
This message is issued to the NetMaster log when an incoming message from a name server contains structural errors.
A description of the problem and the approximate offset in the message where the problem was found is shown.
System Action:
The message is discarded.
User Action:
Contact Technical Support.
Reason:
The CA NetMaster DNR is active and tracing activity.
System Action:
None.
User Action:
Provide the trace information to Technical Support as requested.
Reason:
This message is issued to the NetMaster log when the NetMaster DNR is tracing activity.
It is only issued if NetMaster DNR tracing is activated. This will only be done when requested by a NetMaster Support Engineer.
System Action:
None.
User Action:
Provide the trace information to Technical Support as requested.
Reason:
A UDP send has fails for the CA NetMaster DNR socket. The sockets interface name, return code, reason code, errno, and vendor error information are shown.
System Action:
DNR requests can be rejected with a send error.
User Action:
Examine the error codes and determine why the send failed.
Reason:
The CA NetMaster DNR is active and tracing activity.
System Action:
None.
User Action:
Provide the trace information to Technical Support as requested.
Reason:
This message is issued to the NetMaster log when the NetMaster DNR is tracing activity.
It is only issued if NetMaster DNR tracing is activated. This will only be done when requested by a NetMaster Support Engineer.
System Action:
None.
User Action:
Provide the trace information to Technical Support as requested.
Reason:
This message is issued to the NetMaster log when the NetMaster DNR is tracing activity.
It is only issued if NetMaster DNR tracing is activated. This will only be done when requested by a NetMaster Support Engineer.
System Action:
None.
User Action:
Provide the trace information to Technical Support as requested.
Reason:
This message is issued to the NetMaster log when the NetMaster DNR is tracing activity.
It is only issued if NetMaster DNR tracing is activated. This will only be done when requested by a NetMaster Support Engineer.
System Action:
None.
User Action:
Provide the trace information to Technical Support as requested.
Reason:
This message is issued to the NetMaster log when the NetMaster DNR is tracing activity.
It is only issued if NetMaster DNR tracing is activated. This will only be done when requested by a NetMaster Support Engineer.
System Action:
None.
User Action:
Provide the trace information to Technical Support as requested.
Reason:
This message is issued to the NetMaster log when the NetMaster DNR is tracing activity.
It is only issued if NetMaster DNR tracing is activated. This will only be done when requested by a NetMaster Support Engineer.
System Action:
None.
User Action:
Provide the trace information to Technical Support as requested.
Reason:
This message is issued to the NetMaster log when the NetMaster DNR is tracing activity.
It is only issued if NetMaster DNR tracing is activated. This will only be done when requested by a NetMaster Support Engineer.
System Action:
None.
User Action:
Provide the trace information to Technical Support as requested.
Reason:
This message is issued to the NetMaster log when the NetMaster DNR is tracing activity.
It is only issued if NetMaster DNR tracing is activated. This will only be done when requested by a NetMaster Support Engineer.
System Action:
None.
User Action:
Provide the trace information to Technical Support as requested.
Reason:
This diagnostic message is produced when System SSL errors are detected. P1 identifies the connection as it is known by the transport,
P2 identifies the connection as it is known by System SSL, P3 is the SSL call, P4 is the errno, and P5 is the character translation of the errno.
System Action:
Processing continues.
User Action:
None.
Reason:
This message is produced when tracing of errors detected by the Generic SSL Interface is requested. P1 identifies the connection as it is known by the transport, P2 identifies the connection as it is known by the SSL provider, and P3 is the error as classified by the Generic SSL Interface.
System Action:
Processing continues.
User Action:
None.
Reason:
This message is produced when tracing of buffers read from the SSL provider is requested. It is followed by message N3S203.
System Action:
Processing continues.
User Action:
None.
Reason:
This message is produced when tracing of buffers processed by the SSL provider is requested.
System Action:
Processing continues.
User Action:
None.
Reason:
This message is produced when tracing of buffers read from the SSL provider is requested. It indicates that an SSL READ operation failed.
System Action:
Processing continues.
User Action:
None.
Reason:
This message is produced when tracing of buffers written to the SSL provider is requested. It is followed by message N3S203.
System Action:
Processing continues.
User Action:
None.
Reason:
This message is produced when tracing of buffers written to the SSL provider is requested. It indicates that an SSL WRITE operation failed.
System Action:
Processing continues.
User Action:
None.
Reason:
This message is produced when tracing of SSL callback activity is requested. It indicates that a P1 callback request gave return code P2 .
System Action:
Processing continues.
User Action:
None.
Reason:
This message is produced when tracing of SSL callback activity is requested. It is followed by message N3S203.
System Action:
Processing continues.
User Action:
None.
Reason:
An attempt was made to add an SSL profile with a duplicate name.
System Action:
The SSL profile is not added.
User Action:
Choose another profile name.
Note: SSL profiles can be listed with the SHOW SSLPROF command.
Reason:
An attempt was made to delete an SSL profile that did not exist.
System Action:
The SSL profile is not deleted.
User Action:
Choose another profile name.
Note: SSL profiles can be listed with the SHOW SSLPROF command.
Reason:
An attempt was made to add an SSL profile with an invalid cipher specification.
System Action:
The SSL profile is not added.
User Action:
Correct the cipher specification and retry the operation.
Reason:
An attempt was made to add an SSL profile with a cipher specification that occurred more than once in a list.
System Action:
The SSL profile is not added.
User Action:
Correct the cipher specification and retry the operation.
Reason:
An attempt to add an SSL profile failed due to a shortage of storage.
System Action:
The SSL profile is not added.
User Action:
Make more storage available and retry the operation.
Reason:
An attempt was made to add an SSL certificate entry with a duplicate handle.
System Action:
The SSL certificate entry is not added.
User Action:
Choose another handle.
Note: SSL certificate entries can be listed with the SHOW SSLCERT command.
Reason:
An attempt was made to delete an SSL certificate entry that does not exist.
System Action:
The SSL certificate entry is not deleted.
User Action:
Choose another handle.
Note: SSL certificate entries can be listed with the SHOW SSLCERT command.
Reason:
An attempt to add an SSL certificate entry failed due to a shortage of storage.
System Action:
The SSL certificate entry is not added.
User Action:
Make more storage available and retry the operation.
Reason:
This is the first line of a two-line header, resulting from a SHOW SSL command.
System Action:
Processing continues.
User Action:
None.
Reason:
This is the second line of a two-line header, resulting from a SHOW SSL command.
System Action:
Processing continues.
User Action:
None.
Reason:
This is one of a set of detail lines, resulting from a SHOW SSL command.
System Action:
Processing continues.
User Action:
None.
Reason:
This is the first line of a two-line header, resulting from a SHOW SSLPROF command.
System Action:
Processing continues.
User Action:
None.
Reason:
This is the second line of a two-line header, resulting from a SHOW SSLPROF command.
System Action:
Processing continues.
User Action:
None.
Reason:
This is one of a set of detail lines, resulting from a SHOW SSLPROF command. Each profile entry consists of this message, followed by 0 or more N3S704 messages.
System Action:
Processing continues.
User Action:
None.
Reason:
This is one of a set of detail lines, resulting from a SHOW SSLPROF command. Each profile entry consists of an N3S703 message, followed by 0 or more occurrences of this message.
System Action:
Processing continues.
User Action:
None.
Reason:
This is the first line of a two-line header, resulting from a SHOW SSLCERT command.
System Action:
Processing continues.
User Action:
None.
Reason:
This is the second line of a two-line header, resulting from a SHOW SSLCERT command.
System Action:
Processing continues.
User Action:
None.
Reason:
This is one of a set of detail lines, resulting from a SHOW SSLCERT command.
System Action:
Processing continues.
User Action:
None.
Reason:
An invalid call was made to module NM0003U1. For a call to be valid, the first parameter must be either "INIT" or "GET".
System Action:
The call is rejected.
User Action:
Correct the code which calls NM0003U1.
Reason:
An attempt was made to call module T01PNSIP. The Link SVC returned an error response. (T01PNSIP is a utility module which is provided as a component of CA TCPaccess.
System Action:
The call fails.
User Action:
Ensure that T01PNSIP is available for use in your region by placing it in either the steplib or linklist.
Reason:
A Netstat command was issued to gather information from CA TCPaccess. A timeout occurred while waiting for a response to the command.
System Action:
The request for information from CA TCPaccess fails.
User Action:
Determine why CA TCPaccess cannot respond to the request.
Reason:
NM0003U1 attempted to issue a Netstat command to CA TCPaccess, but the interface module (T01PNSIP) returned an unrecognized return code.
System Action:
The call is rejected.
User Action:
Determine why T01PNSIP returned an unrecognized response. Correct the situation, and reissue the request.
Reason:
Module NM0003U1 was attempting cleanup after receiving information from CA TCPaccess. The cleanup call to the interface module (T01PNSIP) returned an unrecognized response.
System Action:
The call fails.
User Action:
Determine why the cleanup call to T01PNSIP failed. Correct the situation, and retry the call.
Reason:
A call was made to NM0003U1 to obtain information from CA TCPaccess. The second parameter of the call is the subsystem identifier that names the CA TCPaccess system to be queried. The SSID passed is invalid. To be valid, the SSID must be from one to four characters long.
System Action:
The call is rejected.
User Action:
Correct the code which calls NM0003U1, and retry the operation.
Reason:
A call was made to NM0003U1 to obtain information from CA TCPaccess. Not enough parameters were provided for NM0003U1 to return any information.
System Action:
The call fails.
User Action:
Amend the call to NM0003U1 to pass more parameters.
Reason:
A call was made to the $IPNETAX subsystem, using the old-format subsystem parameter list. $IPNETAX requires the use of the new-format parameter list.
System Action:
The call is rejected.
User Action:
Use the OCS command "SHOW SUBSYS=$IPNETAX" to diagnose the subsystem. The subsystem must be defined to use the new-format parameter list.
Reason:
The TCP/IP server has started. It identifies the server port being used and the assigned TCP/IP socket number.
System Action:
The TCP/IP server becomes available.
User Action:
None.
Reason:
The TCP/IP server is unable to start.
The likely cause is a port conflict. Other software on this system may be using the port (indicated by ERRNO 37 (EADDRINUSE)).
Other errors can be analyzed by referring to the return code (RC), feedback code (FB), and error number (ERRNO) of the SOCKET NCL verb. For more information, see the NCL Reference Guide.
This message is followed by an N3AE01 message that describes the error number in more detail.
System Action:
The TCP/IP server is unavailable.
User Action:
If the port number is already in use, change it using the SOCKETS parameter group.
Reason:
The TCP/IP server is unable to accept an incoming connection request.
This can occur when the connecting system closes the connection before it is complete or a storage shortage occurs.
This message is followed by an N3AE01 message that describes the error number in more detail.
System Action:
The connection is not accepted. The server stops accepting connections until TCP/IP is restarted.
User Action:
None.
Reason:
A new client has successfully completed initial negotiation.
The message shows the TCP/IP address and port of the client, and the allocated LUname and Telnet session type.
Session types are as follows:
NVT is a Network Virtual Terminal (a linemode session that appears as an LU1 terminal).
TN3270 is a standard TN3270 session.
TN3270E TERMINAL is a TN3270E terminal session.
TN3270E PRINTER is a TN3270E printer session (that appears as an LU1 printer).
System Action:
The session is connected.
User Action:
None.
Reason:
This message is displayed on a TN3270 or NVT session Telnet client when SOLVE has refused the session due to all generic terminals being in use.
System Action:
The connection is closed.
User Action:
None.
Reason:
This message is displayed on a TN3270 session Telnet client when SOLVE has refused the session. The session was refused because the requested terminal name was invalid or in use.
System Action:
The connection is closed.
User Action:
Check that the supplied terminal name is valid. The TNSPREFX and TNANYNAM sysparm settings are relevant.
Reason:
An error occurred during session negotiation. A description of the error is in the message.
System Action:
The connection closes.
User Action:
Contact Technical Support.
Reason:
This message is issued by the SOLVE Telnet Server connection processor when an error occurs during session negotiation.
A description of the error is in the message.
System Action:
The connection is closed.
User Action:
Report the error to your SOLVE support office.
Reason:
A TCP/IP error occurred during session negotiation. A description of the error and the return information from the TCP/IP request is shown.
System Action:
The connection closes.
User Action:
Contact Technical Support.
Reason:
This message is issued by the SOLVE Telnet Server connection processor following an N3Z480 message when the last received Telnet command was related to the error.
It is followed by a set of N3Z484 messages that show the received command.
System Action:
A dump of the command follows.
User Action:
Report the error to your SOLVE support office.
Reason:
This message is logged following an N3Z483 message and contains a dump of an incoming data buffer.
This message is logged, and precedes N3ZJ91 messages containing an incoming data buffer that may help diagnose the error.
System Action:
See N3Z483.
User Action:
See N3Z483.
Reason:
A TCP/IP error occurred. A description of the error and the return information from the TCP/IP request is shown.
System Action:
The connection closes.
User Action:
Ensure that the client did not close the connection.
Reason:
There is a storage shortage. The return information from the TCP/IP request is shown.
System Action:
The connection closes.
User Action:
None.
Reason:
Invalid input data from the Telnet client was detected.
It is followed by a dump of the buffer and the return information from the TCP/IP request.
System Action:
The connection closes.
User Action:
None.
Reason:
This message is logged following an N3Z682 message and contains a dump of a data buffer.
This message is logged, and precedes N3ZJ91 messages containing an incoming data buffer that may help diagnose the error.
System Action:
See N3Z682.
User Action:
See N3Z682.
Reason:
Invalid input data from a TN3270E Telnet client was detected.
It is followed by a dump of the buffer and the return information from the TCP/IP request.
System Action:
The connection closes.
User Action:
None.
Reason:
This message is logged following an N3Z684 message and contains a dump of a data buffer.
This message is logged, and precedes N3ZJ91 messages containing an incoming data buffer that may help diagnose the error.
System Action:
See N3Z684.
User Action:
See N3Z684.
Reason:
An attempt to modify a TCP/IP Telnet sysparm was made when the TCP/IP interface was active.
Some of these sysparms can be altered only when the TCPIP interface is not active.
System Action:
The command is ignored.
User Action:
Issue TCPIP STOP, alter the sysparm, then issue TCPIP START.
Reason:
This message is issued during input message processing for terminals and INMC/APPC sessions that are using the TCP/IP access method.
It indicates that no storage was available for the input data.
System Action:
The session is terminated.
User Action:
Determine why the storage shortage occurred.
Reason:
This message is issued during an incoming connect request for a session using the TCP/IP access method.
It indicates that the incoming connect failed.
The fields in the message are:
xxxxxxxx - The incoming SOLVE primary APPL name.
aaaaaa - the TCP/IP IP address of the incoming request
pppp - the TCP/IP port of the incoming request
sss - the assigned socket number of the incoming request
rrrrrrr - the failure reason:
STORAGE SHORTAGE - a storage shortage has occurred
REJECTED - the request was rejected, for example no LINK START or DEFLINK matched the request.
System Action:
The session is refused.
User Action:
For storage shortages, determine why the storage shortage occurred.
For rejections, check the current DEFLINK and LINK requests.
Reason:
This message is issued when a TCP/IP send on a TCPIP access method session fails.
The fields in the message are:
xxxxxxxx - The session SOLVE primary APPL name.
aaaaaa - The TCP/IP IP address of the session.
pppp - The TCP/IP port of the session.
sss - The assigned socket number of the session.
rr - The socket return code (normally 8)
ff - The socket feedback (see the NCL SOCKET verb &ZFDBK values)
ee - The socket errno (see the NCL SOCKET verb &ZSOCERRN values)
The most likely cause of this error is a TCPIP STOP or the other SOLVE domain has terminated the connection.
System Action:
The session is closed.
User Action:
Use the feedback and errno values to determine the cause of the failure and take appropriate corrective action.
Reason:
This message is issued when a TCP/IP receive on a TCP/IP access method session fails.
The fields in the message are:
Is the session primary APPL name.
Is the TCP/IP IP address of the session.
Is the TCP/IP port of the session.
Is the assigned socket number of the session.
Is the socket return code (typically 8)
The most likely cause of the error is a TCPIP STOP or the other region has terminated the connection.
System Action:
The session is closed.
User Action:
Check that the other region has not closed the connection.
Reason:
This message is issued when a TCP/IP RECEIVE on a TCP/IP access method fails.
Are the IP address and port number of the peer.
Is the assigned socket number of the session.
Is the socket return code.
Is the socket feedback code.
Is the socket ERRNO value.
The most likely cause of an error is a TCPIP STOP or the other domain has terminated the connection.
System Action:
The session is closed.
User Action:
Check that the remote domain has not closed the connection.
Reason:
This message is issued when a TCP/IP RECEIVE on a TCP/IP access method times out.
aaaaaa:pppp are the IP address and port number of the peer
xxxxxxxx - The session SOLVE primary APPL name.
aaaaaa - The TCP/IP IP address of the session.
pppp - The TCP/IP port of the session.
sss - The assigned socket number of the session.
rr - The socket return code (normally 8)
The most likely causes of an error are a TCPIP STOP or the other SOLVE domain has terminated the connection.
System Action:
The session is closed.
User Action:
Check that the remote SOLVE domain has not closed the connection.
Reason:
Invalid data is detected from an initial RECEIVE.
aaaaaa:pppp are the IP address and port number of the peer
rrr describes the reason the data is considered invalid
xxxxxxxx - The session region primary APPL name.
aaaaaa - The TCP/IP IP address of the session.
pppp - The TCP/IP port of the session.
sss - The assigned socket number of the session.
rr - The socket return code (normally 8).
Likely causes of the an error are:
- A TCPIP STOP command has been issued
- A connected region has terminated the connection
System Action:
The session is closed.
User Action:
Contact Technical Support and quote the message number and reason code.
Reason:
The target LU to log on to is incorrect.
aaaaaa:pppp are the IP address and port number of the peer.
tttttttt is the target specified by the logon request.
eeeeeeee is the lu of the system issuing the message.
xxxxxxxx - The session SOLVE primary APPL name.
aaaaaa - The TCP/IP IP address of the session.
pppp - The TCP/IP port of the session.
sss - The assigned socket number of the session.
rr - The socket return code (normally 8).
Likely causes of an error are:
- A TCPIP STOP command has been issued
- The other SOLVE domain has terminated the connection
System Action:
The session is refused.
User Action:
Check the luname specified in the preceding DOMAIN DEFINE for the link.
Reason:
This message is issued when a TCP/IP send on a TCP/IP access method session fails.
The fields in the message are:
xxxxxxxx - The session SOLVE primary APPL name.
aaaaaa - The TCP/IP IP address of the session.
pppp - The TCP/IP port of the session.
sss - The assigned socket number of the session.
rr - The socket return code (normally 8).
The most likely causes of the error are a TCPIP STOP or that the other SOLVE domain has terminated the connection.
System Action:
The session is closed.
User Action:
Check that the other SOLVE domain has not closed the connection.
Reason:
An incoming TCP/IP connection through a proxy server is not defined in the domain table.
p1 identifies the TCP/IP IP address of the peer.
p2 identifies the TCP/IP port of the peer.
p3 is the socket number assigned to the incoming connection.
System Action:
The session is closed.
User Action:
Issue a DOMAIN DEFINE command to define the peer with proxy information.
Reason:
This message is issued when an attempt to connect to another SOLVE system using the TCP/IP access method fails.
It indicates that the incoming connect failed.
The fields in the message are:
xxxxxxxx - The incoming SOLVE primary APPL name.
rrrrrrr - the failure reason:
IP AM NOT INITIALIZED
The TCP/IP access method is not active, for example no TCPIP START has been issued, or no IPAMPORT has been set.
CANNOT CONNECT TO SELF
A request to connect to the same SOLVE system was received.
STORAGE SHORTAGE (1)
An internal storage shortage occurred.
STORAGE SHORTAGE (2)
An internal storage shortage occurred.
INTERNAL REJECT (1)
An internal error occurred.
INTERNAL REJECT (2)
An internal error occurred.
xxxxxxxx FAILED RC=rr FB=ff E=eee
The named SOCKET request failed with the displayed return code, feedback, and errno.
xxxxxxxx SCHED FAILED RC=rr
the named SOCKET request schedule failed with the displayed return code.
INIT. RECEIVE TIMED OUT 60 seconds.
BAD RSP BUF, REAS=xx
The initial response buffer was invalid. Reasons are:
01 - buffer too short
02 - invalid eyecatcher
03 - length mismatch
04 - invalid response code
REFUSED, SENSE: ssxx
The target SOLVE system refused the connection with the indicated (SNA) sense code.
CANCELLED DURING LOGON
The connect request was cancelled by this system during processing.
System Action:
The connection is not started.
User Action:
Examine the reason. Common causes are having a wrong DOMAIN definition table entry (wrong IP address/port), or the target system not accepting the request due to no LINK START or DEFLINK in effect.
Reason:
This message is issued when a TCP/IP send on a TCPIP access method session fails due to a storage shortage.
System Action:
The session is closed.
User Action:
Determine the cause of the storage shortage.
Reason:
This message is issued when a TCP/IP send on a TCPIP access method session fails.
System Action:
The session is closed.
User Action:
The most likely reason for the send failing is either a TCPIP STOP command being issued or the other SOLVE system closing the connection.
Thus there is normally no specific action to take.
Reason:
This message is issued when an attempt to connect to another SOLVE system using the TCP/IP access method fails.
It indicates that the incoming connect failed.
The fields in the message are:
xxxxxxxx - The incoming SOLVE primary APPL name.
rrrrrrr - the failure reason:
TCP/IP ACCESS METHOD NOT ACTIVE
The TCP/IP access method is not active, for example no TCPIP START has been issued, or no IPAMPORT has been set.
NO DOMAIN DEF FOR xxxxxxxx
there is no defined DOMAIN table entry for the requested target.
The DOMAIN DEFINE command can be used to define the target name and TCP/IP address/port information.
DOMAIN DEF FOR xxxxxxxx HAS NO TCPIP INFO
there is a defined DOMAIN table entry for the requested target, however the entry has no TCP/IP address/port information.
The DOMAIN DEFINE command can be used to update the target name and TCP/IP address/port information.
CONNECT TIMED OUT
The TCPIP CONNECT did not complete within 60 seconds.
RECEIVE TIMED OUT
The TCPIP RECEIVE did not complete within 60 seconds.
PEER CLOSED CONNECTION
The target system closed the connection.
STORAGE SHORTAGE (1)
xxxxxxxx FAILED RC=rr FB=ff E=eee
The named SOCKET request failed with the displayed return code, feedback, and errno.
xxxxxxxx SCHEDULE FAILED RC=rr
the named SOCKET request schedule failed with the displayed return code.
PROTOCOL ERROR xx, SEE LOG
The initial handshake encountered a protocol error. The SOLVE log will contain additional messages. The codes are:
1 - unexpected data received
2 - unexpected TELNET command received
3 - received 2nd DO TN3270E
4 - received 2nd DO TERMTYPE
5 - received 2nd SEND TERMTYPE
6 - received TERMTYPE IS, not yet sent
7 - received TERMTYPE IS, invalid length
8 - received TERMTYPE IS, invalid name
9 - received TERMTYPE IS, invalid num2
10 - received TELNET command too long
System Action:
The connection is not started.
User Action:
Examine the reason. Common causes are having a wrong DOMAIN definition table entry (wrong IP address/port), or the target system not accepting the request due to no LINK START or DEFLINK in effect.
Reason:
This message is issued to all SOLVE Monitor status users when an attempt to connect to another SOLVE system using the TCP/IP access method fails.
It indicates the failure was related to DOMAIN definitions.
The fields in the message are:
xxxxxxxx - The incoming SOLVE primary APPL name.
rrrrrrr - the failure reason:
NO DOMAIN TABLE ENTRY FOUND
there is no defined DOMAIN table entry for the requested target.
The DOMAIN DEFINE command can be used to define the target name and TCP/IP address/port information.
DOMAIN TABLE ENTRY HAS NO TCPIP INFORMATION
there is a defined DOMAIN table entry for the requested target, however the entry has no TCP/IP address/port information.
The DOMAIN DEFINE command can be used to update the target name and TCP/IP address/port information.
System Action:
The connection is not started.
User Action:
Correct the Domain table entries as required, using the DOMAIN DEFINE or DOMAIN REPLACE commands.
Reason:
An attempt to connect to another region using the TCP/IP access method fails.
xxxxxxxx identifies the region.
rrrrrr is the reason.
Note: For more information about the reason, see the help for the N3ZJ01 message.
This message is followed by N3ZJ91 messages that display the incoming data buffers, which can help you diagnose the problem.
System Action:
See N3ZJ01.
User Action:
See N3ZJ01.
Reason:
This message follows an N3ZJ90 message and contains the dump of an incoming data buffer.
System Action:
See N3ZJ01.
User Action:
See N3ZJ01.
Reason:
A send failure has occurred. A description of the error is in the message..
System Action:
The connection closes.
User Action:
Determine why the send failed. It is likely that the TCP/IP connection was closed or broken.
Reason:
An error occurred while preparing or sending an outbound data buffer to a Telnet client.
The info field in the message contains one of the following reasons:
A storage shortage was encountered during processing.
A buffer overflow occurred during message reformatting.
A TCP/IP SEND error occurred.
System Action:
The connection closes.
User Action:
Determine the reason. If the SEND failed, it is likely that the client closed the connection.
Reason:
An error occurred while sending a heartbeat message to a Telnet Client.
System Action:
The connection closes.
User Action:
Probably none. It is likely that the client closed the connection or that the client has become unreachable due to a network problem.
Reason:
This message is issued by the SOLVE Telnet Server when a TN3270E session client user presses the SYSREQ key. The client has been switched into SYSREQ mode.
System Action:
SOLVE waits for input.
User Action:
Press SYSREQ again to resume the SOLVE Telnet session. Type LOGOFF and press the ENTER key to terminate the session.
Reason:
This message is issued by the SOLVE Telnet Server when a TN3270E session is in SYSREQ mode. Input from the client was not valid.
System Action:
SOLVE waits for more input.
User Action:
Press SYSREQ again to resume the SOLVE Telnet session. Type LOGOFF and press the ENTER key to terminate the session.
Reason:
An error occurred while sending SSCP-LU data (SYSREQ mode) to a Telnet client.
System Action:
The connection closes.
User Action:
Probably none. It is likely that the client closed the connection or that the client has become unreachable due to a network problem.
Reason:
This message is issued following a successful TNCTL ADDPORT, DEFPORT, REPORT, or DELPPORT command.
System Action:
The command was processed successfully.
User Action:
Rejoice!
Reason:
This message is issued following a TNCTL ADDPORT, DEFPORT, or REPPORT command, if the port number used in the command is the same port number presently set by the SYSPARMS IPPORT command.
Port numbers used by the TELNET server must be different from the port number used by the SOLVE shared port server.
To set up a TELNET definition for the shared port, use the TNCTL xxxPORT=SHARED command.
System Action:
The command is ignored.
User Action:
Correct the port number and reissue the command.
Reason:
This message is issued following a TNCTL ADDPORT or DEFPORT command. The port number in the command is already defined as a TELNET port.
System Action:
The command is ignored.
User Action:
Correct the port number and reissue the command.
Reason:
This message is issued following a TNCTL DELPORT command. The port number in the command is not defined as a TELNET port.
System Action:
The command is ignored.
User Action:
Correct the port number and reissue the command.
Reason:
This message is issued if an entered TNCTL command has the TEDSS operand specified.
This operand is not obsolete. The operand is ignored.
System Action:
The command was processed successfully.
User Action:
remove the TEDSS operand from the command.
Reason:
This message is a heading message for the output from the SHOW TNCTL command. This command displays currently defined TELNET server ports. The column headings refer to following N3ZS20 messages.
The column headings are:
PORT The port number. If a definition currently exists for the shared server port, the port number field for that definition says SHARED.
NVT The NVT option (YES or NO)
ANY The ANYNAME option (YES or NO)
EAS The EASINET option (YES or NO)
TLS The TLS option (YES or NO)
APPL The APPL name (or '-' if none is set)
T-E The TN3270E option (YES or NO)
BI The TEOPTS BIND option (Y or N)
RS The TEOPTS RESPONSE option (Y or N)
SR The TEOPTS SYSREQ option (Y or N)
TM The TEOPTS TERMINAL option (Y or N)
PR The TEOPTS PRINTER option (Y or N)
SC The TEOPTS SCSCTL option (Y or N)
DS The TEOPTS DSCTL option (Y or N)
EJ The TEOPTS EOJ option (Y or N)
System Action:
None
User Action:
None
Reason:
This message is a heading message for the output from the SHOW TNCTL command. This command displays currently defined TELNET server ports. This heading relates to following N3ZS21 messages.
The column headings are:
T/O Whether or not a takeover of an apparently lost TCP/IP connection is allowed
TM Whether or not timing marks will be sent on TELNET sessions using this port
TMINT The timing mark interval This will be (interval,count) or DEFAULT, meaning that the SYSPARMS TNDTMINT value will be used
System Action:
None
User Action:
None
Reason:
This message is a heading message for the output from the SHOW TNCTL command. This command displays currently defined TELNET server ports. This heading relates to following N3ZS22 messages.
The column headings are:
COMMENT If a comment was specified on the TNCTL command, the comment text.
System Action:
None
User Action:
None
Reason:
This message provides information on a defined TELNET server port. Refer to message N3ZS10 for column headings.
System Action:
None
User Action:
None
Reason:
This message provides information on a defined TELNET server port. Refer to message N3ZS11 for column headings.
System Action:
None
User Action:
None
Reason:
This message provides information on a defined TELNET server port. Refer to message N3ZS12 for column headings.
System Action:
None
User Action:
None
Reason:
This message is a heading message for the output from the SHOW TELNET command. This command displays currently-connected Telnet sessions. The column headings refer to the following N3ZS50 messages:
Is the assigned Logical Unit Name.
Note: This is not a VTAM-defined name.
Is the Telnet session type:
Indicates whether this session is signed on to CA NetMaster with the NET/MASTER User ID.
Indicates whether the session is a secure session using SSL.
Is the local port (as defined by the TNCTL command) that this session is using.
Is the port being used by the Telnet client for this session.
Is the Telnet client TCP/IP Address.
System Action:
None.
User Action:
None.
Reason:
This message is a detail message for the output from the SHOW TELNET command. Each line contains details about a Telnet session. For column headings and explanations, see message N3ZS50.
System Action:
None.
User Action:
None.
Reason:
This message is written to the SOLVE log when a TELNET server port is defined and opened. It indicates the port number and socket number.
System Action:
None
User Action:
None
Reason:
This message is written to the SOLVE log when a TELNET server port error occurs.
The following error information is logged. (Note that if a specific piece of information is not available, a '-' is displayed.)
Port number (ppp) Error description (eee) Socket number (S#=sss) Socket operation return code (RC=rrr) Socket operation feedback code (FB=fff) Socket operation error number (E#=nnn) Socket operation vendor information (VI=iii)
System Action:
The socket is closed if it was opened. If a failure occurs during open, the open is retried after a few seconds.
User Action:
Check the error information against the SOLVE socket error code tables and take corrective action if relevant.
Reason:
This message is written to the SOLVE log when a TELNET server port error occurs. It follows a previous N3ZT80 message that provides error diagnostics.
System Action:
The socket is closed.
User Action:
Check the error information from the preceding N3ZT80 message against the SOLVE socket error code tables and take corrective action if relevant.
Reason:
SOLVE was unable to load module NM001002.
System Action:
FTS will be unavailable.
User Action:
Refer this problem to your systems administrator for resolution. Until the problem is resolved and SOLVE restarted, FTS will be unavailable.
Reason:
An attempt has been made to access the FTS panels by a user not authorized for FTS.
System Action:
The request is rejected.
User Action:
Refer to your systems administrator.
Reason:
An unauthorized user issued the PROFILE FTSMSG command. This command allows a user that is authorized to receive FTS messages to determine whether or not he wishes to receive messages relating to FTS. The user that has issued this command is not authorized to receive FTS messages and therefore may not use this command.
System Action:
The command is rejected.
User Action:
Refer to your Systems Administrator. You need to enter Y in the File Transmission Services field in the UAMS definition of your User ID or the Group ID if specified.
Reason:
This message is issued in response to the PROFILE command.
System Action:
None.
User Action:
None.
Reason:
The SYSPARMS operand entered is supported in DOS/VSE system only.
System Action:
The command is rejected.
User Action:
None.
Reason:
An invalid selection was entered.
System Action:
The request is rejected.
User Action:
Enter a valid selection.
Reason:
The name of the required INMC destination (remote SOLVE system) must be entered.
System Action:
The request is rejected.
User Action:
Enter the required name.
Reason:
Any changes made to the initiator set for the destination destname have been actioned and are now in effect.
System Action:
None.
User Action:
None.
Reason:
The specified destination is not active (no INMC link) or FTS is not yet available at that destination.
System Action:
The request is rejected.
User Action:
Determine why the destination is not active or why FTS is not yet available.
Reason:
Your request could not be completed due to a lack of storage.
System Action:
The request fails.
User Action:
Retry the request. If it continues to fail increase the region size.
Reason:
This message is issued on completion of a "list destinations" function. It is for information only.
System Action:
None.
User Action:
None.
Reason:
The name entered has invalid syntax.
System Action:
The input is rejected.
User Action:
Correct the field containing the cursor.
Reason:
The field containing the cursor is invalid or out of range.
System Action:
The input is rejected.
User Action:
Correct the field and re-enter.
Reason:
No initiators have transmission classes specified. A minimum of one initiator must be specified.
System Action:
The input is rejected.
User Action:
Enter transmission classes for one or more initiators.
Reason:
The initiator containing the cursor has been specified with duplicate classes. Classes in the range A to Z can be specified in any order. However, each class can only be specified once.
System Action:
The input is rejected.
User Action:
Correct the classes.
Reason:
The specified destination is not licensed for the FTS feature and cannot therefore be used to receive or transmit datasets.
System Action:
The input is rejected.
User Action:
Refer to your systems administrator.
Reason:
An attempt to modify an outbound transmission request has been rejected because no request of that name exists.
System Action:
The request is ignored.
User Action:
None. If the request is associated with a transmission that has already completed, termination processing will have automatically deleted the request, unless the need for operator response was specified in the transmission definition.
Reason:
An attempt to modify an inbound transmission request has been rejected because no request of that name exists.
System Action:
The request is ignored.
User Action:
None. If the request is associated with a transmission that has already completed, termination processing will have automatically deleted the request, unless the need for operator response was specified in the transmission definition.
Reason:
This is an information message only, advising that no changes were made to the request.
System Action:
None.
User Action:
Ensure that no changes were intended.
Reason:
During the period between when the transmission request was displayed and when the action was taken to invoke changes, the transmission request was deleted and no longer exists. It may have been deleted by another user or it may have been deleted automatically by termination processing, following successful completion of the transmission.
System Action:
None.
User Action:
Ensure that the request has completed successfully and has not been incorrectly deleted by another user.
Reason:
An error has occurred on the FTS VSAM database, known as VFS. This might indicate that the VFS dataset is corrupt. The code X'nn' is the VSAM RPL return code.
System Action:
The request fails.
User Action:
Determine the type of error and if possible correct it. Refer this error to your systems administrator. If necessary restore the FTS database from the most recent backup.
Reason:
The user has attempted to perform an FTS function for which their userid does not have the specified SYSTEM, PRIVATE or ANY privilege.
System Action:
The request is rejected.
User Action:
Refer to your systems administrator.
Reason:
The request to access the transmission request or definition has been rejected because the user's access mask mmmmmmmmmmm does not allow access to the specified SYSTEM or PRIVATE definition.
System Action:
The request is rejected.
User Action:
None.
Reason:
You are not authorized for the requested function.
System Action:
The request is rejected.
User Action:
Refer to your systems administrator.
Reason:
TRANSMIT command authorization could not be performed, because no userid was associated with the request. Possibly the request was sourced from EASINET.
System Action:
The request is rejected.
User Action:
None.
Reason:
Internal security check for user userid failed. The specified reason was returned from the security subsystem.
System Action:
The request is rejected.
User Action:
Refer to your systems administrator.
Reason:
A TRANSMIT command has been issued, but no transmission request name has been specified.
System Action:
The request is rejected.
User Action:
Re-enter the TRANSMIT command specifying the names of one or more transmission definitions.
Reason:
A TRANSMIT command has specified an incorrect transmission request name.
System Action:
The request is rejected.
User Action:
Re-enter the request correctly.
Reason:
A TRANSMIT command has failed due to a lack of storage.
System Action:
The request has failed.
User Action:
Retry the request and if necessary increase the region size.
Reason:
An attempt to request a transmission has failed due to a lack of storage.
System Action:
The request fails.
User Action:
Retry the request. If necessary increase the region size.
Reason:
A request to invoke transmission definition defname has failed because the definition does not exist.
System Action:
None.
User Action:
Enter a correct definition name.
Reason:
A transmission request has been accepted. However, the link to the destination specified in the transmission definition is not currently active and the request has been queued pending activation of the link.
System Action:
The request is stored on the FTS database and will be automatically invoked when the link to the nominated destination becomes active and a transmission initiator of the appropriate class becomes available.
User Action:
No further action is required. The transmission will commence when the link becomes active.
Reason:
The transmission request defname has been accepted and the link to the destination specified in the transmission definition is active.
System Action:
The transmission will commence as soon as a transmission initiator of the appropriate class becomes available.
User Action:
None.
Reason:
An error has occurred on the FTS VSAM database known as VFS. This may indicate that the VFS dataset has been corrupted. The code X`nn' is the VSAM RPL return code.
System Action:
The request fails.
User Action:
Determine the type of error and if possible correct it. Refer this error to your systems administrator. If necessary restore the FTS database from the most recent backup.
Reason:
An attempt to request a transmission has been rejected because a previous request of the same name already exists. A transmission request name must be unique.
System Action:
The request is rejected and the existing request remains.
User Action:
Determine why a previous request is still available for transmission.
Reason:
An attempt to request a transmission has failed because the VFS dataset which contains the FTS database is full. When a transmission request is made, both the transmission request and a copy of the original transmission definition and written to the FTS database.
System Action:
The request is rejected.
User Action:
This situation must be quickly remedied. The VFS dataset is used by other system components and may result in further failures. In addition, no transmissions will be received if insufficient space remains in the dataset. Either delete unwanted items from the dataset, or take an immediate backup and increase the space allocation for the VFS VSAM dataset.
Reason:
An attempt to request a transmission has failed because a previous request, which has completed transmission, requires acknowledgement by the operator. A transmission can be defined as requiring acknowledgement at either the transmitting or receiving host. If this option is selected the transmission request is not automatically deleted and must be deleted (acknowledged) by the operator from the Transmission Supervision panel. Until this is done no further request of the same name will be accepted.
System Action:
The request is rejected.
User Action:
Determine why the previous request has not been acknowledged and, if you are authorized, proceed with the acknowledgement and then re-request the rejected transmission.
Reason:
An attempt to request a transmission has failed because a previous request, of the same name, which has failed during transmission requires corrective action by the operator. Until the reason for the failure of the previous request is corrected and the request removed from IN ERROR status so that it may resume and complete transmission, or until the request in error is deleted, no further request of the same name will be accepted.
System Action:
The request is rejected.
User Action:
Determine why the previous request failed and if possible have the transmission restarted or delete the request; then re-issue the rejected transmission request. It should be noted that changes made to a transmission definition will only be invoked when a new transmission request is made, as a copy of the definition is taken at that time.
Reason:
The heading line of the SHOW FTS display. Further detail lines follow this heading and line up underneath the categories shown. The meaning of each category is as follows:
Dest Is the name of the remote region from/to which the data set is being transmitted.
Request Is the name of the transmission request.
Cl Is the class of the transmission.
Block Count Is the number of blocks read from/written to the data set so far.
Char Count Is the number of characters read from/written to the data set so far.
Elap-Time Is the elapsed transmission time regardless of restarts.
System Action:
None.
User Action:
None.
Reason:
This message forms part of the SHOW FTS display:
P1 displays the INMC link name of the other region.
P2 displays the contact state of the FTS link with the other region.
P3 displays the status of the initiators.
P4 displays the activity of FTS transmissions on this link.
System Action:
None.
User Action:
None.
Reason:
Part of the SHOW FTS display. Indicates whether subsequent display lines apply to inbound or outbound transmissions.
System Action:
None.
User Action:
None.
Reason:
This message forms part of the SHOW FTS display. The fields in this line contain information about outbound transmissions and line up underneath the heading line, message N42601. For further information, see the description of that message.
System Action:
None.
User Action:
None.
Reason:
This message forms part of the SHOW FTS display. The fields in this line contain information about inbound transmissions and line up underneath the heading line, message N42601. For further information, see the description of that message.
System Action:
None.
User Action:
None.
Reason:
This message is in response to a SHOW FTS STATUS=status command when there are no links currently in the specified status ( P1 ).
System Action:
None.
User Action:
None.
Reason:
An invalid operand P1 was specified on the SHOW FTS command.
System Action:
The command is rejected.
User Action:
Correct the error and retry.
Reason:
Indicates the end of the SHOW FTS display.
System Action:
None.
User Action:
None.
Reason:
There are no links active and consequently there are no datasets being transmitted.
System Action:
None.
User Action:
None.
Reason:
This is a heading line for a SHOW FTS STATUS=status display. Refer to message N42601 for explanation of the fields in the heading.
System Action:
None.
User Action:
Refer to N42601 for detailed information.
Reason:
The heading line of the SHOW FTS INIT display. Further detail lines follow this heading and line up underneath the categories shown. The meaning of each category is as follows:
Init Displays the number that identifies the initiator (1-16).
Classes Displays the request classes serviced by this initiator. The order in which the classes are listed is the order in which work is allocated to the initiator.
Started Displays whether the initiator is started.
Com Displays the compression level for the initiator.
Hi-Pr Displays the high or normal transmission priority.
Status Displays the current status of the initiator (IDLE, active with named request, or draining named request).
System Action:
None.
User Action:
None.
Reason:
This message forms part of the SHOW FTS INIT display. The fields in this line contain information about initiators and line up underneath the heading line, message N42611. For further information, see the description of that message.
System Action:
None.
User Action:
None.
Reason:
This message forms part of the SHOW FTS INIT display.
The receive limit ( P1 ) is the number of concurrent inbound transmissions that this region will accept from the remote region.
The transmit limit ( P2 ) is the number of concurrent transmissions from this region that will be accepted by the remote region.
System Action:
None.
User Action:
None.
Reason:
The specified destination is not active (no INMC link) or FTS is not yet available at that destination.
System Action:
The request is rejected.
User Action:
None.
Reason:
When defining a user's FTS privilege, the user has been authorized for either SYSTEM or PRIVATE definitions. However, the associated access mask has not been defined.
System Action:
The update is rejected.
User Action:
Enter the required access mask.
Reason:
The field containing the cursor has been entered with imbedded blanks where no imbedded blanks are allowed.
System Action:
The request is rejected.
User Action:
Correct the field.
Reason:
The field containing the cursor has been entered with an invalid value.
System Action:
The request is rejected.
User Action:
Correct the field.
Reason:
The field containing the cursor has been omitted. Its entry is mandatory.
System Action:
The request is rejected.
User Action:
Enter the field.
Reason:
The installation's security exit has supplied an invalid value for the structured field with the key nnnn.
System Action:
The message is logged and the structured field is ignored. Processing of other structured fields continues.
User Action:
Refer the message to your systems administrator. Ensure that the security exit always returns valid data for the structured field.
Reason:
An attempt to modify a transmission request using the FTSMOD command has failed because no request of that name exists.
System Action:
The command is rejected.
User Action:
Check the request name. If the request is associated with a transmission that may have already completed, the request will have been automatically deleted by termination processing, unless the transmission definition specified that operator acknowledgement was required.
Reason:
This message indicates the successful completion of an FTSMOD command. Transmission request defname has been actioned as requested.
System Action:
The action may be: HELD the transmission is now in HOLD status. ELIGIBLE FOR RESTART the `in-error' indicator for the transmission has been reset and the request is available for scheduling (unless it is HELD). RELEASED the transmission has been released from hold status. WILL BE COLDSTARTED the transmission is available for rescheduling. The transmission will start over from the beginning.
User Action:
None.
Reason:
An error has occurred on the FTS VSAM database known as VFS. This may indicate that the VFS dataset has been corrupted. The code X`nn' is the VSAM RPL return code.
System Action:
The request fails.
User Action:
Determine the type of error and if possible correct it. Refer this error to your systems administrator. If necessary restore the FTS database from the most recent backup.
Reason:
Insufficient storage was available to obtain FTS records from the VFS database. The FTS facility has been disabled for destination destname.
System Action:
FTS activity to that destination will not be possible.
User Action:
This condition can only be rectified by breaking and restarting the link to the other SOLVE system. This can be done using the LINK command. It should be noted that a storage shortage at this point in FTS processing is likely to lead to later failures and an increase in the region size is recommended.
Reason:
The link to destination destname has been interrupted and FTS processing has been suspended. This message will be accompanied by other messages associated with individual transmissions that may have been in progress when the link interruption occurred.
System Action:
The link will be monitored and FTS processing will resume when the link is re-established.
User Action:
Determine the reason for the link failure and rectify if possible.
Reason:
FTS has established contact with destination destname. Other factors may still prevent the actual transmission or receipt of data. These include the actual enabling of FTS on the Initiator Supervision panel, the setting of the inbound file limit and the availability of active initiators.
System Action:
Transmission will commence if no other factors remain to restrict such activity.
User Action:
None.
Reason:
During the contact process FTS has determined that the FTS system in destination destname is incompatible with this system and further processing cannot proceed.
System Action:
FTS is not available.
User Action:
Refer to your systems administrator.
Reason:
During the contact process FTS has determined that the data compression component of destination destname is incompatible with this system and data compression cannot be performed on files transmitted between the two systems.
System Action:
Dataset transmissions will proceed normally but data compression will not be performed.
User Action:
Refer to your systems administrator.
Reason:
The user has attempted to reset the IN-ERROR status of a transmission. However, the request is not IN-ERROR.
System Action:
None.
User Action:
If using a transmission supervision panel, correct the field or action. If using the FTSMOD command, check the current status of the transmission. If it is ACTIVE, restart can be achieved by HOLDing the request, then doing a RELEASE COLD=YES.
Reason:
This message is issued when FTS is instructed to HOLD an active request.
System Action:
The transmission will be interrupted and the request placed in HOLD status. To resume transmission the request will require operator intervention to remove it from HOLD status. It should be noted that there may be a slight delay from the time this message is issued and the actual suspension of processing of the transmission. This delay will vary depending on system load and the priority of the initiator in which the transmission is running. The request will show a failure reason of `INTERRUPTED BY OPERATOR'.
User Action:
Release the request when transmission is to resume.
Reason:
An information only message, informing the user that no changes were made to the request. This may be because the transmission request was already in the required status. For example, attempting to restart a completed request.
System Action:
None.
User Action:
Ensure that no changes were intended.
Reason:
An invalid attempt to change an active transmission has been received. If you are using the transmission supervision panel, the field where the cursor is positioned cannot be changed for an active request. Actions such as deleting a request or changing its class require that the request first be interrupted and placed in HOLD status.
System Action:
The request is rejected.
User Action:
If you wish to proceed with the change you must first HOLD the transmission. This must be followed by a separate request for the change you require.
Reason:
The process of changing the class of a request requires multiple updates to the FTS database. An error has been detected during this processing.
System Action:
The status of the request may be in doubt.
User Action:
Validate the request to ensure that the required status has been achieved. Monitor this transmission to ensure that it successfully commences and completes. Notify your systems administrator of this error.
Reason:
An error has occurred on the FTS VSAM database known as VFS. This may indicate that the VFS dataset has been corrupted. The code X`nn' is the VSAM RPL return code and will be described in your installation's VSAM programmer guide.
System Action:
The request fails.
User Action:
Determine the type of error and if possible correct it. Refer this error to your systems administrator. If necessary restore the FTS database from the most recent backup.
Reason:
Confirms that transmission request defname has been deleted. The copy of the transmission definition that was taken when the transmission request was made has also been deleted.
System Action:
None.
User Action:
If the request was deleted so that a subsequent new request could be issued to invoke changes to the transmission definition, then this request can now proceed. Any transmission request issued from this point will take a new copy of the transmission definition.
Reason:
Transmission request defname has been acknowledged. This message is issued as the result of an FTSMOD ACK= or FTSMOD DEL= command, or an ACK/DELETE request from the transmission supervision panel. The status of the transmission request was COMPLETE, and the original transmission definition was defined as requiring acknowledgement after successful transmission.
System Action:
The request and associated copy of the transmission definition are deleted.
User Action:
The process of acknowledging the completion of a transmission request is similar to deletion processing. Both the transmission request and its copy of the transmission definition are deleted. A subsequent transmission request of the same name can now be issued. Any subsequent request will take a new copy of the transmission definition at the time the request is made.
Reason:
An attempt to delete or acknowledge an inbound transmission has failed because the transmission is currently in progress.
System Action:
The request is rejected.
User Action:
An inbound transmission request can only be deleted or acknowledged when it is in READY or COMPLETED status. It is not possible to interrupt an inbound transmission from the receiving host. The control of a transmission rests with the transmitting operator, who has the ability to interrupt the transmission if necessary.
Reason:
An attempt to cancel an inbound transmission has been rejected because the request is not currently in progress.
System Action:
The request is rejected.
User Action:
None.
Reason:
An error has occurred on the FTS VSAM database known as VFS. This may indicate that the VFS dataset has been corrupted. The code X`nn' is the VSAM RPL return code.
System Action:
The request fails.
User Action:
Determine the type of error and if possible correct it. Refer this error to your systems administrator. If necessary restore the FTS database from the most recent backup.
Reason:
Issued in response to a request to delete an inbound request. All associated records are removed from the FTS database at the receiving host.
System Action:
None.
User Action:
None.
Reason:
Issued in response to a request to delete or acknowledge the transmission of an inbound request, when that request is found to be in COMPLETED status. The request is acknowledged and any associated records are deleted from the FTS database.
System Action:
None.
User Action:
None. The receipt of another request with the same request name is now possible.
Reason:
A request to cancel the specified transmission has been accepted.
System Action:
None.
User Action:
None.
Reason:
An FTSINIT command specified a new set of classes for an initiator, but the set of classes was invalid. Classes must be in the range A to Z and can be specified in any order. However, each class can only be specified once.
System Action:
The command is rejected.
User Action:
Correct the CLASS operand and reenter.
Reason:
This message indicates the successful completion of an FTSINIT command. Any changes made to the initiator set for the destination have been actioned and are now in effect.
System Action:
None.
User Action:
None.
Reason:
The specified destination is not licensed for the FTS feature and cannot therefore be used to receive or transmit datasets.
System Action:
The input is rejected.
User Action:
Refer to your systems administrator.
Reason:
The specified destination is not active (no INMC link) or FTS is not yet available at that destination.
System Action:
The request is rejected.
User Action:
Determine why the destination is not active or why FTS is not yet available.
Reason:
The SOLVE you are logged onto may only use FTS to transfer files to or from NMPC systems. The destination you have attempted to modify is a host SOLVE system. FTS is not available to host destinations.
System Action:
The input is rejected.
User Action:
Choose a NMPC destination or refer to your systems administrator.
Reason:
A SH XMIT DIRECTION=INBOUND command has been issued, specifying a CLASS= parameter. The CLASS parameter is only valid when displaying outbound transmissions.
System Action:
The command is rejected.
User Action:
Correct the command and reissue.
Reason:
The heading line of the SHOW XMIT display. Further detail lines will follow this heading, each line describing a transmission request. The meaning of each label is as follows:
DEFINITION the name of the transmission.
DIR the direction of the transmission: inbound (I) or outbound (O). DEST/ORIGIN the destination system for outbound transmissions, or the origin for inbound transmissions.
CL the class of the transmission (outbound only).
STATUS the transmission's current status: READY, ACTIVE, FAILED, HELD or COMPLETED.
TERMINATION MESSAGE the first part of the error message for a failed transmission, or the completion statistics for a completed transmission awaiting acknowledgement.
System Action:
None.
User Action:
None.
Reason:
Part of the SHOW XMIT display. Fields in this line contain information about a transmission request, and line up underneath the heading line, message N43B01. See the description of that message for further information.
System Action:
None.
User Action:
None.
Reason:
An error has occurred on the FTS VSAM database known as VFS. This may indicate that the VFS dataset has been corrupted. The code X'nn' is the VSAM RPL return code.
System Action:
The request fails.
User Action:
Determine the type of error and if possible correct it. Refer this error to your systems administrator. If necessary restore the VFS database from the most recent backup.
Reason:
The first line of the SHOW XMIT=reqname display, for an outgoing transmission. It shows the name of the transmission selected for display (reqname), its destination (dest) and the class of the transmission (c).
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an outgoing transmission. It shows the userid who issued the transmission request, and the date and time the request was issued.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an outgoing transmission. It shows the current status of the request (ACTIVE, FAILED etc.) and the date and time at which the request started executing.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an outgoing transmission. It shows the date and time at which the request last stopped executing.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an outgoing transmission. It shows the completion message (or failure message) for the request.
System Action:
None.
User Action:
Refer to the explanation of the completion message for more details.
Reason:
A line of the SHOW XMIT=reqname display, for an outgoing transmission. It shows the name of the dataset being transmitted, or the name of the DD statement(MVS), FILEDEF(VM), or DLBL/TLBL(VSE) which points to the dataset being transmitted.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an outgoing transmission. It shows the name of the remote dataset receiving the transmitted data, or the name of the DD statement(MVS), FILEDEF(VM), or TLBL/DLBL(VSE) on the remote SOLVE system which points at the receiving dataset.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an outgoing transmission. It shows the SOLVE command to be executed on successful completion of the transmission.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an outgoing transmission. It shows the name of a subsequent transmission which will be automatically executed on successful completion of this transmission.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an outgoing transmission. It shows the SOLVE command to be executed at the receiving end, on successful completion of this transmission.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an outgoing transmission. It shows the checkpoint information which will be used to reposition the request for restarting. The checkpoint information listed is the count of physical blocks transmitted from the sending file, at the time of the last two checkpoints for the request.
System Action:
None.
User Action:
None.
Reason:
An attempt to display a transmission request using the SH XMIT command has failed because no request of that name exists.
System Action:
The request is ignored.
User Action:
None. If the request is associated with a transmission that may have already completed, the request will have been automatically deleted by termination processing unless the transmission definition specified that operator acknowledgement was required.
Reason:
An error has occurred on the FTS VSAM database known as VFS. This may indicate that the VFS dataset has been corrupted. The code X'nn' is the VSAM RPL return code.
System Action:
The request fails.
User Action:
Determine the type of error and if possible correct it. Refer this error to your systems administrator. If necessary restore the VFS database from the most recent backup.
Reason:
The first line of the SHOW XMIT=reqname display, for an incoming transmission. It shows the name of the transmission selected for display (reqname) , and the name of the origin system sending the transmission (orig) .
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an incoming transmission. It shows the remote userid who issued the transmission request, and the date and time the request was issued at the remote system.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an incoming transmission. It shows the current status of the request (ACTIVE, FAILED etc.) and the date and time at which the request started executing.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an incoming transmission. It shows the date and time at which the request last stopped executing.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an incoming transmission. It shows the completion message (or failure message) for the request.
System Action:
None.
User Action:
Refer to the explanation of the completion message for more details.
Reason:
A line of the SHOW XMIT=reqname display, for an incoming transmission. It shows the name of the dataset being transmitted, or the name of the DD statement(MVS), FILEDEF(VM), or DLBL/TLBL(VSE) on the transmitting system which points to the dataset being sent.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an incoming transmission. It shows the name or dataset receiving the transmitted data, or the name of the DD statement(MVS), FILEDEF(VM), or TLBL/DLBL(VSE) which points at the dataset to receive the data.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an incoming transmission. It shows the SOLVE command to be executed at the sending end, on successful completion of the transmission.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an incoming transmission. It shows the name of a subsequent transmission which will be automatically executed at the remote system when this transmission terminates successfully.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an incoming transmission. It shows the SOLVE command to be executed on this system, on successful completion of the transmission.
System Action:
None.
User Action:
None.
Reason:
A line of the SHOW XMIT=reqname display, for an incoming transmission. It shows the checkpoint information which will be used to reposition the request for restarting. The checkpoint information listed is the count of physical blocks transmitted from the sending file, at the time of the last two checkpoints for the request.
System Action:
None.
User Action:
None.
Reason:
An attempt to display an incoming transmission request using the SH XMIT command has failed because no request of that name exists.
System Action:
The request is ignored.
User Action:
None. If the request is associated with a transmission that may have already completed, the request will have been automatically deleted by termination processing unless the transmission definition specified that operator acknowledgement was required.
Reason:
An error has occurred on the FTS VSAM database known as VFS. This may indicate that the VFS dataset has been corrupted. The code X'nn' is the VSAM RPL return code.
System Action:
The request fails.
User Action:
Determine the type of error and if possible correct it. Refer this error to your systems administrator. If necessary restore the VFS database from the most recent backup.
Reason:
Issued to FTS authorized users when a transmission is started. defname is the request name, destname is the destination to which the transmission is being made. hh.mm.ss is the current time and c is the class of the request.
System Action:
The transmission proceeds.
User Action:
None.
Reason:
Issued to FTS authorized users when a transmission is restarted following an earlier interruption. The request defname is being transmitted to destination destname and the restart has taken place from the block bbbb within the dataset.
System Action:
The transmission resumes.
User Action:
None.
Reason:
Issued following the successful completion of transmission request defname to destination destname. The current time is hh.mm.ss and the request was processed as class c.
System Action:
None.
User Action:
None.
Reason:
This message indicates the successful completion of a transmission. The statistics show the values:
Is the number of blocks transmitted.
Is the number of characters in the data set.
Is the elapsed time of the transmission.
The value is the length of time that is taken to transmit the number of bytes shown, regardless of any restarts that have taken place. The time does not include delays that are associated with allocations or mount operations. For small data sets, the displayed elapsed time can be zero because the transmission completed in less than one second.
Is the effective transmission rate.
The value is the rate of data transfer for this request, expressed in kilobits per second. When multiple requests are being transmitted to the same destination, the effective data transfer rate for each individual request is lower than when a single request is being transmitted because the multiple requests are competing for use of the physical network bandwidth available between the two systems.
Note: The transmission rate can appear disproportionately low for small data sets because of elapsed time rounding effects and other overheads that are associated with the transmission.
Note: If the data was compressed, the effective transmission rate is calculated using the number of characters that are transmitted after compression.
Is the achieved data compression if the data was compressed during the transmission. The effective rate of compression is expressed as the average percentage by which the data was compressed before transmission: the higher the percentage, the greater the level of the compression.
Is the request name.
If a counter overflow condition prevents calculation of the transmission and compression rates, these fields are set to N/A in the completion message.
System Action:
None.
User Action:
If this message is accompanied by a message stating that the request must be acknowledged, use the Transmission Supervision panel to acknowledge the request. Another request of the same name is then permitted.
Reason:
Issued when a transmission request is interrupted or fails for any reason. This message will be followed by message N44304 giving the reason for the interruption or failure.
System Action:
The request will be placed in error status and will require operator intervention before transmission can resume.
User Action:
Determine the cause of the interruption and if necessary take corrective action and restart the request.
Reason:
This message follows message N44303 and supplies the request completion code and description associated with a failing request. lll is LOC or REM, where LOC indicates that the source of the error is the local system and REM indicates that the source of the error is the remote system. cc is the completion reason code. xxxxxxxxxxxxxxxxxxxxx is a description of the reason for the error or interruption. This information is also saved on the FTS database and is available for problem analysis from the Transmission Supervision panels.
System Action:
The transmission of this request has been suspended pending corrective action by the operator.
User Action:
Use the lll-cc completion code information to determine the cause of the error. If lll is LOC, action is required from this system. If lll is REM, action is required at the remote destination. lll is always LOC for link failures or interruptions. If the cause of the failure is a link interruption, no action may be necessary. However, if the transmission definition was specified with AUTO-RESTART=N, the request is placed in HOLD status and requires operator action before transmission resumes.
Reason:
This message is issued following the successful completion of transmission when the transmission definition was specified as requiring operator acknowledgement of successful transmission. No further transmission of the same name will be possible until this transmission has been acknowledged.
System Action:
None.
User Action:
This transmission must be acknowledged by use of the Transmission Supervision panels and entry of a Y in the ACK/DELETE field. The process of acknowledging a transmission deletes associated records from the FTS database making it possible to issue another transmission request of the same name.
Reason:
This message is issued to alert the operator that a potential abnormal condition has been detected and further investigation may be required. The text of this message will be one of the following:
INPUT DATASET WAS CLASSIFIED UNMOVABLE
The transmission definition has specified a dataset that was classified as unmovable. This is normally because it was defined with the U option as a part of the dataset organisation (DSORG). FTS will proceed with the transmission. However, the unmovable attribute will not be retained on the output dataset.
TRANSMITTED DATASET WAS EMPTY
The transmitted dataset contained 0 blocks of data. This may be a valid situation where regular transmissions are run against datasets that may not contain information on certain occasions. You should verify that this is valid on this occasion.
INPUT PDS MEMBER NOT EMPTIED ON COMPLETION
A member of a partitioned dataset was successfully transmitted. However, the transmission definition requested that the input dataset be emptied following the transmission. This option cannot be honoured as the system regards the deletion of a member of a PDS as an integrity exposure. The member will not be deleted and independent means must be used to delete the member if required.
System Action:
Processing continues.
User Action:
Verify that the alerted condition is acceptable. If not, take corrective action.
Reason:
If the SYSPARMS FTSTRDSN=YES command has been issued, this message will be generated to indicate the name of the dataset just transmitted.
wwww is PRIVATE or SYSTEM, indicating the classification of the transmission, xxxx is the transmission request name, yyyy is the name of the dataset transmitted, and zzzz is the name of the member transmitted in the case of a partitioned dataset.
System Action:
None.
User Action:
This message may be intercepted by LOGPROC and dynamically built JCL submitted to the internal reader to perform processing dependent upon successful transmission of the file.
Reason:
Issued when an FTS request specifies either GROUP or USERDATA.
System Action:
None.
User Action:
This message may be intercepted by LOGPROC for further processing.
Reason:
Following completion of the file transmission defname, the request indicated that the FTS definition by that name should be deleted. This was attempted but failed with the VSAM feedback code xx shown in the message.
System Action:
None.
User Action:
None.
Reason:
Following completion of the file transmission defname, the request indicated that the FTS definition by that name should be deleted. This message indicates that the deletion has been successful.
System Action:
None.
User Action:
None.
Reason:
Following completion of the file transmission defname, the request indicated that the FTS definition by that name should be deleted. Before deleting the record FTS determined that the definition had been updated since the original transmission request. As this indicates that the definition may still be in use the deletion request is ignored.
System Action:
The deletion request is ignored.
User Action:
Delete the definition from the FTS definition maintenance options if necessary.
Reason:
A chained transmission request was found following completion of the file transmission indicated by previous messages in the log. The FTS definition defname, specified in the chained transmission request field of the previous request, is queued for transmission.
System Action:
An implicit TRANSMIT defname command is executed.
User Action:
None.
Reason:
The definition for the transmission just completed specified 'EMPTY INPUT=Y', indicating that the transmitting dataset should be emptied on successful termination of the transmission. The transmission ended successfully, but the attempt to empty the dataset failed. Emptying is done by opening the dataset for output, then closing it. The process fails if an error occurs on the open.
System Action:
The transmission continues to terminate normally.
User Action:
Investigate why the empty process failed. If necessary, empty the dataset manually.
Reason:
This message is issued at the receiving host to indicate that an inbound transmission is commencing. The request reqname is being transmitted from the host origin . The current time is hh.mm.ss. Note that there is no class associated with the receipt of a transmission.
System Action:
None.
User Action:
None.
Reason:
This message is issued at the receiving host to indicate that a previously interrupted transmission is being restarted from block bbbb. The request name is reqname and is being transmitted from host origin.
System Action:
None.
User Action:
None.
Reason:
This message is issued to indicate successful completion of the receipt of transmission request reqname from host origin . hh.mm.ss is the current time.
System Action:
This message will be followed by message N44802.
User Action:
None.
Reason:
This message indicates the successful completion of a transmission. The statistics show the values:
Is the number of blocks transmitted.
Is the number of characters in the data set.
Is the elapsed time of the transmission.
The value is the length of time that is taken to transmit the number of bytes shown, regardless of any restarts that have taken place. The time does not include delays that are associated with allocations or mount operations. For small data sets, the displayed elapsed time can be zero because the transmission completed in less than one second.
Is the effective transmission rate.
The value is the rate of data transfer for this request, expressed in kilobits per second. When multiple requests are being transmitted to the same destination, the effective data transfer rate for each individual request is lower than when a single request is being transmitted because the multiple requests are competing for use of the physical network bandwidth available between the two systems.
Note: The transmission rate can appear disproportionately low for small data sets because of elapsed time rounding effects and other overheads that are associated with the transmission.
Note: If the data was compressed, the effective transmission rate is calculated using the number of characters that are transmitted after compression.
Is the achieved data compression if the data was compressed during the transmission. The effective rate of compression is expressed as the average percentage by which the data was compressed before transmission: the higher the percentage, the greater the level of the compression.
Is the request name.
If a counter overflow condition prevents calculation of the transmission and compression rates, these fields are set to N/A in the completion message.
System Action:
None.
User Action:
None.
Reason:
This message is issued when the receipt of a transmission fails or is interrupted. This message will be followed by message N44804 giving a reason for the failure.
System Action:
Processing of the request is suspended pending operator intervention.
User Action:
Determine the reason for the failure and if necessary correct the problem and notify the transmitting operator to restart the transmission. If you display an inbound transmission request that has failed, it will always show a status of READY. This is because the aspects of control of a transmission always rest with the transmitting host, which will have also been notified of the failure reason. At the transmitting host the request will have been placed in IN ERROR status and must be released by operator action. Having corrected the problem, you should notify the transmitting operator to remove the request from IN ERROR status to allow a restart to take place.
Reason:
This message follows message N44803 and supplies the request completion code and description associated with a failing request. lll will be either LOC or REM, where LOC indicates that the source of the error is the local SOLVE system and REM indicates that the source of the error is the remote SOLVE system. cc is the completion reason code explained in the FTS Request Completion Codes chapter of the SOLVE Initilisation Messages and Abend Codes manual. xxxxxxxxxxxxxxxxxxxxx is a description of the reason for the error or interruption. This information will also be saved on the FTS database and will be available for problem analysis from the Transmission Supervision panels.
System Action:
The transmission of this request has been suspended pending corrective action by the operator.
User Action:
Use the lll-cc completion code information to determine the cause of the error. If lll is LOC then action will be required from this system. If
lll is REM then action will be required by the transmitting host. lll will always be LOC for link failures or interruptions. If the cause of the failure was a link interruption then no action may be necessary. However, if the transmission definition was specified with AUTO- RESTART=N then the request will have been placed in HOLD status and will require operator action before transmission can resume. It must be noted that the control of the request, and hence the ability to restart it following an error, rests with the transmitting operator. If you require a failed request to be restarted, then you must inform the transmitting operator to do so.
Reason:
This message is issued following the successful receipt of a transmission when the transmission definition was specified as requiring operator acknowledgement at the receiving system. No further receipt of a transmission of the same name will be possible until this transmission has been acknowledged.
System Action:
None.
User Action:
The receipt of this transmission must be acknowledged by use of the Transmission Supervision panels to display the inbound transmission and entry of a Y in the ACK/DELETE field. The process of acknowledging a transmission deletes associated records from the FTS database making it possible to receive another transmission request of the same name.
Reason:
This message is issued to alert the operator that a potential abnormal condition has been detected and further investigation may be required. The text of this message will be one of the following:
INPUT DATASET WAS CLASSIFIED UNMOVABLE
The transmission definition has specified a dataset that was classified as unmovable. This is normally because it was defined with the U option as a part of the dataset organisation (DSORG). FTS will proceed with the transmission. However, the unmovable attribute will not be retained on the output dataset.
TRANSMITTED DATASET WAS EMPTY
The transmitted dataset contained 0 blocks of data. This may be a valid situation where regular transmissions are run against datasets that may not contain information on certain occasions. You should verify that this is valid on this occasion.
INPUT PDS MEMBER NOT EMPTIED ON COMPLETION
A member of a partitioned dataset was successfully transmitted. However, the transmission definition requested that the input dataset be emptied following the transmission. This option cannot be honoured as the system regards the deletion of a member of a PDS as an integrity exposure. The member will not be deleted and independent means must be used to delete the member if required.
System Action:
Processing continues.
User Action:
Verify that the alerted condition is acceptable. If not, take corrective action.
Reason:
If the SYSPARMS FTSRCDSN=YES command has been issued, this message will be generated to indicate the target of the transmission.
wwww is either SYSTEM or PRIVATE to indicate the classification of the transmission and xxxx is the transmission request name. If the transmission took place to a dataset, yyyy is the name of the dataset. In addition, if the transmission took place to a member of a partitioned dataset, zzzz is the member name. If the transmission took place directly into spool, c is the SYSOUT class.
System Action:
None.
User Action:
This message may be intercepted by LOGPROC and dynamically built JCL submitted to the internal reader to process the dataset just received.
Reason:
Issued when an FTS request specifies either GROUP or USERDATA.
System Action:
None.
User Action:
This may be intercepted by LOGPROC for further processing.
Reason:
This message indicates that an I/O error has occurred on a dataset involved in a transmission. It includes the error information returned from a SYNADAF macro issued in a SYNAD exit. The meaning of the various fields of the message can be found in the appropriate data management macros manual for your operating system. This message is accompanied by other messages that indicate which transmission request has failed.
System Action:
The request will be placed in error status and will require operator intervention before transmission can resume.
User Action:
Determine the cause of the error. If the error is unrecoverable, delete the request, otherwise correct the error condition and reset the request `in error' status to retry.
Reason:
This message indicates that an I/O error has occurred on a dataset involved in a transmission. It includes the error information returned from a SYNADAF macro issued in a SYNAD exit. The meaning of the various fields of the message can be found in the appropriate data management macros manual for your operating system. This message is accompanied by other messages that indicate which transmission request has failed.
System Action:
The request will be placed in error status and will require operator intervention before transmission can resume.
User Action:
Determine the cause of the error. If the error is unrecoverable, delete the request, otherwise correct the error condition and reset the request 'in error' status to retry.
Reason:
An error has occurred on an FTS transmission for the given reason, while attempting to reposition to the TTR shown.
System Action:
The request will be placed in error status and will require operator intervention before transmission can resume.
User Action:
Determine the cause of the error. If the error is unrecoverable, delete the request, otherwise correct the error condition and reset the request 'in error' status to retry.
Reason:
This message indicates that an I/O error has occurred on a dataset involved in a transmission. It includes the error information returned in the CCB located in the file DTF. The meaning of the various fields of the message can be found in the appropriate data management macros manual for your operating system. This message is accompanied by other messages that indicate which transmission request has failed.
System Action:
The request will be placed in error status and will require operator intervention before transmission can resume.
User Action:
Determine the cause of the error. If the error is unrecoverable, delete the request, otherwise correct the error condition and reset the request 'in error' status to retry.
Reason:
This message indicates that an I/O error has occurred on a dataset involved in a transmission. It includes the error information returned from a SYNADAF macro issued in a SYNAD exit. The meaning of the various fields of the message can be found in the appropriate data management macros manual for your operating system. This message is accompanied by other messages that indicate which transmission request has failed.
System Action:
The request will be placed in error status and will require operator intervention before transmission can resume.
User Action:
Determine the cause of the error. If the error is unrecoverable, delete the request, otherwise correct the error condition and reset the request 'in error' status to retry.
Reason:
This message indicates that an I/O error has occurred on a dataset involved in a transmission. It includes the error information returned from a SYNADAF macro issued in a SYNAD exit. The meaning of the various fields of the message can be found in the appropriate data management macros manual for your operating system. This message is accompanied by other messages that indicate which transmission request has failed.
System Action:
The request will be placed in error status and will require operator intervention before transmission can resume.
User Action:
Determine the cause of the error. If the error is unrecoverable, delete the request, otherwise correct the error condition and reset the request `in error' status to retry.
Reason:
An error has occurred on an FTS transmission for the given reason, while attempting to reposition to the TTR shown.
System Action:
The request will be placed in error status and will require operator intervention before transmission can resume.
User Action:
Determine the cause of the error. If the error is unrecoverable, delete the request, otherwise correct the error condition and reset the request 'in error' status to retry.
Reason:
This message indicates that an I/O error has occurred on a dataset involved in a transmission. It includes the error information returned in the CCB located in the file DTF. The meaning of the various fields of the message can be found in the appropriate data management macros manual for your operating system. This message is accompanied by other messages that indicate which transmission request has failed.
System Action:
The request will be placed in error status and will require operator intervention before transmission can resume.
User Action:
Determine the cause of the error. If the error is unrecoverable, delete the request, otherwise correct the error condition and reset the request 'in error' status to retry.
Reason:
A different process has already registered the application specified on an &SNAMS REGISTER request.
System Action:
The request is rejected.
User Action:
Use the SHOW SNAMS APPL command to display registered applications. Retry the request with a different application name.
Reason:
The application and/or routing names supplied on a SNAMS registration request conflicts with an existing registration.
System Action:
The request is rejected.
User Action:
Use the SHOW SNAMS APPL command to display registered applications.
Reason:
The application name or registration ID supplied is invalid.
System Action:
The request is rejected.
User Action:
Use the SHOW SNAMS APPL command to display registered applications. Retry the request with a different application name or ID.
Reason:
The NCL notification exit address supplied to $NMSNAMS conflicts with the existing registration.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
Either the data supplied is not an MDS-MU, or some vital information is omitted from the MDS-MU. ssss is the sense data for this error.
System Action:
The request is rejected.
User Action:
Look up the sense data from the SNA Formats manual.
Reason:
The MDS Router has failed to deliver the MDS-MU to its destination application. ssss is the sense data for the failure.
System Action:
The request is rejected.
User Action:
Look up the sense data from the SNA Formats manual.
Reason:
The MDS-MU to be sent contains origin network id and nau name which do not correspond to those values of the local node.
System Action:
The request is rejected.
User Action:
Since the MDS-MU is sent from the local node, the origin network id and nau name must correspond to that of the local node. You may either delete them from the MDS-MU (in which case SOLVE will default their values to those of the local node) or assign the local values to the MDS-MU.
Reason:
The MDS-MU carrying an MS Capabilities major vector has been rejected by the internal SOLVE MS_CAPS application. rrrr is the reason and may be any of the following:
- INVALID MS CATEGORY The MS category specified is not registered with MS_CAPS.
- INVALID FP APPL FOR SPECIFIED CATEGORY The application supplied is not the focal point application for the specified category.
- A FOCAL POINT OF HIGHER RANK EXISTS A focal point for the specified category is already established and has a higher rank than that which is requested.
- INVALID REPLY The MS Capabilities reply is invalid for its corresponding request.
System Action:
The request is rejected.
User Action:
Correct the error and retry. Where appropriate, use the SHOW SNAMS APPL and/or SHOW SNAMS FP commands to display registered MS applications and existing focal points respectively.
Reason:
The MS_CAPS application has failed to parse the MS Capabilities major vector within an MDS-MU. ssssssss is the sense data for this error.
System Action:
The request is rejected.
User Action:
Look up the sense data from the SNA Formats manual.
Reason:
The application name specified in a SHOW SNAMS command is not registered.
System Action:
None.
User Action:
None.
Reason:
This signifies the end of a tabular listing for a SHOW SNAMS command. nnn is the number of entries displayed for that list.
System Action:
None.
User Action:
None.
Reason:
This is the title for the list of applications displayed on a SHOW SNAMS APPL command. The information displayed for each application are:
NAME This is the registered application name.
ID This is the application routing name used by the MDS Router for message delivery.
NCLID This is the ID of the NCL process which registered the application.
FP This indicates whether or not the application is registered as a focal point for some MS category. Values are "Y" for yes, or "N" for no.
FPN This indicates whether or not the application is registered for focal point updates for some MS category. Values are "Y" for yes, or "N" for no.
System Action:
None.
User Action:
None.
Reason:
This message is produced for each registered application on a SHOW SNAMS APPL command. The information displayed is described in the explanation for message N46H10
System Action:
None.
User Action:
None.
Reason:
The display of a specific application has been requested by using the SHOW SNAMS APPL command with the NAME= parameter specified. aaaa is the name of the specified application.
System Action:
None.
User Action:
None.
Reason:
The display of a specific MS application has been requested by using the SHOW SNAMS APPL command with the NAME= parameter specified. bbbb is the routing name of the specified application used by the MDS Router for message delivery,
System Action:
None.
User Action:
None.
Reason:
The display of a specific MS application has been requested by using the SHOW SNAMS APPL command with the NAME= parameter specified. cccc is the process identifier of the NCL process which registered the application.
System Action:
None.
User Action:
None.
Reason:
The display of a specific MS application has been requested by using the SHOW SNAMS APPL command with the NAME= parameter specified. dddd is the MS category for which the specified application has registered as focal point.
If the application has registered as focal points for multiple MS categories, this message will be repeated for each registered category.
System Action:
None.
User Action:
None.
Reason:
The display of a specific MS application has been requested by using the SHOW SNAMS APPL command with the NAME= parameter specified. eeee is the MS category for which the specified application has registered for focal point updates.
If the application has registered to receive focal point updates for multiple MS categories, this message will be repeated for each registered category.
System Action:
None.
User Action:
None.
Reason:
This is the title for the list of focal points displayed on a SHOW SNAMS FP command. The information displayed for each focal point are:
CATEGORY This is the MS category for the focal point.
DESCRIPTION This is descriptive name for the MS category.
NODE This contains the network ID and the NAU name of the focal point.
APPL This is the application routing name of the focal point.
STATUS This indicates the status/type of focal point established. Possible values are:
INACTIVE: Focal point is inactive.
PENDING : Primary/Backup focal point is pending active.
ACT-PRI : Primary focal point is active.
ACT-BKUP: Backup focal point is active.
PRIMARY : Primary focal point is inactive.
BACKUP : Backup focal point is inactive.
LOCAL : The focal point application is registered on the local node.
System Action:
None.
User Action:
None.
Reason:
This message is produced for eac focal point category displayed on a SHOW SNAMS FP command. The information displayed is described in the explanation for message N46H20.
System Action:
None.
User Action:
None.
Reason:
This is the title for the list of entry points displayed on a SHOW SNAMS EP command. The information displayed for each entry point are:
CATEGORY This is the MS category for the entry point.
DESCRIPTION This is descriptive name for the MS category.
NODE This contains the network ID and the NAU name of the entry point.
STATUS This indicates the status/type of focal point established with respect to the entry point. Possible values are:
PENDING : Primary/Backup focal point is pending active.
ACT-PRI : Primary focal point is active.
ACT-BKUP: Backup focal point is active.
System Action:
None.
User Action:
None.
Reason:
This message is produced for each entry point node displayed on a SHOW SNAMS EP command. The information displayed is described in the explanation for message N46H30
System Action:
None.
User Action:
None.
Reason:
The MDO supplied to an SNAMS statement is invalid.
System Action:
None.
User Action:
Check the syntax of the MDO name and verify it against its corresponding MAP definition.
Reason:
An internal error has occurred while processing Mapping Services.
System Action:
None.
User Action:
Contact your product support representative.
Reason:
The internal recursion stack limit was exceeded while processing an &SNAMS operation.
System Action:
None.
User Action:
Contact your product support representative.
Reason:
The MDS-MU returned on an SNAMS RECEIVE request is invalid for the target MDO.
System Action:
None.
User Action:
Check the type definition of the target MDO and rectify as appropriate.
Reason:
The system attempted to start an APPC link but there was insufficient storage to satisfy the request.
System Action:
The request is rejected.
User Action:
Investigate the storage problem.
Reason:
Indicates that all sessions in the APPC link have been deactivated.
System Action:
None.
User Action:
None.
Reason:
Indicates that the first session of an APPC link is now active. If the link is a single session link only then aaaa is SINGLE, else aaaa is PARALLEL.
System Action:
Single session links require no further action. Parallel session links require the system to start the CNOS transaction responsible for negotiating session limits with the remote LU. The system will activate the minimum number of contention winner sessions negotiated.
User Action:
None.
Reason:
This message indicates that an attempt to start an APPC link as a parallel session link failed and an automatic attempt to start the link as a single session link is being retried.
System Action:
An attempt is made to start a single session link using a mode name with pending conversations, otherwise the first mode name found for the link.
User Action:
None.
Reason:
The CNOS transaction has failed and CNOS is now disabled. aaaa is either CLIENT or SERVER and indicates whether the transaction was started by this node (CLIENT) or the partner node (SERVER). bbbb is the fully qualified partner LU name.
System Action:
The system will attempt to activate sessions for each mode as required by pending conversations.
User Action:
Contact your systems administrator.
Reason:
The CNOS transaction has received a reply indicating abnormal completion of session limits negotiation. aaaa is CLIENT if the transaction was started by the local node, or SERVER if it was started by the partner LU.
System Action:
The system will ignore the error and continue processing.
User Action:
None.
Reason:
This message indicates that the internal CNOS transaction that performs session limit negotiation for parallel session links has started. If started in the local system aaaaaa is CLIENT, else SERVER, while bbbbbb is the link name and ccccc the fully qualified networl name of the remote LU.
System Action:
This message is only seen if APPC link tracing is active.
User Action:
None.
Reason:
This message indicates that the internal CNOS transaction that performs session limit negotiation for parallel session links has ended. If the transaction started in this system aaaaaa is CLIENT, else its SERVER, whill bbbbbb is the link name and cccccc the fully qualified network name for the remote LU.
System Action:
This message is only seen if APPC link tracing is active.
User Action:
None.
Reason:
The internal CNOS transaction has successfully negotiated session limits for the mode name cccccc. The session is with the remote LU bbbbbbbb and aaaaaa is CLIENT if the transaction was started by the local system else its SERVER.
System Action:
This message is only seen if APPC link tracing is active.
User Action:
None.
Reason:
The internal CNOS transaction has detected a command rece whilst negotiating session limits to LU bbbbbbbb for the mode name cccccc. If the transaction was started in the local system aaaaaa is CLIENT else its SERVER.
System Action:
This message is only seen if APPC link tracing is active.
User Action:
None.
Reason:
The internal CNOS transaction is draining all session for mode cccccc to LU bbbbbb. If the transaction was started by the local system then aaaaa is CLIENT, else its SERVER. If the transaction initiator is responsible for actual session termination the dddddd is set to SOURCE else its set to TARGET.
System Action:
This message is only seen if APPC link tracing is active.
User Action:
None.
Reason:
When APPC sends an error to a remote system or receives an error from a a remote system, it logs a sequence of messages describing the nature of the error. This is the first message in the sequence and shows the following information: aaaa indicates whether the error is being sent (SENDING) or has been received (RECEIVED), bbbb indicates the type of error 'ERROR DATA' or 'DEALLOCATE ABEND' and cccc indicates whether the error is contained in a GDS variable or an FMH7.
System Action:
Information describing the error follows this message, including the APPC transaction name, conversation ID and any sense code associated with the error.
User Action:
See the sequence of messages following this message for a detailed description of the error.
Reason:
When APPC sends an error to a remote system or receives an error from a a remote system, it logs a sequence of messages describing the nature of error. This message identifies the transaction in error and shows the following information: aaaa indicates whether it is a 'USER' transaction or a 'SYSTEM' transaction, bbbb is the name of the transaction.
System Action:
The system will log another message giving more details about the error or it will issue a message indicating that error processing has been completed.
User Action:
See all messages belonging to the sequence of messages describing this error to determine which APPC conversation was in error and the exact nature of the error.
Reason:
When APPC sends an error to a remote system or receives an error from a a remote system, it logs a sequence of messages describing the nature of error. This message identifies the APPC conversation ID and its remote LU connection: aaaa is the APPC conversation ID, bbbb is the APPC link name and cccc is the LU name where the conversation partner for conversation aaaa is located.
System Action:
The system will log another message giving more details about the error or it will issue a message indicating that error processing has been completed.
User Action:
See all messages belonging to the sequence of messages describing this error to determine which APPC conversation was in error and the exact nature of the error.
Reason:
When APPC sends an error to or receives an error from a remote system, it logs a sequence of messages describing the error. This message gives sense code information:
Is the sense code data.
Indicates whether the error information originated from the SEND_ERROR verb from the local or remote program, or it was due to the abnormal termination of the conversation.
Note: For information about sense codes, see z/OS Communications Server: IP and SNA Codes.
System Action:
The system logs another message giving more details about the error, or it issues a message indicating that error processing has been completed.
User Action:
See the sequence of messages describing this error, and determine which APPC conversation was in error and the exact nature of the error.
Reason:
When APPC sends an error to a remote system or receives an error from a a remote system, it logs a sequence of messages describing the nature of the error. This message indicates the end of error processing and is the last message in the sequence.
System Action:
None.
User Action:
See all messages belonging to the sequence of messages describing this error to determine which APPC conversation was in error and the exact nature of the error.
Reason:
When APPC sends an error to a remote system or receives an error from a a remote system, it logs a sequence of messages describing the nature of the error. This message indicates that APPC receive processing has received an invalid map name GDS variable.
System Action:
The GDS variable is discarded by the system and processing continues without mapping.
User Action:
See all messages belonging to the sequence of messages describing this error to determine which APPC conversation received the invalid GDS variable.
Reason:
The APPC conversation identified by messages N47H02 and N47H03 received a CONFIRMED response but CONFIRMED was not expected.
System Action:
Processing continues.
User Action:
Consult your systems administrator.
Reason:
A request to allocate a conversation has been rejected by the remote LU because the access security information sent by the requesting procedure is invalid. The conversation was identified by messages N47H02 and N47H03 which precede this message.
System Action:
Message N47H04 is issued with sense data indicating the cause of error. The appropriate error codes are returned to the conversation in RETCODE and ZFDBK.
User Action:
Consult your systems administrator.
Reason:
The remote end of the conversation has detected an error during attach processing. The sense data in message N47H04 indicates the cause of the error. The conversation is identified by messages N47H02 and N47H03.
System Action:
The appropriate error codes are returned to the conversation in RETCODE and ZFDBK.
User Action:
Determine the cause of the error from the sense data in N47H04.
Reason:
APPC has detected a mapping error and is either sending or receiving an Error Data GDS variable indicating the error bbbb for GDS ID or map name cccc . If the local system detected the error aaaa is set to 'SENDING' else it is set to 'RECEIVED'.
System Action:
None.
User Action:
Consult your systems administrator.
Reason:
The remote LU has detected an error and sent an Error Log GDS variable. aaaa indicates the software product name the version and release of the remote LU.
System Action:
None.
User Action:
Consult your systems administrator.
Reason:
The local LU has detected a resource failure (e.g. session outage) which has caused the conversation to terminate abnormally. The conversation is identified by message N47H02 and N47H03.
System Action:
The conversation terminates abnormally. Error codes are returned in
RETCODE and ZFDBK.
User Action:
Investigate the cause of the session outage.
Reason:
This message follows message N47H11 and displays the message text data received in an Error Log GDS variable.
System Action:
None.
User Action:
Consult your systems administrator.
Reason:
APPC has attempted to signon to a user region and the call to the security interface was rejected.
System Action:
The APPC request is rejected with authorisation failed.
User Action:
See all messages belonging to the sequence of messages describing this error to determine which APPC conversation was in error and the exact nature of the error. This error may be accompanied with messages from the security interface.
Reason:
APPC has attempted to signon to a user region and the security system verified the user ID and password as correct, however, the logon will be denied for other reasons. This may be related to other attributes of the user ID that restrict access, for example time of day or terminal etc.
System Action:
The APPC request is rejected with authorisation failed.
User Action:
See all messages belonging to the sequence of messages describing this error to determine which APPC conversation was in error and the exact nature of the error.
Reason:
APPC has attempted to signon to a user region and the security system rejected the signon because the supplied user ID and password were not valid.
System Action:
The APPC request is rejected with authorisation failed.
User Action:
See all messages belonging to the sequence of messages describing this error to determine which APPC conversation was in error and the exact nature of the error.
Reason:
APPC has attempted to signon to a user region and the security system rejected the signon because the supplied user ID is not known to the security system.
System Action:
The APPC request is rejected with authorisation failed.
User Action:
See all messages belonging to the sequence of messages describing this error to determine which APPC conversation was in error and the exact nature of the error.
Reason:
APPC has attempted to signon to a user region however the requesting user bbbbbb did not have an access key that was valid for the target user aaaaaa access lock.
System Action:
The APPC request is rejected with authorisation failed.
User Action:
See all messages belonging to the sequence of messages describing this error to determine which APPC conversation was in error and the exact nature of the error.
Reason:
APPC has attempted to signon to a user region however the region was cancelled before signon was complete.
System Action:
The APPC request is rejected with authorisation failed.
User Action:
See all messages belonging to the sequence of messages describing this error to determine which APPC conversation was in error and the exact nature of the error.
Reason:
APPC has attempted to signon to a user region however the security system rejected the signon and issued the message P1 . The userid that issued the signon request was aaaaaa .
System Action:
The APPC request is rejected with authorisation failed.
User Action:
See the explanation for the message P1 for further action. See all messages belonging to the sequence of messages describing this error to determine which APPC conversation was in error and the exact nature of the error.
Reason:
An attempt was made to change the password for an APPC user but it was rejected by the security exit.
System Action:
An error indication is returned in the SIGNON transaction mesage.
User Action:
Determine the cause of the exit failure. Correct and retry.
Reason:
Internal APPC transaction aaaa has failed due to a protocol violation or invalid data.
System Action:
The request for the service provided by this transaction is rejected.
User Action:
Consult your systems administrator.
Reason:
&APPC RPC/START statement contains invalid syntax. The following message may contain NCL statement after substitution. However syntax error was detected in original NCL buffer before substitution.
System Action:
NCL procedure terminates.
User Action:
Correct NCL procedure and rerun it.
Reason:
Message text as supplied by the LOG=msg operand on an &APPC SEND_ERROR or DEALLOCATE TYPE=ABEND.
System Action:
None.
User Action:
None.
Reason:
Internal APPC transaction aaaa has failed due to a protocol violation or invalid data.
System Action:
The request for the service provided by this transaction is rejected.
User Action:
Consult your systems administrator.
Reason:
This message precedes session trace details for session id dddd MODE cccc in LINK aaaa to remote LU bbbb .
System Action:
A message with trace details will follow this message.
User Action:
None.
Reason:
A request has been issued to APPC's Session Manager to locate a specific link. This message is preceded by message N47T01.
System Action:
Locate link.
User Action:
None.
Reason:
A request has been issued to APPC's Session Manager to build an APPC link. This message is preceded by message N47T01.
System Action:
None.
User Action:
None.
Reason:
A request has been issued to APPC's Session Manager to locate or build an APPC link. This message is preceded by message N47T01.
System Action:
Locate or build link.
User Action:
None.
Reason:
A request has been issued to APPC's Session Manager to activate a session. This message is preceded by message N47T01.
System Action:
Commence session activation.
User Action:
None.
Reason:
A request has been issued to APPC's Session Manager to activate enough contention winner sessions to reach the mode's desired limit. This message is preceded by message N47T01.
System Action:
Session activation commences.
User Action:
None.
Reason:
This message indicates that APPC's Session Manager has received notification that a session has been activated. This message is preceded by message N47T01.
System Action:
None.
User Action:
None.
Reason:
A request has been issued to APPC's Session Manager to deactivate a session. This message is preceded by message N47T01.
System Action:
Session deactivation will commence.
User Action:
None.
Reason:
This message indicates that APPC's Session Manager has received notification that a session has been deactivated. This message is preceded by message N47T01.
System Action:
None.
User Action:
None.
Reason:
A LINK STOP=linkname TYPE=APPC command has been entered and a request has been issued to APPC's session manager to commence deactivation. This message is preceded by message N47T01.
System Action:
In a single session link deactivation commences. In a parallel session link the CNOS transaction is started.
User Action:
None.
Reason:
A request has been issued to APPC's Session Manager to deactivate all sessions for this link. This message is preceded by message N47T01.
System Action:
Session deactivation commences for this link.
User Action:
None.
Reason:
A request has been issued to APPC's Session Manager to deactivate all sessions in this mode. This message is preceded by message N47T01.
System Action:
Session deactivation commences for this mode.
User Action:
None.
Reason:
A request has been issued to APPC's Session Manager to YIELD this session. This message is preceded by message N47T01.
System Action:
A YIELD-SESSION request is sent to the remote LU.
User Action:
None.
Reason:
A request has been issued to APPC's Session Manager to send a BID request for a contention loser session. This message is preceded by message N47T01.
System Action:
A BID request is sent to the remote LU.
User Action:
None.
Reason:
A request has been issued to APPC's Session Manager to send an RTR request to the remote LU to indicate the success of a previous BID for this session. This message is preceded by message N47T01.
System Action:
An RTR request is sent to the remote LU.
User Action:
None.
Reason:
A request has been issued to APPC's Session Manager to send a SIGNAL to the remote LU indicating a request to send. This message is preceded by message N47T01.
System Action:
A SIGNAL request is sent to the remote LU.
User Action:
None.
Reason:
A request has been issued to APPC's Session Manager to send an FMH12 to the remote LU for session LU-LU verification. This message is preceded by message N47T01.
System Action:
An FMH12 request is sent to the remote LU.
User Action:
None.
Reason:
A request has been issued to APPC's Session Manager to send a BIS request/reply to the remote LU to indicate the intention to deactivate this session. This message is preceded by message N47T01.
System Action:
A BIS request/reply is sent to the remote LU.
User Action:
None.
Reason:
A request has been issued to APPC's Session Manager to start the CNOS transaction. This message is preceded by message N47T01.
System Action:
The CNOS transaction is started.
User Action:
None.
Reason:
APPC trace - module aaaaaaaa called the Session Manager to place the session in continue any mode.
System Action:
None.
User Action:
None.
Reason:
APPC trace - module aaaaaaaa called the Session Manager to lock the link
System Action:
None
User Action:
None
Reason:
APPC trace - module aaaaaaaa called the Session Manager to unlock the link.
System Action:
None
User Action:
None
Reason:
APPC trace - module aaaaaaaa called the Session Manager to indicate that a bid has failed.
System Action:
None.
User Action:
None.
Reason:
APPC trace - module aaaaaaaa called the Session Manager to indicate that an LU6.2 session is now initialized and ready for conversation use.
System Action:
None
User Action:
None
Reason:
APPC trace - module aaaaaaaa has called the Session Manager to delete the link after all activity has ceased.
System Action:
None
User Action:
None
Reason:
APPC trace - module aaaaaaa has called the Conversation Manager to indicate that a session is free and available for use.
System Action:
None
User Action:
None
Reason:
APPC trace - module aaaaaaaa has called the Conversation Manager to assign a session to a conversation. If none available the conversation is placed in the pending queue.
System Action:
None
User Action:
None
Reason:
APPC trace - module aaaaaaa called the Conversation Manager to indicate that a session mode is inactive and all pending conversations for the mode are failed.
System Action:
None
User Action:
None
Reason:
A request RU has been sent to the remote LU. Session id, luname and linkname were identified by the previous message N47T01. The fields displayed have the following meaning:
aaaa - RU type, it can be DATA, LUSTAT, RTR, BIS, SIGNAL, BIND and NEG/BIND (negotiated BIND)
bbbb - RU sequence number,
ccc - response type,
dddd - bracket indicator,
eee - chain indicator and
ff - change direction indicator.
System Action:
None.
User Action:
None.
Reason:
A response RU has been sent to the remote LU. The session id, luname and linkname were identified by the previous message N47T01. The fields displayed have the following meaning:
aaaa - RU type, it can be DATA, LUSTAT, RTR, BIS and SIGNAL
bbbb - RU sequence number
c - response type (+ or -)
d - response number (1,2 or 3)
eeee - sense code.
System Action:
None.
User Action:
None.
Reason:
A request RU has been received from the remote LU. Session id, luname and linkname have been identified by the previous message N47T01. The fields displayed have the following meaning:
aaaa - RU type, it can be DATA, LUSTAT, RTR, BIS, SIGNAL, BIND and NEG/BIND (negotiated BIND)
bbbb - RU sequence number
ccc - response type
dddd - bracket indicator
eee - chain indicator
ff - change direction indicator.
System Action:
None.
User Action:
None.
Reason:
A response RU has been received from the remote LU. Session id, luname, and linkname have been identified by the previous message N47T01. The fields displayed have the following meaning:
aaaa - RU type, it can be DATA, LUSTAT, RTR, BIS and SIGNAL
bbbb - RU sequence number
c - response type (+ or -)
d - response number (1,2 or 3)
eeee - sense code.
System Action:
None.
User Action:
None.
Reason:
APPC session trace RU hex dump.
System Action:
None.
User Action:
None.
Reason:
A storage shortage was detected during APPC initialization.
System Action:
None.
User Action:
Investigate the storage shortage.
Reason:
The DEFTRANS or REPTRANS command has been entered but a storage shortage has been detected when processing the command.
System Action:
The request is rejected.
User Action:
Investigate the storage shortage.
Reason:
This message confirms that a Transaction Control Table (TCT) entry has been successfully defined for transaction aaaa .
System Action:
None.
User Action:
None.
Reason:
A DEFTRANS command has been entered to define a Transaction Control Table entry (TCT) but an entry with the same TRANSID and QUAL already exists.
System Action:
The command is rejected.
User Action:
None.
Reason:
The DELTRANS command has been entered to delete a Transaction Control Table (TCT) entry but the entry does not exist.
System Action:
The command is rejected.
User Action:
None.
Reason:
A DEFTRANS or REPTRANS command has been entered to define or replace a Transaction Control Table (TCT) entry but the transaction program name (TPN) specified is not unique.
System Action:
The command is rejected.
User Action:
None.
Reason:
A DEFTRANS or REPTRANS command has been entered to define or replace a Transaction Control Table (TCT) entry but the transaction program name (TPN) specified has an invalid value.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
A REPTRANS or DELTRANS command has been entered to replace or delete a system Transaction Control Table (TCT) entry. If the REPTRANS command was issued the message indicates that replacement of one or more of the specified TCT parameters is invalid for system transaction aaaa . If the DELTRANS command was issued the message indicates that deletion of system transaction aaaa is invalid.
System Action:
The command is rejected.
User Action:
See the NCL Reference for information about the TCT parameters allowed to be changed for system transaction aaaa . It is invalid to delete system transaction TCT entries.
Reason:
A DEFTRANS or REPTRANS command has been entered to define or replace a Transaction Control Table (TCT) entry for system transaction aaaa but aaaa is not a valid system transaction.
System Action:
The command is rejected.
User Action:
Specify a valid system transaction name and retry. A list of the valid system transactions can be obtained by issuing the SHOW DEFTRANS command with TYPE=SYSTEM specified. Note that since system transactions are always internally defined and can not be deleted it is only valid to issue a REPTRANS command to change their TCT options.
Reason:
On a DEFTRANS or REPTRANS the SIGNON=YES operand, which indicates persistent signon is to be carried out for this transaction, is not allowed with SECURITY=NONE. SECURITY=SAME|USER|USERPSWD must be specified instead.
System Action:
DEFTRANS fails.
User Action:
Change either the SIGNON or SECURITY operand settings.
Reason:
This is the header message displayed in response to the SHOW DEFTRANS command. The column headings are:
TRANSID - Transaction id.
TPN - Transaction Program Name.
QUAL - Transaction qualifier.
LINK/LU/DM - Link name, LU name or Domain ID.
MODENAME - Mode name.
PROC - NCL procedure name.
C - Synchronisation level of CONFIRM in use: Y/N.
S - Conversation level security:
N - NONE, S - SAME, SS - SAME with SIGNON=YES, U - USER, US - USER with SIGNON=YES, P - USERPSWD, PS - USERPSWD with SIGNON=YES,
M - Mapped conversation: Y/N.
CMD - Command authority.
System Action:
None.
User Action:
None.
Reason:
This message is produced for each Transaction Control Table (TCT) entry when the SHOW DEFTRANS command is entered. The columns are described in the explanation of message N48301.
System Action:
None.
User Action:
None.
Reason:
The number of Transaction Control Table (TCT) entries displayed as a result of a SHOW DEFTRANS command.
System Action:
None.
User Action:
None.
Reason:
The display of a specific APPC Transaction Control Table entry has been requested by using the SHOW DEFTRANS command with the TRANSID= and QUAL= parameters. aaaa is the transaction id defined in this TCT entry.
System Action:
None.
User Action:
None.
Reason:
The display of a specific APPC Transaction Control Table entry has been requested by using the SHOW DEFTRANS command with the TRANSID= and QUAL= parameters. aaaa is the transaction program name (TPN) defined in this TCT entry.
System Action:
None.
User Action:
None.
Reason:
The display of a specific APPC Transaction Control Table entry has been requested by using the SHOW DEFTRANS command with the TRANSID= and QUAL= parameters. aaaa is the transaction qualifier defined in this TCT entry.
System Action:
None.
User Action:
None.
Reason:
The display of a specific APPC Transaction Control Table entry has been requested by using the SHOW DEFTRANS command with the TRANSID= and QUAL= parameters. aaaa is the linkname defined in this TCT entry.
System Action:
None.
User Action:
None.
Reason:
The display of a specific APPC Transaction Control Table entry has been requested by using the SHOW DEFTRANS command with the TRANSID= and QUAL= parameters. aaaa is the luname defined in this TCT entry.
System Action:
None.
User Action:
None.
Reason:
The display of a specific APPC Transaction Control Table entry has been requested by using the SHOW DEFTRANS command with the TRANSID= and QUAL= parameters. aaaa is the mode name defined in this TCT entry.
System Action:
None.
User Action:
None.
Reason:
The display of a specific APPC Transaction Control Table entry has been requested by using the SHOW DEFTRANS command with the TRANSID= and QUAL= parameters. aaaa is the NCL procedure name defined in this TCT entry.
System Action:
None.
User Action:
None.
Reason:
The display of a specific APPC Transaction Control Table entry has been requested by using the SHOW DEFTRANS command with the TRANSID= and QUAL= parameters. aaaa is the synchronisation level defined in this entry. It can be CONFIRM or NONE.
System Action:
None.
User Action:
None.
Reason:
The display of a specific APPC Transaction Control Table entry has been requested by using the SHOW DEFTRANS command with the TRANSID= and QUAL= parameters. aaaa is the conversation security level defined in this entry. It can be NONE, SAME, USER or USERPSWD.
System Action:
None.
User Action:
None.
Reason:
The display of a specific APPC Transaction Control Table entry has been requested by using the SHOW DEFTRANS command with the TRANSID= and QUAL= parameters. aaaa is the command authority level defined in this entry
System Action:
None.
User Action:
None.
Reason:
The display of a specific APPC Transaction Control Table entry has been requested by using the SHOW DEFTRANS command with the TRANSID= and QUAL= parameters. aaaa is the conversation type defined in this entry. It can be BASIC or MAPPED.
System Action:
None.
User Action:
None.
Reason:
The display of a specific APPC Transaction Control Table entry has been requested by using the SHOW DEFTRANS command with the TRANSID= and QUAL= parameters. aaaa is the NCL server name defined in this TCT entry. Refer to the DEFTRANS command for further information about defining transactions with a server name.
System Action:
None.
User Action:
None.
Reason:
Displays the APPC transaction name if it exceeds 12 characters.
System Action:
None.
User Action:
None.
Reason:
The display of a specific APPC Transaction Control Table entry has been requested by using the SHOW DEFTRANS command with the TRANSID= and QUAL= parameters. aaaa is the scope associated with the server name defined in this TCT entry.
System Action:
None.
User Action:
None.
Reason:
The display of a specific APPC Transaction Control Table entry has been requested by using the SHOW DEFTRANS command with the TRANSID= and QUAL= parameters. aaaa is the domain ID of the SOLVE system that is the target of this APPC transaction.
System Action:
None.
User Action:
None.
Reason:
The display of a specific APPC Transaction Control Table entry has been requested by using the SHOW DEFTRANS command with the TRANSID= and QUAL= parameters. aaaa is CURRENT if the APPC partner procedure is to run in the same NCL environment as the procedure initiating the conversation. aaaa is DEPENDENT if the APPC partner procedure is to run in a dependent environment of the NCL environment in which the procedure initiating the conversation is running.
System Action:
None.
User Action:
None.
Reason:
The DEFMODE or REPMODE command has been entered but a storage shortage has been detected when processing the command.
System Action:
The request is rejected.
User Action:
Investigate the storage shortage.
Reason:
This message confirms that an APPC Mode Control Table (MCT) entry has been successfully defined.
System Action:
None.
User Action:
None.
Reason:
A DEFMODE command has been entered to define an APPC Mode Control Table (MCT) entry but an entry with the same MODE name already exists
System Action:
The command is rejected.
User Action:
None.
Reason:
A DELMODE command has been entered to delete an APPC Mode Control Table (MCT) entry but the entry does not exist.
System Action:
The command is rejected.
User Action:
None.
Reason:
A DEFMODE command has been entered to define an APPC Mode Control Table (MCT) entry but the session limits specified are invalid. The minimum number of winner sessions plus the minimum number of loser sessions can not exceed the session limit.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
The DEFOPSET or REPOPSET command has been entered but a storage shortage has been detected when processing the command.
System Action:
The request is rejected.
User Action:
Investigate the storage shortage.
Reason:
This message confirms that an APPC Option Set Control Table (OSCT) entry has been successfully defined.
System Action:
None.
User Action:
None.
Reason:
A DEFOPSET command has been entered to define an APPC Option Set Control Table (OSCT) entry but an entry with the same OPSET name already exists.
System Action:
The command is rejected.
User Action:
None.
Reason:
A DELOPSET command has been entered to delete an APPC Option Set Control Table (OSCT) entry but the entry does not exist.
System Action:
The command is rejected.
User Action:
None.
Reason:
A DEFOPSET command has been entered to define an APPC Option Set Control Table (OSCT) entry but the MODE= operand specifies an invalid value.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
On a DEFOPSET or REPOPSET command the PV=YES operand, which is used to indicate persistent verification is to be used on transactions, is not allowed with SECURITY=NONE. SECURITY=USER or SECURITY=USERPSWD must be specified instead.
System Action:
DEFOPSET fails.
User Action:
Change either the PV operand, or the SECURITY operand settings.
Reason:
This is the header message displayed in response to the SHOW DEFOPSET command. The column headings are:
OPSET Identifies the unique name for this Option Set Control Table. MODENAME A list of mode names as defined in the MCT that are available through this option set defintion.
MAP Specifies whether or not this option set includes data mapping support. LOG Specifies whether or not this option set includes GDS log variable support.
SEC N - NONE, U - USER, or P - USERPSWD. The level of security for this option set. USER(U), and USERPSWD(P) are possible.
PV Specifies whether or not APPC persistent verification support for user signon is accepted.
PARS Specifies whether or not the target system supports parallel sessions.
System Action:
None.
User Action:
None.
Reason:
This message is produced for each Option Set Control Table (OSCT) entry when the SHOW DEFOPSET command is entered. The columns are described in the explanation of message N48601.
System Action:
None.
User Action:
None.
Reason:
The number of Option Set Control Table or Mode Control Table entries displayed as a result of a SHOW DEFOPSET or SHOW DEFMODE command.
System Action:
None.
User Action:
None.
Reason:
This is the header message displayed in response to the SHOW DEFMODE command. The column headings are:
MODE Identifies the unique name for this Mode Control Table.
MODENAME This is the actual LU6.2 mode name for this MCT definition. LOGMODE This the actual logmode name to be used on session intiation requests for this mode definition.
SESSLIM Specifies the session limit (up to 99) for this mode name.
MINWIN Specifies the minimum number of contention winner sessions. MINLOS Specifies the minimum number of contention loser sessions.
System Action:
None.
User Action:
None.
Reason:
This message is produced for each Mode Control Table (MCT) entry when the SHOW DEFMODE command is entered. The columns are described in the description of message N48604.
System Action:
None.
User Action:
None.
Reason:
This is the header message displayed in response to the SHOW LINK TYPE=APPC command. The column headings are:
LINKNAME The APPC link name.
LUNAME The LU name of the remote partner.
STATUS Link status:
ACTIVE - the link is active, INACTIVE - the link is inactive but it is in the process of being activated, DRAIN, QUIESCE, FORCE - the link was stopped with one of these options.
TYPE P - parallel sessions link, S - single session link.
MAP Y/N - whether or not this link supports mapping.
CNOS Y/N - whether or not CNOS support is active for this link.
LOG Y/N - whether or not link supports GDS Log variables.
SIN N - NONE, U - USER or P - USERPSWD. The level of security the local LU will accept from the remote LU.
SOUT N - NONE, U - USER or P - USERPSWD. The level of security the remote LU will accept from the local LU.
LUV Y/N - whether or not LU-LU verification is in effect.
SLIM The maximum number of active sessions allowed for this link.
AM the access method the link is using.
System Action:
None.
User Action:
None.
Reason:
This message is displayed for each APPC link when the SHOW LINK TYPE=APPC command is issued. The columns are described in the explanation of message N48701.
System Action:
None.
User Action:
None.
Reason:
A SHOW LINK TYPE=APPC command was issued but no APPC link activation requests have been processed.
System Action:
None.
User Action:
None.
Reason:
This message is displayed for all modes of each APPC link that satisfies the selection criteria on the SHOW LINK=linkname TYPE=APPC MODE=modename command. The meaning of each column is explained in the description of message N48708.
System Action:
None.
User Action:
None.
Reason:
This message gives the total number of APPC links that support parallel sessions. It is displayed in response to the SHOW LINK=linkname TYPE=APPC command.
System Action:
None.
User Action:
None.
Reason:
This message is the last line of a SHOW LINK=linkname TYPE=APPC command. It gives the total number of APPC links defined in the system.
System Action:
None.
User Action:
None.
Reason:
This is the header message displayed in response to the SHOW LINK=link- name TYPE=APPC MODE=modename command. The column headings are: LINKNAME The APPC link name.
MODENAME The actual LU6.2 mode name.
STATUS Mode status: ACTIVE, INACTIVE, QUIESCE OR DRAIN.
SESLIM The maximum number of sessions allowed for this mode.
MINWIN The minimum number of contention winner sessions allowed.
MINLOS The minimum number of contention loser sessions allowed.
CWIN The current number of active contention winner sessions.
CLOS The current number of active contention loser sessions.
ACTV The total number of active sessions.
AM The access method in use for the session.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown in response to the SHOW APPC command. It indicates the user ID aaaa of the region for which APPC conversation information is being displayed.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown in response to the SHOW APPC command. It provides the ID of the NCL process for which APPC conversation information is being displayed.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown in response to the SHOW APPC command. It indicates that the APPC conversations shown following this message and belonging to the NCL process identified by N48802, are server conversations (i.e. they have been APPC attached). In addition, if the NCL process is registered as a server this message shows the server name aaaa .
System Action:
None.
User Action:
None.
Reason:
This message gives the total number of APPC conversations displayed in response to the SHOW APPC command.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID= aaaa command has been entered. aaaa is the unique conversation identifier.
System Action:
Single session links require no further action. Parallel session links require the system to start the CNOS transaction responsible for negotiating session limits with the remote LU. The system will activate the minimum number of contention winner sessions negotiated.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered requesting information about a specific APPC conversation. aaaa is the transaction ID being processed by this conversation.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered requesting information about a specific APPC conversation. aaaa is the LU 6.2 mode name associated with this conversation.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered requesting information about a specific APPC conversation. aaaa is the APPC link name.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered requesting information about a specific APPC conversation. aaaa is the LU name of the remote end of this conversation.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered requesting information about a specific APPC conversation. aaaa is the user ID associated with this conversation.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered requesting information about a specific APPC conversation. aaaa is the state of the conversation and can have the following values: RESET (reset), SEND (send), DEFRC (defer-receive), DEFDA (defer-deallocate), RECV (receive), CONF (confirm), CONSE (confirm -send), CONDA (confirm-deallocate), DEALL (deallocate).
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered requesting information about a specific APPC conversation. aaaa is the APPC verb this conversation is currently processing.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered requesting information about a specific APPC conversation. aaaa indicates whether the conversation was attached or allocated.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered requesting information about a specific APPC conversation. aaaa is the synchronisation level used by this conversation.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered requesting information about a specific APPC conversation. aaaa is the name of the NCL procedure that is processing this conversation.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered requesting information about a specific APPC conversation. aaaa is the unique identifier (for a given mode) for the LU 6.2 session which this conversation was allocated.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered requesting information about a specific APPC conversation. aaaa is the number of currently accumulated bytes to send.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered requesting information about a specific APPC conversation. aaaa is the total number of bytes sent by this side of the conversation.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered requesting information about a specific APPC conversation. aaaa is the number of currently accumulated bytes received.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered requesting information about a specific APPC conversation. aaaa is the total number of bytes received by this side of the conversation.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered. aaaa is the NCLID of the procedure that is processing this APPC conversation.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered. aaaa is the NCLID of the procedure that is processing this APPC conversation.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown when a SHOW APPC ID=convid command has been entered. aaaa is the NCLID of the procedure that is processing this APPC conversation.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown in response to the SHOW APPC command. It is only present when the NCL process for which conversation information is being displayed is registered as server. It shows the client-server connect mode aaaa which can be PENDING, ACCEPT, NOTIFY or REJECT, and the number of active conversations bbbb in the server.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown in response to the SHOW APPC command. It marks the end of the display generated by the command and shows the total number aaaa of NCL processes for which APPC conversa- tion information has been displayed.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown in response to the SHOW APPC command. It shows the unique APPC conversation ID aaaa and the local transaction name bbbb of the conversation running in the NCL process identified in message N48802.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown in response to the SHOW APPC command. It shows the LU name aaaa and SOLVE domain ID bbbb (if applicable) of the remote system where the conversation partner is located. It also shows the state cccc of the conversation in the local system.
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown in response to the SHOW APPC command. It shows the APPC conversation ID aaaa and NCL process ID bbbb of the conversation partner when the partner is located in the local SOLVE system. It also shows the state cccc for the local end of the conversation (identified in N48827 which immediately precedes this message).
System Action:
None.
User Action:
None.
Reason:
This message is part of the display shown in response to the SHOW APPC command. It indicates that the APPC conversations shown following this message and belonging to the NCL process identified by N48802, are client conversations (i.e. they have been allocated).
System Action:
None.
User Action:
None.
Reason:
An APPC verb specified the parameter aaaa with invalid value bbbb .
If the parameter is LUNAME, a probable cause of the error is having no DEFLINK TYPE=APPC ... definition covering this LUNAME.
System Action:
The verb that specified this parameter completes with &RETCODE = 16.
User Action:
Correct this parameter and retry. If the parameter is LUNAME, do a SH DEFLINK TYPE=APPC command and ensure that there is an LUMASK that matches this LUNAME. If not, use REPLINK to correct the definition.
Reason:
An APPC verb was issued while the conversation was not in a valid state for that verb. This usually indicates a program error.
System Action:
The APPC verb completes with &RETCODE = 12.
User Action:
Correct and retry.
Reason:
An APPC request has been issued but no conversation is active.
System Action:
The request completes with &RETCODE = 16.
User Action:
Correct and retry.
Reason:
This message indicates that a SEND_ERROR verb was issued by the remote program while in receive or confirm state. The verb may have caused information to be purged.
System Action:
This condition is indicated by setting &RETCODE to 8 and &ZFDBK to 0. The conversation enters receive state.
User Action:
The response to this condition is application dependent.
Reason:
This message indicates that a SEND_ERROR verb was issued by the remote program from send state but no loss of data has occurred.
System Action:
This condition is indicated by setting &RETCODE to 8 and &ZFDBK to 4. No state change occurs.
User Action:
The response to this condition is application dependent.
Reason:
This message indicates that a SEND_ERROR verb was issued by the remote program from send state and truncation of data has occurred.
System Action:
This condition is indicated by setting &RETCODE to 8 and &ZFDBK to 8. The conversation remains in receive state.
User Action:
The response to this condition is application dependent.
Reason:
A request to allocate a conversation has failed due to a condition that may be temporary.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 4.
User Action:
The NCL procedure can be written to retry the allocation request when this condition occurs.
Reason:
A request to allocate a conversation has failed due to a condition that is not temporary.
This failure may occur because the APPC link to another system is not recognized.
System Action:
The failure is indicated by setting &RETCODE to 16 and &ZFDBK to 8.
User Action:
Determine the reason for the failure. The NCL procedure should not retry the allocation request until the condition has been corrected.
Reason:
A request to allocate a conversation has failed because it specified a synchronisation level not supported by the local LU.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 12.
User Action:
Correct and retry.
Reason:
A request to SEND_DATA has failed because the data contains FM headers and the remote end of the conversation or the remote LU does not support FM headers.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 48.
User Action:
Consult your systems administrator.
Reason:
A request to SEND_DATA has failed because it specified a map name and the remote end of the conversation or the remote LU does not support data mapping.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 52.
User Action:
Consult your systems administrator.
Reason:
Indicates that the remote program has issued a DEALLOCATE TYPE=ABEND verb.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 16. The conversation enters deallocate state.
User Action:
Determine the reason for the ABEND in the remote end. Correct and retry.
Reason:
Indicates the remote end of the conversation has been ABENDed by the remote LU.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 20. The conversation enters deallocate state.
User Action:
Determine the reason for the ABEND of the remote end. Correct and retry.
Reason:
Indicates the remote end of the conversation has been ABENDed by the remote LU because a time limit has been exceeded.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 24. The conversation enters deallocate state.
User Action:
Determine the reason for the ABEND. Correct and retry.
Reason:
LU Services in the remote LU has detected a problem and issued a SEND_ERROR verb.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 28. The conversation is in receive state.
User Action:
Consult your systems administrator.
Reason:
LU Services in the remote LU has detected a problem and issued a SEND_ERROR verb.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 32. The conversation remains in receive state.
User Action:
Consult your systems administrator.
Reason:
LU Services in the remote LU has detected a problem and issued a SEND_ERROR verb.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 36. The conversation remains in receive state.
User Action:
Consult your systems administrator.
Reason:
The conversation has terminated due to a failure caused by a condition that may be temporary.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 40. The conversation enters deallocate state.
User Action:
The NCL procedure can be written to retry the request when this condition is encountered.
Reason:
The conversation was terminated due to a failure caused by a condition that is not temporary.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 44. The conversation enters deallocate state.
User Action:
Determine the condition that caused the failure. The transaction should not be retried until the condition has been corrected.
Reason:
The local end of the conversation issued SEND_DATA using a map name that is unknown to the local or the remote LU.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 56. The conversation is in send state.
User Action:
Correct and retry.
Reason:
The local end of the conversation issued SEND_DATA with mapping but the local or remote LU could not map the data based on the map name.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 60. The conversation is in send state.
User Action:
Correct and retry.
Reason:
A request to allocate a conversation has been rejected because the access security information provided by the requesting NCL procedure is invalid.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 64.
User Action:
See your systems administrator.
Reason:
A request to allocate a conversation has been rejected by the remote LU because the request specified a transaction program name that the remote LU does not recognize.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 68.
User Action:
Check that the transaction program name (tpn) defined in the Transaction Control Table (TCT) is also defined in the remote LU.
Reason:
A request to allocate a conversation has been rejected because the request specified program initialization parameters (PIP) but the remote LU does not support PIP data.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 72.
User Action:
Correct and retry.
Reason:
A request to allocate a conversation has been rejected by the remote LU because the remote program expected PIP variables but the requesting NCL procedure did not specify PIP variables or specified an incorrect number of variables.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 76.
User Action:
Correct and retry.
Reason:
A request to allocate a conversation has been rejected because the conversation type specified in the request is not supported by the remote program or the remote LU.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 80.
User Action:
See your systems administrator.
Reason:
A request to allocate a conversation has been rejected because the request specified a synchronisation level not supported by the remote program.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 84.
User Action:
Consult your systems administrator.
Reason:
A request to allocate a conversation has been rejected by the remote LU because the transaction program specified in the request can not be started by the remote LU. The condition may be temporary and the requesting NCL procedure can retry the allocation request.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 88.
User Action:
An NCL procedure can be written to retry the allocation request when this condition is detected.
Reason:
A request to allocate a conversation has been rejected by the remote LU because the transaction program specified in the request can not be started by the remote LU. The condition is not temporary and the requesting NCL procedure should not retry the allocation request.
System Action:
This condition is indicated by setting &RETCODE to 16 and &ZFDBK to 92.
User Action:
Consult your systems administrator.
Reason:
This message confirms that a logon request from LU aaaa has been accepted and the session is now active.
System Action:
None.
User Action:
None.
Reason:
A request to establish an LU 6.2 session to LU aaaa has failed due to an error. The specific error reason is shown as rrrrrr .
System Action:
The request is rejected.
User Action:
Determine the cause of the error by examining the displayed reason.
Reason:
A request to establish an LU 6.2 session to LU aaaa has been rejected because session LU-LU verification has failed.
System Action:
The request is rejected.
User Action:
Consult your systems administrator.
Reason:
A request by LU aaaa to establish an LU 6.2 session has been accepted and the session is now active.
System Action:
None.
User Action:
None.
Reason:
A request to establish an LU 6.2 session to LU aaaa has been rejected because LU-LU verification has failed.
System Action:
The request is rejected.
User Action:
Consult your systems administrator.
Reason:
The APPC user region aaaa was the target of a CANCEL command. This message confirms that region termination has completed.
System Action:
None.
User Action:
None.
Reason:
A request to establish an LU 6.2 session to LU aaaa on link bbbb has failed due to a LOGON error.
System Action:
The request is rejected and a message is issued indicating the reason for the error.
User Action:
The next message issued contains the reason for the error. Refer this to your systems administrator.
Reason:
A request to establish the first LU 6.2 session for LINK aaaa has failed.
System Action:
The request is rejected and a message is issued indicating the reason for the error.
User Action:
The next message issued contains the reason for the error. Refer this to your systems administrator.
Reason:
A request to establish an LU 6.2 session to LU aaaa has failed due to a LOGON error.
System Action:
The request is rejected and a message is issued indicating the reason for the error.
User Action:
The next message issued contains the reason for the error. Refer this to your systems administrator.
Reason:
A request to establish the first LU 6.2 session for LINK aaaa has failed. This is because there was no available access method for the link. Either no access method was nominated (On the LINK START or DEFLINK), or the DOMAIN table entry for this link blocked all available access methods.
System Action:
The request is rejected and a message is issued indicating the reason for the error.
User Action:
Check the LINK or DEFLINK command AM operand (if specified). Also check the SHOW DOMAINS TYPE=DEFINED command output for the available access methods for this link.
Reason:
APPC has attempted to signon to a user region however the region was terminated before signon was complete.
System Action:
The APPC request is rejected with authorization failed.
User Action:
See all messages belonging to the sequence of messages describing this error to determine which APPC conversation was in error and the exact nature of the error.
Reason:
This message confirms normal NCL termination.
System Action:
None.
User Action:
None.
Reason:
This message confirms that clean up processing has completed for an abnormally terminating procedure.
System Action:
None.
User Action:
None.
Reason:
An APPC verb has been issued with an invalid syntax.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
An NCL procedure has issued APPC DEALLOCATE TYPE=ABEND LOG=~aaaa~or
APPC SEND_ERROR LOG=~aaaa~where~aaaa~is a user defined error message. See the description of the APPC verb for further information on the use of the LOG= operand.
System Action:
None.
User Action:
None.
Reason:
This message indicates that the maximum number of bytes allowed to accumulate in the receive queue has been reached.
System Action:
The conversation terminates abnormally.
User Action:
The conversation can be re-written to avoid this problem. For example using CONFIRM level synchronisation to ensure the arrival of data before the next send.
Reason:
This message indicates that conversation aaaa has issued SEND_ERROR and an associated message follows.
System Action:
The error message is by the system.
User Action:
None.
Reason:
An unrecoverable protocol violation or internal error has occurred for an LU 6.2 session. aaaa gives an indication of the nature of the error. The name of the remote LU is given in N48U02 which follows this message.
System Action:
The session is deactivated.
User Action:
Consult your systems administrator.
Reason:
An unrecoverable error has occurred in an LU 6.2 session to LU aaaa and the session will be deactivated. Message N48U01 precedes this message and gives an indication of the nature of the error.
System Action:
The session will be deactivated.
User Action:
Consult your systems administrator.
Reason:
An unrecoverable protocol violation or internal error has occurred for an LU 6.2 session. aaaa gives an indication of the nature of the error. The name of the remote LU is given in N48W02 which follows this message.
System Action:
The session is deactivated.
User Action:
Consult your systems administrator.
Reason:
An unrecoverable error has occurred in an LU 6.2 session to LU aaaa and the session will be deactivated. Message N48W01 precedes this message and gives an indication of the nature of the error.
System Action:
The session will be deactivated.
User Action:
Consult your systems administrator.
Reason:
The SCIP exit for the local LU has received a request that is invalid in an LU 6.2 session.
System Action:
The request is ignored by the system.
User Action:
None.
Reason:
This message indicates that an LU 6.2 session failure has occurred on link aaaa to LU bbbb .
System Action:
The session is deactivated.
User Action:
Consult your systems administrator.
Reason:
An attempt to write an SMF record type X`nn' (HEX) has failed. SMF records can be optionally written to SMF to provide billing or accounting statistics for transmissions. SMF records can be written at the transmitting host, the receiving host or both. This message is written to the activity log only. It is possible that SMF is not active or the SMF datasets are full.
System Action:
Processing continues.
User Action:
Determine why the SMF records could not be written and correct the problem.
Reason:
An attempt to signon/signoff a background APPC user region failed. xxxxxxxx = SIGNON/SIGNOFF.
System Action:
APPC user region signon fails.
User Action:
Check that user is defined on system being signed on to.
Reason:
An attempt to signoff a persistent background APPC user failed.
System Action:
Signoff transaction ignored.
User Action:
Check that background user is still logged on.
Reason:
An error occurred during the APPC SIGNOFF system transaction.
System Action:
SIGNOFF transaction fails.
User Action:
See if background APPC user is still logged on.
|
Copyright © 2014 CA.
All rights reserved.
|
|