|
|
|
Reason:
This is the asynchronous event message. It is intended for delivery in the INTCMD environment to NCL processes which issue asynchronous NCL verbs that notify completion in this manner (eg PANEL and APPC verbs).
System Action:
None.
User Action:
User defined.
Reason:
This is the event notification message. It is intended for delivery in the INTCMD environment to NCL processes profiled for the particular event variables. Scope will be either SYSTEM or REGION, depending on event scope.
System Action:
None.
User Action:
User defined.
Reason:
The release of OS/390 that you are running supports UNIX System Services but the first call made by SOLVE failed.
System Action:
SOLVE UNIX support is reset. SOLVE initialization continues.
User Action:
UNIX Systems Services may not be configured correctly in OS/390. Consult your systems programmer. The reason code may be found in the UNIX System Services Messages and Codes manual.
Reason:
SOLVE in a Fujitsu FSP or XSP environment has been link-edited incorrectly. It has been entered as NM000001, not NMFSP001.
System Action:
SOLVE terminates.
User Action:
Check that NM001 has been link-edited correctly.
Reason:
SOLVE is unable to recognise the operating system environment, when it expects Fujitsu FSP or XSP.
System Action:
SOLVE terminates.
User Action:
Contact your product support representative.
Reason:
SOLVE running in an FSP or XSP environment must run as a subsystem. This was not the case.
System Action:
SOLVE terminates.
User Action:
Change the SOLVE JCL to execute it as a subsystem.
Reason:
SOLVE running in FSP or XSP must be APF authorized.
System Action:
SOLVE terminates.
User Action:
Ensure that the SOLVE load modules are in an APF authorized library.
Reason:
An error was detected during validation of the JCL parm field ( P1 ). The value for the operand is invalid. This error may occur if commas are omitted between two parms and cannot be delimited.
System Action:
Execution is terminated.
User Action:
Correct the error and re-start the region.
Reason:
An invalid operand was detected during validation of the JCL PARM field data. The invalid operand commences with xxxxxxxx.
System Action:
Execution is terminated.
User Action:
Correct the error and re-submit the job.
Reason:
The security exit load module, mmm, named by the SEC=mmm JCL parm, could not be loaded.
System Action:
SOLVE terminates.
User Action:
Check the load module name, and ensure that the load module is in the SOLVE load library.
Reason:
This message indicates that an obsolete parameter ( P1 ) was specified. The parameter has been ignored.
System Action:
None.
User Action:
Update your run JCL to remove the obsolete parameter.
Reason:
The JCL initialization parameters xxx.....xxx are correct and are written to the activity log for reference.
System Action:
None.
User Action:
None.
Reason:
The system broadcasts stored on the VFS dataset could not be read.
System Action:
Processing continues. The stored broadcast will not be set and should be manually set by the system operator.
User Action:
Determine the cause of the dataset I/O error and correct it.
Reason:
This message is written to the system console at the completion of the product's initialization. P1 is the product name and P2 is the system name as set by the PRI= initialization parameter.
The inclusion of the system name provides an identification aid when multiple regions are executing in the same system.
System Action:
The system is available for use. Both the INIT and READY procedures have completed and users can now logon.
User Action:
None
Reason:
Failure to load the specified module caused initialization of the relevant optional feature to be abandoned. yyyy and zzzz are the register values associated with the load failure and can be used to determine the reason for the failure.
System Action:
The optional feature will not be available for use.
User Action:
Determine which feature, of the optional features configured for your system, failed to initialize. Then determine why the system was unable to find the specified load module. The STATUS command will identify those features that have successfully initialized.
Reason:
SOLVE has issued an exclusive ENQ for the VFS dataset dsname, and this ENQ was not satisfied. Another SOLVE system has currently enqueued it. This message is followed by message N00514, which may be replied to cancel the wait.
System Action:
SOLVE delays further initialization until the ENQ is satisfied.
User Action:
If the requested VFS dataset is in use by another SOLVE system, then reply (with anything) to message N00514 and alter the SOLVE JCL, as VFS datasets cannot be shared. If the VFS dataset is being held by a previous execution of this SOLVE job, then when it finishes terminating, the ENQ is released and initialization continues. If you do not want to delay initialization, the JCL parameter, VFSENQ, can be used to prevent the ENQueing of the VFS dataset.
Reason:
This message follows a previous N00511 message. It indicates that the VFS dataset ENQ has now been satisfied.
System Action:
SOLVE initialization continues. The N00514 WTOR message is deleted from the console.
User Action:
None.
Reason:
This message follows the previous N00511 and N00514 messages. The operator has replied to the N00514 (WTOR) message. Any reply to that message results in SOLVE terminating immediately.
System Action:
SOLVE terminates.
User Action:
Check that the operator reply to message N00514 was wanted. Restart SOLVE after correcting the VFS ENQ problems.
Reason:
This message follows the previous N00511 message. It is a WTOR message that may be replied to in order to shut SOLVE down.
If not replied to, it is automatically deleted when the VFS dataset wait is satisfied (see message N00513).
System Action:
SOLVE waits for either a reply (any reply) to this message, or for the the VFS dataset wait to be satisfied.
User Action:
If you do not want SOLVE to wait for the VFS dataset ENQ, then use the operating system REPLY command to reply to this message. SOLVE will then terminate.
Reason:
Region initialization failed because the region was started from a non-authorized load library. This product must run from an APF-authorized library.
System Action:
The region terminates.
User Action:
Determine why the load library is not APF-authorized.
Reason:
The attempt to log on user ID bbbbbbbb failed for the stated reason. The user category (aaaaaaaa) is noted which may be LOCAL, REMOTE, SYSTEM, CONSOLE, TSO, NET/VIEW, VM/OPER, or APPC.
System Action:
User IDs fail to logon only if they have been defined incorrectly on the UAMS dataset, or incorrect definitions are provided by an installation's security exit.
User Action:
Check the definition of the userid whose logon is failing.
Reason:
The initial attempt to logon an internal userid environment failed so a userid environment is built using standard system default userid attributes.
System Action:
Internal virtual userids fail to logon only if they are defined incorrectly on the UAMS dataset, or incorrect definitions are provided by an installation's security exit.
The default command authority is 255 except for consoles. Secondary consoles default to the same attributes as the SYSOPER userid. If the SYSOPER userid is undefined, the default command authority for all consoles is 3. In addition, if the system is configured with the WTO=YES initialization job parameter, the console region is enabled for monitor class message receipt.
User Action:
Check the definition of the userid whose logon is failing.
Reason:
When the SIGNON command is used for an environment refresh the user security system is called to return the user attributes. The security system has rejected the request with the stated reason bbbb.
System Action:
The signon refresh for the region fails and the existing environment remains in effect.
User Action:
Note the reason and refer the problem to your installations help desk facility or systems administrator.
Reason:
Errors were found when the system tried to process the NPF control members or NPF resource tables defined for user xxxxxxxx. Network functions may be limited because resource names have been restricted.
System Action:
None.
User Action:
Use the SHOW NPF and SHOW NPTAB commands to determine the cause of the error. Correct the control members or NPF resource tables and signon again.
Reason:
This message is issued to the log every minute or every 15 seconds (depending on whether CPUCM or CPUFM is specified in the JCL parm XOPT list), if the XOPT JCL parameter CPUMM is specified. It provides an indication of the region CPU utilization in the preceding period.
The fields are as follows:
Displays the time the message was issued
Displays the interval elapsed time. This is normally 60.00 or 15.00. If significantly longer, it may indicate that the region is not being dispatched in a timely manner due to system load.
Displays the amount of CPU time used in this period by the CA NetMaster Maintask (Delta CPU).
Displays the total amount of CPU time used by the CA NetMaster Maintask since this region started.
Displays the average percentage of the time that the CA NetMaster maintask was active in this period (that is, (delta CPU times 100) divided by elapsed time).
System Action:
None.
User Action:
None.
Reason:
This message is issued to the log every minute or every 15 seconds (depending on whether CPUCM or CPUFM is specified in the JCL parm XOPT list), if the XOPT JCL parameter CPUMM is specified. It provides a breakdown of the 'maintask' CPU utilization in the preceding period.
This message is produced only if XM=ZIIP or XM=BEST is specified in the JCL parms. IT indicates the CPU time used by the maintask TCB in the preceding period.
The fields are as follows:
hh:mm:ss displays the time the message was issued.
ET: ss.th displays the interval elapsed time. This is normally 60.00 or 15.00. If significantly longer, it may indicate that the region is not being dispatched in a timely manner due to system load.
TCB: indicates that the times in this message pertain to the maintask TCB CPU utilization.
DC: s.tttttt displays the amount of CPU time used in this period by the CA NetMaster Maintask (Delta CPU).
TC: s.tttttt displays the total amount of CPU time used by the CA NetMaster Maintask since this region started.
%T: pp.th displays the percentage of the CPU time expended in the period by the TCB, the percentage being of the total of TCB times (as in this message), and SRB times (as in the following N00M12 message).
System Action:
None.
User Action:
None.
Reason:
This message is issued to the log every minute or every 15 seconds (depending on whether CPUCM or CPUFM is specified in the JCL parm XOPT list), if the XOPT JCL parameter CPUMM is specified. It provides a breakdown of the 'maintask' CPU utilization in the preceding period.
This message is produced only if XM=ZIIP or XM=BEST is specified in the JCL parms. IT indicates the CPU time used by the paired maintask SRB in the preceding period.
The fields are as follows:
hh:mm:ss displays the time the message was issued.
ET: ss.th displays the interval elapsed time. This is normally 60.00 or 15.00. If significantly longer, it may indicate that the region is not being dispatched in a timely manner due to system load.
SRB: indicates that the times in this message pertain to the SRB associated with the maintask TCB.
DC: s.tttttt displays the amount of CPU time used in this period by the SRB (Delta CPU).
TC: s.tttttt displays the total amount of CPU time used by the SRB since the region started.
%S: pp.th displays the percentage of the CPU time expended in the period by the SRB, the percentage being of the total of TCB times (as in the preceding N00M11 message), and SRB times (as in this message).
System Action:
None.
User Action:
None.
Reason:
This message is issued to the log every minute or every 15 seconds (depending on whether CPUCM or CPUFM is specified in the JCL parm XOPT list), if the XOPT JCL parameter CPUMM is specified. It provides information about events during the preceding period.
This message is produced only if XM=ZIIP or XM=BEST is specified in the JCL parms.
The fields are as follows:
hh:mm:ss displays the time the message was issued.
ET: ss.th displays the interval elapsed time. This is normally 60.00 or 15.00. If significantly longer, it may indicate that the region is not being dispatched in a timely manner due to system load.
MS: sss displays the number of 'mode switches' between TCB and SRB mode.
#W: www displays the number of real waits issued in this period.
#T: ttt displays the number of timer requests issued in this period.
XM: mmm displays the execution mode, normally ZIIP.
System Action:
None.
User Action:
None.
Reason:
This message is issued to the log every minute or every 15 seconds (depending on whether CPUCM or CPUFM is specified in the JCL parm XOPT list), if the XOPT JCL parameter CPUMM is specified. It provides information about events during the preceding period.
This message is produced only if XM=ZIIP or XM=BEST is specified in the JCL parms.
The fields are as follows:
hh:mm:ss displays the time the message was issued.
ET: ss.th displays the interval elapsed time. This is normally 60.00 or 15.00. If significantly longer, it may indicate that the region is not being dispatched in a timely manner due to system load.
PH: s.tttttt displays the delta of the ASSBPHTM field, indicating the total preemptible SRB CPU time expended in the period.
ZC: s.tttttt displays the delta of the ASSB_TIME_zIIP_ON_CP field, indicating the total zIIP-eligible CPU time expended on normal CPs during the period.
ZZ: s.tttttt displays the delta of the ASSB_TIME_ON_zIIP field, indicating the total zIIP-eligible CPU time expended on zIIPs during the period.
%Z: p.th indicates the percentage of total zIIP-eligible time that was actually expended on a zIIP.
System Action:
None.
User Action:
None.
Reason:
This message is issued to the log every minute or every 15 seconds (depending on whether CPUCM or CPUFM is specified in the JCL parm XOPT list), if the XOPT JCL parameter CPUPM is specified. It shows the CA NetMaster Maintask CPU utilization by high-level language processes over the preceding period.
Note: If Process monitoring and CPU monitoring is active, this message follows the N00M10 message, and some fields will be identical.
The fields are as follows:
The time the message was issued.
The interval elapsed time. This is normally 60.00 or 15.00. If significantly longer, it may indicate that CA NetMaster is not being dispatched in a timely manner due to system load.
The amount of CPU time used in this period by the CA NetMaster Maintask (Delta CPU).
The total amount of CPU time used by the high-level language processing in the CA NetMaster maintask in this period. If the value in this field is significantly less than the delta CPU value, it indicates that the remaining Maintask processing is not in high-level languages.
The number of high-level language processes that started in this period.
The number of high-level language processes that ended in this period.
The total number of high-level language processes that existed in this period.
The number of high-level language processes that existed at the end of this period (that is, current).
System Action:
None.
User Action:
None.
Reason:
This message is issued to the log once per minute or once per 15 seconds (depending on whether CPUCM or CPUFM is specified in the JCL parm XOPT list), if the XOPT JCL parameter CPUPM is specified. It follows the N00M20 message that summarizes the period. It lists the most-active high-level language processes in descending scaled CPU utilisation order.
The fields are as follows:
The position of this process in the list.
1 is the top, 10 is the bottom.
The NCLID of the process.
The User ID that this process is executing under.
The base procedure name in the process.
The language of the base procedure.
N is NCL, O is OML, R is REXX.
Two flags that indicate if this process started and/or ended in this period.
The first flag can be 'S' meaning that the process started during this period or '-' meaning that the process was already executing when this period started. The second flag can be 'E' meaning that the process ended during this period or '-' meaning that the process was still executing at the end of the period. Thus,
-- means that the process was executing for the entire period
S- means that the process started during the period
-E means that the process ended during the period
SE means that the process started and ended during the period
The time that the process was executing during the period. If the 'se' field is '--', this is the full period value; otherwise, this field indicates how much of the period the process existed.
The CPU time that this process consumed during the period.
The scaled CPU time that this process consumed during the period. This is the sort key for these lines (descending, highest first), and is calculated by taking the actual CPU time and scaling it by (period time/ actual exec time). For example, if a process was active for 10 seconds out of a 60 second period, the value in this field would be six times the actual CPU time used.
Note: Only processes that existed for at least one second and that used at least 10 milliseconds of CPU are considered for display. Only the top 10 of these eligible processes are displayed.
System Action:
None.
User Action:
None.
Reason:
This message is issued to the log once per minute or once per 15 seconds (depending on whether CPUCM or CPUFM is specified in the JCL parm XOPT list), if the XOPT JCL parameter CPUPM is specified. It follows the last N00M21 message that summarizes the period. It terminates the list of the most active high-level language processes.
System Action:
None.
User Action:
None.
Reason:
This message is issued to the log every minute or every 15 seconds (depending on whether CPUCM or CPUFM is specified in the JCL parm XOPT list), if the XOPT JCL parameter CPUTM is specified. It shows the CA NetMaster CPU utilization by subtasks over the preceding period.
Note: If Task monitoring and CPU monitoring is active, this message follows the N00M10 message, and, if process monitoring is also active, the N00M2x messages, and some fields will be identical.
The fields are as follows:
hh:mm:ss The time the message was issued.
ET: ss.th The interval elapsed time. This is normally 60.00 or 15.00. If significantly longer, it may indicate that CA NetMaster is not being dispatched in a timely manner due to system load.
DC: s.tttttt The amount of CPU time used in this period by the CA NetMaster Maintask (Delta CPU).
TC: s.tttttt The total amount of CPU time used by the subtasks of
the CA NetMaster Maintask in this period.
ST: ss The number of subtasks that started in this period.
EN: ss The number of subtasks that ended in this period.
TO: ss The total number of subtasks that existed in this period.
CU: ss The number of subtasks that existed at the end of this period (that is, current).
System Action:
None.
User Action:
None.
Reason:
This message is issued to the log once per minute or once per 15 seconds (depending on whether CPUCM or CPUFM is specified in the JCL parm XOPT list), if the XOPT JCL parameter CPUTM is specified. It follows the N00M30 message that summarizes the period. It lists the most-active subtasks in descending scaled CPU utilsation order.
The fields are as follows:
aa The position of this subtask in the list.
1 is the top, 10 is the bottom.
iiiiiiii A unique id number assigned to each subtask, to allow correlation of messages concerning that subtask.
(many subtasks have the same program name, thus this field will uniquely identify a specific subtask instance)
pppppppp The subtask program name.
se Two flags that indicate if this subtask started and/or ended in this period.
The first flag can be 'S' meaning that the subtask started during this period or '-' meaning that the subtask was already executing when this period started. The second flag can be 'E' meaning that the subtask ended during this period or '-' meaning that the subtask was still executing at the end of the period. Thus,
-- means that the subtask was executing for the entire period
S- means that the subtask started during the period
-E means that the subtask ended during the period
SE means that the subtask started and ended during the period
s.th The time that the subtask was executing during the period. If the 'se' field is '--', this is the full period value; otherwise, this field indicates how much of the period the subtask existed.
c.tttttt The CPU time that this subtask consumed during the period.
s.tttttt The scaled CPU time that this subtask consumed during the period. This is the sort key for these lines (descending, highest first), and is calculated by taking the actual CPU time and scaling it by (period time/ actual exec time). For example, if a subtask was active for 10 seconds out of a 60 second period, the value in this field would be six times the actual CPU time used.
Note: All subtasks that existed in the period are considered for display. Only the top 50 of these subtasks are displayed.
System Action:
None.
User Action:
None.
Reason:
This message is issued to the log once per minute or once per 15 seconds (depending on whether CPUCM or CPUFM is specified in the JCL parm XOPT list), if the XOPT JCL parameter CPUTM is specified. It follows the last N00M31 message that summarizes the period. It terminates the list of the most active high-level subtasks.
System Action:
None.
User Action:
None.
Reason:
This message is written to the system console when a region or job abends. The message contains the following information:
P1 = Product Name
P2 = Abend Code
P3 = NMID
P4 = Jobname
P5 = Date (yyyyddd)
P6 = Time (hhmmsstt)
System Action:
The region or job will take a formatted dump and a system dump. This message is followed by the N01102 and N01103 messages with additional information.
User Action:
Contact your support office with the details of the abend.
Reason:
This message is written to the system console when a region or job abends. It follows the N01101 message and contains information about the abend. The fields are:
SRC= P1 - the source of the abend information. P1 will be either:
AB - meaning that the information in this and the N01103 message was derived from the PSW and registers at the time of the abend, or
SE - meaning that the information was derived from the registers and PSW from the region/job primary RB.
PRD= P2 - The product name.
P3 - Either:
REL=Rv.r - the product release, or,
INTLVL=vvrrmm - the internal product level (Management Services level).
SP= P4 - the product Service Pack level.
ABC= P5 - the abend code. One of the following:
S-xxx - system abend code.
U-nnnn - user abend code.
N-aaa-bb - internal abend code.
System Action:
See message N01101
User Action:
See message N01101
Reason:
This message is written to the system console when a region or job abends. It follows the N01102 message and contains information about the abend. The fields are:
ALM= P1 - the ABEND load module.
ALO= P2 - the offset within the ABEND load module.
ACS= P3 - the ABEND CSECT, if it could be identified.
ACO= P4 - the offset within the ABEND CSECT, if the CSECT could be identified.
LLM= P5 - the last apparent active load module.
LCS= P6 - the last apparent CSECT.
System Action:
See message N01101
User Action:
See message N01101
Reason:
This message is used as the dump title if an SDUMP is requested when a ##FDUMP command is issued. The message contains the following:
P1 = Product Name
P2 = NMID
P3 = Jobname
P4 = Date (yyyyddd)
P5 = Time (hhmmsstt)
System Action:
The product takes a formatted dump and optionally a system dump. When a system dump is requested, it is written to a SYS1.DUMP dataset with this message used as the dump title.
User Action:
Send the formatted and system dumps to your support office.
Reason:
The system attempted to obtain storage but none was available.
System Action:
The system attempts to continue to operate but if not successful terminates with a U017- 01 abend, signifying that there is insufficient storage for continued operation.
User Action:
If the message occurs persistently, increase the region or partition size. If the message continues to occur, contact your product support representative.
Reason:
The value set by either the STGWRN (below 16M) or STGWRNXA (above 16M) has been exceeded.
System Action:
The message is issued at 30 second intervals until the storage used drops below the limit.
User Action:
Review the storage requirements to determine if the region size is adequate for the workload.
Reason:
This message is written to the log during region startup. It indicates the requested execution mode (aaa), as set or defaulted by the XM JCL Parm, and the in-effect execution mode (bbb).
The possible requested mode values are as follows:
N/S-No execution mode was requested.
TASK-Task mode was requested.
ZIIP-zIIP mode was requested.
BEST-The best available mode was requested.
The possible in-effect execution mode values are as follows:
TASK-The region is executing in TASK mode.
ZIIP-The region is executing in SRB mode, possibly utilizing a zIIP if one is available.
System Action:
None.
User Action:
None.
Reason:
This message is written to the log during region startup. It indicates that the setup of the requested execution mode failed. A reason is provided.
The possible requested mode values are as follows:
ZIIP-zIIP mode was requested.
BEST-The best available mode was requested.
The possible reasons are as follows:
System Action:
Initialization continues in TASK mode.
User Action:
Examine the reason and take corrective action, if required.
Reason:
No previous INTREAD has been satisfied or INTCONT has been issued after other message read processing, such as LOGREAD, MSGREAD etc.
System Action:
The procedure is terminated.
User Action:
Ensure INTREAD is satisfied before issuing INTCONT. If necessary change the procedure's logic to issue INTCONT before other message processing.
Reason:
No previous INTREAD has been satisfied or INTREPL has been issued after other message read processing, such as LOGREAD, MSGREAD etc.
System Action:
The procedure is terminated.
User Action:
Ensure INTREAD is satisfied before issuing INTREPL. If necessary change the procedure's logic to issue INTREPL before other message processing.
Reason:
$MSG is a reserved MDO name for an INTREAD operation. A $MSG MDO is always built when an INTREAD request is satisfied, hence it may not be the target of an embedded input MDO.
System Action:
The procedure is terminated.
User Action:
Correct the INTREAD statement to specify an MDO name other than $MSG.
Reason:
An EVENT statement contains an invalid NAME operand. The event name must consist of valid NCL variable name characters and must not begin with $.
System Action:
The NCL procedure is terminated.
User Action:
Correct the EVENT NCL statement.
Reason:
A PROFILE EDS ENABLE=name command was issued from an environment in which a profile with the same name has already been defined.
System Action:
The registration request is ignored.
User Action:
Ensure the profile is only defined once, or define the new profile with a different name.
Reason:
SOLVE was unable to obtain storage for a PROFILE EDS ENA=name request.
System Action:
The registration request is ignored.
User Action:
Contact your systems administrator and examine reason for storage shortage.
Reason:
A PROFILE EDS DIS=name command was issued from an environment in which no profile existed with a matching name for the request.
System Action:
The request is ignored.
User Action:
Ensure the profile is correct.
Reason:
The system wide limit on event profile registration has been reached.
System Action:
The registration request is ignored.
User Action:
Investigate why a large number of event profile requests are being generated.
Reason:
SOLVE was unable to obtain storage for a PROFILE EDS ENA=name request.
System Action:
The registration request is ignored.
User Action:
Contact your systems administrator and examine the reason for the storage shortage.
Reason:
This message is in response to a successful PROFILE EDS DIS=name request.
System Action:
All matching EDS profiles were successfully disabled.
User Action:
None.
Reason:
This message is in response to a successful PROFILE EDS ENA=name request.
System Action:
The EDS profile is registered.
User Action:
None.
Reason:
The RESOURCE operand specified on the PROFILE EDS request is invalid.
System Action:
The registration request is ignored.
User Action:
Correct the PROFILE EDS statement.
Reason:
This message is issued if the event registration profile build fails.
System Action:
The registration request is unsuccessful.
User Action:
Investigate the reason for the EDS profile build failure by looking for messages issued prior to this one.
Reason:
The TYPE operand specified on the PROFILE EDS request is invalid.
System Action:
The registration request is ignored.
User Action:
Correct the PROFILE EDS statement.
Reason:
The ROUTCDE operand specified on the PROFILE EDS request is invalid.
System Action:
The registration request is ignored.
User Action:
Correct the PROFILE EDS statement.
Reason:
The name specified on the PROFILE EDS ENA=profile NAME=name request is invalid. Specify any NCL character set name plus '*' wild characters.
System Action:
The registration request is ignored.
User Action:
Correct the PROFILE EDS statement.
Reason:
The name specified on the PROFILE EDS ENA=name request is invalid. The profile name may contain 1 to 32 characters which are valid in an NCL variable in addition to '.' and '_'.
System Action:
The registration request is ignored.
User Action:
Correct the PROFILE EDS ENABLE operand.
Reason:
This is the header line for the SHOW EDS command output.
System Action:
None.
User Action:
Refer to message N02D02.
Reason:
This is a detail line for SHOW EDS command output which follows the N02D01 message. The attribute masks for an event profile are displayed. Fields displayed are as follows:
userid - Id of user who has EDS profile defined.
nclid - NCLID of NCL procedure to which EDS profile is assigned.
scope - Scope may be SYSTEM or REGION and defines the scope of event receipt.
profname - Name assigned to EDS profile on the ENA= operand of the PROFILE EDS command.
NAME= Shows the event name mask for the profile.
TYPE= Lists event types for profile.
OBJECT= Object mask (or mask pair) for profile.
RESOURCE=Resource mask for profile.
REF= Profile reference mask.
ROUTCDE= PROFILE route codes.
Only the first 256 bytes of profile details will be displayed on message N02D02. Data extending beyond this overflows onto message N02D03.
System Action:
None.
User Action:
None.
Reason:
This is a continuation of N02D02 for profile displays which do not fit on one line.
System Action:
None.
User Action:
See N02D02 for details.
Reason:
A SHOW EDS command was issued but no EDS profiles matched the show command display criteria.
System Action:
None.
User Action:
Check SHOW EDS operands.
Reason:
A SHOW EDS command operand was invalid.
System Action:
None.
User Action:
Check SHOW EDS operands.
Reason:
This message is displayed for a SHOW EDS STATS command. It shows the number of events which have matched a user's EDS profile since it was enabled (time and day show when profile was enabled).
System Action:
None.
User Action:
None.
Reason:
This message is displayed for a SHOW EDS STATS command. It shows the number of times events have been delivered to a user NCL environment because it matched an enabled EDS profile for that NCL process.
Note that a single event may be delivered more than once if it matches multiple EDS profiles.
System Action:
None.
User Action:
None.
Reason:
This message is displayed for a SHOW EDS STATS command. It shows the number of times EDS has been entered since system initialization. This represents the number of &EVENT statements executed, plus the number of times internal event points were entered.
System Action:
None.
User Action:
None.
Reason:
This message is displayed for a SHOW EDS STATS command. It shows the number of events delivered to all users since system initialization.
System Action:
None.
User Action:
None.
Reason:
This message indicates a SOLVE logic error has occurred during event profile cleanup.
System Action:
None.
User Action:
Report the error to your product support representative.
Reason:
This message is written to the CA NetMaster log during initialization and shows the local date and time. It also shows the offset from UTC (GMT) time in the format shhmm, or if grater than 1 day, sddd:hhmm.
System Action:
None.
User Action:
None.
Reason:
This message is written to the CA NetMaster log during initialization when the TZ JCL parm is processed. It shows the offset used for local time.
System Action:
None.
User Action:
None.
Reason:
This message is written to the CA NetMaster log during initialization when the TZ JCL parm is processed. It shows that the region is using GMT (UTC) time.
System Action:
None.
User Action:
None.
Reason:
This message is written to the CA NetMaster log and monitor receivers when a local time offset change is processed.
System Action:
The local region time is updated.
Additional message are written (messages N02H11,12,13) indicating the old, new and changed offset.
User Action:
None.
Reason:
This message is written to the CA NetMaster log and monitor receivers following the N02H10 message. It shows the previous local time and UTC (GMT) offset.
System Action:
None.
User Action:
None.
Reason:
This message is written to the CA NetMaster log and monitor receivers following the N02H11 message. It shows the new local time and UTC (GMT) offset.
System Action:
None.
User Action:
None.
Reason:
This message is written to the CA NetMaster log and monitor receivers following the N02H12 message. It shows the change in local time offset for shhmm format or sddd:hhmm format.
System Action:
None.
User Action:
None.
Reason:
This message is written to the CA NetMaster log during initialization and indicates that a listener for ENF event 53 (local time offset change) has been installed.
This listener allows the region to automatically detect and process changes to the local date/time offset relative to GMT (UTC).
Note: The listener is activated only for z/OS release 1.7 or later.
System Action:
The listener is activated.
User Action:
If you do not want the ENF event 53 listener, specify XOPT=NOENF53 in the JCL parameters.
Reason:
This message is written to the CA NetMaster log during initialization and indicates that the ENF event 53 listener could not be installed. The reasons are:
The reasons are self-explanatory.
System Action:
The listener is not installed.
User Action:
If the reason is not because of an unsupported operating system or because it is not APF-authorized, contact Technical Support.
Reason:
No valid resource name was specified on an RSCCHECK,
NPFDCHK, NPFMCHK, or NPFVCHK builtin function statement.
System Action:
The NCL procedure is terminated.
User Action:
Correct the statement and retry the procedure.
Reason:
An invalid statement has been detected.
System Action:
The NCL procedure is terminated.
User Action:
This may have been caused by a variable having an unexpected null value which resulted in the variable being eliminated during the variable substitution process and hence altering the syntax of the statement. You must ensure that all variables are correct (and cannot have a null value) when used in a string statement (eg: SUBSTR, SELSTR). Correct the statement and retry the procedure.
Reason:
An invalid operator xx has been found in the nominated aaaaaaaa NCL statement. Only those operators (eg: EQ or NE etc.) discussed in the appropriate section of the NCL Reference are accepted.
System Action:
The NCL procedure is terminated.
User Action:
Refer to the NCL Reference for valid operators. Correct the statement and retry the procedure. This error may have been caused by the elimination of a null variable during the variable substitution process. The NCL User Guide discusses techniques to cater for situations where variables in &IF statements may have a null value.
Reason:
NCL procedure processing provides automatic runaway loop protection. When an NCL procedure commences processing a value of 1000 is assigned to the &LOOPCTL counter. This is subsequently decremented by 1 for each branch statement. If this count reaches 0, the procedure is automatically terminated as potentially looping.
System Action:
The NCL procedure is terminated.
User Action:
Determine if the procedure is in fact looping. The &CONTROL TRACE statement can be used to obtain expanded trace information during the processing of a procedure. If the NCL procedure is looping, correct it and retry. If the procedure is not looping, but has validly exhausted the &LOOPCTL counter due to large processing requirements, use the &LOOPCTL statement to assign a higher loop protection limit. Refer to the NCL Reference for information on the &LOOPCTL built infunction.
Reason:
The data to be converted to character format by the HEXPACK function must consist of hexadecimal digits (0 - 9, A - F).
System Action:
The procedure is terminated.
User Action:
Correct and retry.
Reason:
HEXEXP processing converts single characters into 2-digit HEX representation (eg: 'A' converts to 'C1'). The result of the conversion is a string twice as long as the original string. Since the maximum length of a variable is 256 characters, the maximum string length input to HEXEXP processing is 128 characters, whilst for HEXPACK it is the NCL word length of 256 characters. This message indicates that more than the maximum length was supplied.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
APPSTAT was used to obtain the status of an application but the name of the application was either omitted or was not a valid 1 - 8 character name.
System Action:
The procedure is terminated.
User Action:
Correct and retry.
Reason:
Data assigned to a variable cannot exceed the maximum variable data length of 256 characters.
System Action:
The procedure is terminated.
User Action:
Correct and retry.
Reason:
The numeric expression contains invalid syntax or has violated the rules for numeric expressions.
System Action:
The NCL procedure is terminated.
User Action:
Ensure no variables have been eliminated from the expression during the variable substitution process because they have a null value. Correct the statement and retry the procedure.
Reason:
The numeric expression has resulted in a value that exceeds the limits for the function being attempted.
System Action:
The NCL procedure is terminated.
User Action:
Refer to the NCL User Guide for information on the limits of numeric expressions. Correct the statement and retry the procedure.
Reason:
The &HEX and &DEC builtin functions must specify the number to be converted. For &DEC this must be a valid hexadecimal number, for &HEX this must be a valid decimal number.
System Action:
The NCL procedure is terminated.
User Action:
Refer to the NCL Reference for information on the maximum values that can be processed by these functions. Correct the statement and retry the procedure.
Reason:
An NUMEDIT NCL statement to convert a floating point number to a character format has failed because the source variable is not a valid floating point number.
System Action:
The NCL procedure terminates.
User Action:
Correct the procedure and retry.
Reason:
The variable xxxxxxx violates the rules for user defined variables. A variable name must not exceed 12 characters (not including the ampersand).
System Action:
The NCL procedure terminates.
User Action:
Correct the statement and retry the procedure.
Reason:
The syntax of an assignment statement is invalid.
System Action:
The NCL procedure terminates.
User Action:
Correct the statement and retry the procedure.
Reason:
The system imposed limit for the number of outstanding NCL trace messages has been reached.
System Action:
Tracing has been terminated, processing of the NCL procedure continues.
User Action:
If the trace limit is too low, increase it by use of the SYSPARMS NCLTRMAX command, or use the CONTROL TRACE/NOTRACE NCL statement to do selective tracing.
Reason:
The statement following an WAIT must be a command.
System Action:
The NCL procedure terminates.
User Action:
Correct the statement and retry.
Reason:
The specified keyword cannot be used in a procedure of this type or the keyword has been used in an invalid way.
System Action:
The procedure is terminated.
User Action:
See the NCL Reference for restrictions on the use of this keyword.
Reason:
The function xxxxxxxx does not support operand yyyyyyyy. It is invalid.
System Action:
The NCL procedure terminates.
User Action:
Correct the statement and retry the procedure.
Reason:
Use of the &DEFMSG function is only valid within the system level PPOPROC procedure.
System Action:
The NCL procedure terminates.
User Action:
Use of this function within other NCL procedures is meaningless. Refer to the NCL Reference for information on these facilities.
Reason:
When used within PPOPROC, DEFMSG specifies the three trailing characters of the VTAM PPO messages to be processed by the procedure. Multiple three character operands can follow DEFMSG. In systems other than DOS each operand must be a three digit number in the range 000-999. In a DOS or NIDOS system, each operand must be one alphabetic characters followed by a 2 digit number in the range 00-99.
System Action:
The NCL procedure terminates and normal PPO message processing resumes.
User Action:
Correct the statement and retry the procedure.
Reason:
During the processing of the specified statement an attempt was made to perform variable substitution on the variable xxxxxxxx. The substitution process failed as the system buffer limit was exceeded.
System Action:
The NCL procedure terminates.
User Action:
The maximum size of a single variable is 256 characters. The maximum length of a statement after variable substitution is 16384. Restructure the procedure so that the failing statement remains within the system limits.
Reason:
The first message format identifies the passage of logic flow through the nominated label (.aaaaaaaa), when the CONTROL TRACE/TRACELAB/ TRACEALL/TRACELOG statement is in force, at statement number bbbbbbbb within procedure cccccccc. The NCLID of the NCL procedure (dddddd) is also shown.
The second message format is issued when CONTROL TRACE/TRACELOG is in force. The statement number (bbbbbbbb) and the substituted text of the statement (stmttext) are displayed.
The third message format is issued when CONTROL TRACEALL is in use. In addition to the second format, the message will include the procedure name (cccccccc) and its NCLID (dddddd).
System Action:
None.
User Action:
None.
Reason:
The maximum length of the string generated by variable substitution cannot exceed 256 characters.
System Action:
The procedure is terminated.
User Action:
Correct and retry.
Reason:
The variable xxxxxxx exceeds the system limit of 256 characters.
System Action:
The NCL procedure terminates.
User Action:
Restructure the procedure to avoid this error and work within system limits.
Reason:
An invalid label has been specified. A label must commence with a period and be followed by 1 to 12 characters.
System Action:
The NCL procedure terminates.
User Action:
Correct the label and retry the procedure.
Reason:
The NCL statement starts with an unknown keyword or a keyword that cannot logically start a statement.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
The NCL statement contains an NCL verb created by a process of substitution. However, it is not valid to create the verb in this way.
System Action:
The NCL procedure terminates.
User Action:
Correct and retry.
Reason:
An NCL assignment statement has been created by a process of substitution. This is not valid.
System Action:
The NCL procedure terminates.
User Action:
Correct the procedure and retry.
Reason:
Signals the completion of a previous SYSPARMS PRELOAD=procname request. IF this preload was as a result of the SYSPARMS CMDREPL command, the additional literal (COMMAND REPLACED) will appear.
System Action:
Procedure procname is now preloaded.
User Action:
The SHOW NCLSTAT command can be used to display a list of preloaded NCL procedures. A preloaded procedure cannot be updated until a restart of the system is performed or a SYSPARMS UNLOAD=procname command is issued.
Reason:
A statement has been found in the nominated NCL procedure that (after concatenation of all continuation statements) exceeds the system limit of 2048 characters (excluding trailing blanks and continuation '+' characters). The CONTROL CONT / NOCONT operands control continuation processing.
System Action:
The NCL procedure is terminated.
User Action:
Correct the overlength statement and retry the procedure.
Reason:
The LIST, EXEC, FSPROC, NCLCHECK or START processing for NCL procedure 'procedure' has completed.
If SYSPARMS NCLOGTRM=YES is in effect, this message is also logged, with the total processing-units and performance group displayed.
System Action:
None.
User Action:
None. This message is issued by default. It can be suppressed by issuing an CONTROL NOENDMSG statement within the procedure. Regardless of CONTROL NOENDMSG, this message will be issued if a procedure is terminated by an END command.
Reason:
An NCL process aaaaaaaa that was being executed has been flushed. This can be the result of the FLUSH or CANCEL command being issued or the OCS Operator exiting while the function was in progress, in which case this message will be written to the log. The NCL identifier nnnnnn of the ended process is included in the message.
System Action:
None.
User Action:
None.
Reason:
The NCL label statement nominated has an invalid label name.
System Action:
Execution of the procedure procname fails.
User Action:
Correct the label and retry.
Reason:
The special system procedure typPROC (CNMPROC, PPOPROC, or LOGPROC) has ended. This can result from an error in the procedure that has caused it to terminate or the logic of the procedure has allowed it to end. This message is issued to users with Monitor status.
System Action:
The procedure is no longer active. Normal typ message processing resumes.
User Action:
Correct the error or procedure logic to avoid termination and restart the procedure.
Reason:
The nominated procedure could not be loaded, as the library indicated was not defined in the SOLVE JCL.
System Action:
The procedure is not loaded.
User Action:
Ensure the alternate NCL library DD or DLBL statement(s) are placed in the SOLVE JCL.
Reason:
The dataset(s) on the indicated ddname is not a PDS, or is not RECFM=F/FB with LRECL 80.
System Action:
The procedure is not loaded.
User Action:
Ensure the correct library name is in the user's UAMS definition.
Reason:
An ABEND occurred while loading an NCL procedure from the indicated library.
System Action:
The procedure is not loaded.
User Action:
If the ABEND is a SYSTEM 913 ABEND, ensure that SOLVE is authorized to access the library. Otherwise, investigate the ABEND using the relevant operating system message manuals.
Reason:
A hard I/O error occurred while loading an NCL procedure from the indicated library.
System Action:
The procedure is not loaded.
User Action:
Correct the cause of the I/O error. Note that, for normal NCL load requests, the system automatically retries once after an I/O error.
Reason:
Insufficient storage was available to process an NCL procedure load request.
System Action:
The procedure is not loaded.
User Action:
Retry. If the problem persists, contact your systems administrator.
Reason:
An unexpected return code from the FIND macro was encountered while trying to locate the indicated NCL procedure.
System Action:
The procedure is not loaded.
User Action:
Contact your systems administrator. The PDS directory may be corrupt.
Reason:
An ABEND occurred while loading an NCL procedure from the indicated library.
System Action:
The procedure is not loaded.
User Action:
If the ABEND is a SYSTEM 913 ABEND, ensure that SOLVE is authorized to access the library. Otherwise, investigate the ABEND using the relevant operating system message manuals.
Reason:
A hard I/O error occurred while loading an NCL procedure from the indicated library.
System Action:
The procedure is not loaded.
User Action:
Correct the cause of the I/O error. Note that, for normal NCL load requests, the system automatically retries once after an I/O error.
Reason:
Insufficient storage was available to process an NCL procedure load request.
System Action:
The procedure is not loaded.
User Action:
Retry. If the problem persists, contact your systems administrator.
Reason:
An MVS partitioned dataset containing the NCL library (DDNAME bbbbbbbb) has been extended by another region/address space whilst SOLVE was loading procedure aaaaaaaa.
System Action:
If the procedure was being loaded as a result of the LIST command, the command is terminated. In all other cases the load is retried once.
User Action:
If this was as a result of a LIST command, resubmit the command.
Reason:
An attempt to load the named procedure failed. The procedure was found to be in written in the OML language, not NCL.
This should only occur if an NCLCHECK command names the procedure.
System Action:
The load is terminated.
User Action:
If this was as a result of the NCLCHECK command, use the OMLCHECK command instead.
Reason:
An I/O error was encountered while loading the indicated procedure. One retry will be attempted.
System Action:
The procedure load will be restarted.
User Action:
None. If the load fails a second time, further messages will be produced.
Reason:
Insufficient storage was available to complete the load of NCL procedure xxxxxxxx.
System Action:
The procedure is not executed.
User Action:
Use the SHOW NCL command to determine whether an unusually high number of NCL processes are running.
Contact Technical Support if you are unable to identify the reason (process starts looping) for the situation.
Reason:
This message (sent to the SOLVE activity log) indicates that the NCL I/O manager has initialized successfully.
System Action:
None.
User Action:
None.
Reason:
This message indicates an unexpected subtask abend by an NCL I/O subtask.
System Action:
An attempt is made to restart the subtask.
User Action:
Determine the reason for the abend from the operating system log. Contact your product support representative.
Reason:
An I/O error was encountered whilst loading the indicated NCL procedure. I/O error information, as obtained by the SYNADAF function is displayed.
System Action:
The system will retry the load, if possible.
User Action:
None, unless the problem persists. If it does, investigate the problem.
Reason:
Statistics for the NCL procedure loader follow. This is output of the SHOW NCLLOAD command.
System Action:
none.
User Action:
none.
Reason:
Statistics for the NCL procedure loader follow. This is a heading line.
System Action:
none.
User Action:
none.
Reason:
This is an NCL loaded stats line. The name is self-explanatory.
System Action:
none.
User Action:
none.
Reason:
A group of NCL procedures contains more than 250 levels of nested EXEC statements. EXEC statements in excess of 250 nested levels are invalid.
System Action:
The procedure terminates.
User Action:
Restructure the procedure(s) to prevent it/them from exceeding this maximum.
Reason:
During execution of a group of NCL procedures, a nested EXEC statement occurred specifying a procedure already being executed at an earlier nesting level.
System Action:
The EXEC statement is ignored since its processing could lead to a nesting loop.
User Action:
Check the nesting levels specified in the executed group. This check is imposed to avoid inadvertent recursive looping of procedures. If it is intentional to re-execute a procedure of the same name the CONTROL RECCHK option must be used to bypass this check.
Reason:
The procedure specified on the EXEC, START or FSPROC command does not exist in the procedure library specified by ddname.
System Action:
The command is rejected.
User Action:
Correct the procedure name. If the procedure name is correct ensure that it exists in the procedure library specified for use by this userid. This can be determined by the SHOW EXEC command or alternatively the LIST command could be used to display the procedure without execution.
Reason:
This message is issued if the user exits OCS mode before the specified procedure had started execution. The procedure type (NCL or OML) is indicated. This message is only written to the activity log.
System Action:
The procedure is flushed prior to completion.
User Action:
Determine if any corrective action is required due to the procedure being flushed.
Reason:
A request to execute an NCL procedure has been entered while an existing procedure is executing in this OCS window. NCLPEND=YES is in force by default; therefore, the second procedure is queued for execution when
System Action:
Execution commences automatically when all previous procedures are
User Action:
If necessary, use the SHOW NCL command to determine why the existing
Reason:
This situation should not happen because NCLPEND=YES is hard-coded.
System Action:
The command is rejected.
User Action:
Contact Technical Support.
Reason:
An attempt has been made to preload an NCL procedure that is already preloaded, or being shared by one or more users.
System Action:
The request is ignored.
User Action:
Use the SYSPARMS UNLOAD command to schedule an unload for a procedure that is PRELOADed or AUTOSHRed. If a new copy is required in storage, the procedure can then be PRELOADed. If the procedure is in the P-UNLOAD state, subsequent requests for this procedure will not be queued to this copy, rather, a new copy of the procedure will be loaded to which they will be directed. The SHOW NCLSTAT command can be used to display the names of PRELOADed or AUTOSHRed procedures, and those procedures that are pending an unload request.
Reason:
During manipulation of the internal indices for the preload/autoshare lists, an error occurred.
System Action:
The procedure is not loaded.
User Action:
Contact your Systems Administrator and report this error to Technical Support.
Reason:
A SYSPARMS CMDREPL=aaaaaaaa command has failed. This command requires the replacement NCL procedure (aaaaaaaa) to be preloaded, and will automatically preload it. During the execution of the command, another SOLVE user has unloaded the procedure.
System Action:
The command fails.
User Action:
Resubmit the command.
Reason:
A SYSPARMS CMDREPL=aaaaaaaa command has failed because there is already a preloaded or autoshared copy of the NCL procedure.
System Action:
The command fails.
User Action:
Issue a SYSPARMS UNLOAD=aaaaaaaa statement and retry the command.
Reason:
This message is produced by the NCL debug facility when an NCL procedure is suspended during execution. 'reason' gives the reason why the procedure was suspended.
'HOLD COMMAND BEING ISSUED' indicates that the DEBUG HOLD command was used to suspend execution of the procedure.
'PROFILE SETTING NEWHOLD=YES' indicates that the DEBUG SET NEWHOLD=YES command has been entered to cause all new NCL processes to be suspended when they begin execution.
'STEP STMT LIMIT BEING REACHED' indicates that the DEBUG STEP command was used to cause a specific number of statements in the NCL process to be executed before suspending the process.
'STEP STMT NUMBER BEING REACHED' indicates that the DEBUG STEP command was used and that it specified the statement number at which execution was to be suspended.
'PROCEDURE ENTRY' indicates that a DEBUG STEP NEXT=ENTRY command has been entered to allow execution of an NCL process until the next nested procedure entry, and the procedure entry has occurred.
'PROCEDURE EXIT' indicates that a DEBUG STEP NEXT=ENTRY command has been entered to allow execution of an NCL process until the next procedure exit, and the procedure exit has occurred.
System Action:
Execution of the NCL process is suspended.
User Action:
The DEBUG RESUME and DEBUG STEP commands may be used to continue execution of the NCL process.
Reason:
The DEBUG CALLTRC command can be used to turn 'procedure call tracing' on. This causes this message to be issued to the debugging user when a nested procedure call is made by an NCL process which is executing under the control of NCL/DEBUG. If the new nesting level is also a new METHOD LEVEL, the new method level is displayed on the end of the
System Action:
User Action:
Reason:
The DEBUG CALLTRC command can be used to turn 'procedure call tracing' on. This causes this message to be issued to the debugging user when a nested procedure call returns to a previous nesting level in an NCL process which is executing under the control of NCL/DEBUG. If the return is a change in METHOD LEVEL, the new method level is placed on the end of the message.
System Action:
None.
User Action:
None. See also the DEBUG SET CALLTRC= operand.
Reason:
An &PAUSE statement has been detected in an NCL procedure.
System Action:
Processing for the procedure is suspended.
User Action:
Enter GO, END or FLUSH as required to resume or cancel processing of the procedure.
Reason:
An &WAIT STRING statement has been detected in an NCL procedure.
System Action:
Processing for the procedure is suspended, awaiting the arrival of a message containing the specified string aaaaaaaaa.
User Action:
The SHOW PAUSE command can be used to display the expected string.
Reason:
An &WAIT statement has been detected in an NCL procedure.
System Action:
Processing for the procedure is suspended awaiting the arrival of the specified message aaaaaaaaa.
User Action:
None.
Reason:
If &INTCMD is used to EXECute a dependent process, the dependent process cannot include procedures that issue WAIT statements.
System Action:
The procedure terminates.
User Action:
Correct the procedure and retry.
Reason:
During NCL procedure processing an &PAUSE statement was found following an &WAIT statement. The &WAIT must be followed by a command. An &PAUSE statement is invalid.
System Action:
The statement is ignored.
User Action:
Correct the procedure and retry.
Reason:
During NCL procedure processing two successive &WAIT statements were found. An &WAIT statement requires a command other than &WAIT or &PAUSE to follow it.
System Action:
The &WAIT is ignored.
User Action:
Correct the procedure and retry.
Reason:
The return code from a VTAM RECEIVE request indicates a temporary error. SOLVE issues this message and pauses for 5 seconds before retrying the VTAM RECEIVE. VTAM feedback data (rc, fdbk, sense) is only provided if the error is other than temporary storage shortage.
System Action:
If the condition persists for four minutes, SOLVE will close the primary ACB and go into re-open processing after a further five seconds.
User Action:
Refer the problem to your systems administrator.
Reason:
An invalid RPL has been passed to SOLVE via the primary ACB. The reason indicates the failing condition and may be one of the following:
NO VTAM CID PRESENT - The communication identifier is not set in the RPL.
INVALID VTAM CID PRESENT - The communication identifier set does not match that related to the passed user correlator data.
NO USER CORRELATOR RETURNED - The user correlator expected by SOLVE is not set in the RPLUSFLD.
System Action:
The input is ignored. Messages N04203 and N04204 are issued containing a dump of the RPL and RU.
User Action:
Report the problem to your systems administrator.
Reason:
An invalid RPL has been passed to SOLVE via the primary ACB. This message is issued dumping the RU associated with the failing request. Message N04202 is issued detailing the reason for the rejection.
System Action:
Associated message N04204 is produced dumping the failing RPL.
User Action:
Record the data for problem resolution.
Reason:
An invalid RPL has been passed to SOLVE via the primary ACB. This message is issued dumping the RPL associated with the failing request. Message N04202 is issued detailing the reason for the rejection.
System Action:
None.
User Action:
Record the data for problem resolution.
Reason:
Input received from LU luname was longer than 32K bytes. This is inconsistent with the type of data normally received from the type of LU.
System Action:
The LU is disconnected from SOLVE.
User Action:
Investigate the cause of the overlength input. The most likely cause is a failure of the terminal microcode or control program.
Reason:
A VTAM SEND, used to send a response, failed with the return code, feedback and sense codes shown.
System Action:
The error is ignored.
User Action:
Determine the cause of the failure with reference to the appropriate VTAM manual.
Reason:
A command other than START, MODIFY or STOP was received through the system console `MODIFY' command interface.
System Action:
The command is ignored.
User Action:
Refer this situation to your systems administrator.
Reason:
A system STOP (P) command was received from the system console.
System Action:
The command is rejected.
User Action:
Use the FSTOP command through the `MODIFY' command interface.
Reason:
Parameters specified on the START command when running SOLVE as a started task are ignored.
System Action:
SOLVE parameters are taken from the PARM field of the procedure JCL.
User Action:
None.
Reason:
An attempt to use an OCS command through a system console has failed because the console userid, for example SYSOPER, does not have OCS access privilege.
System Action:
The command is rejected.
User Action:
None.
Reason:
A MODIFY command entered at the indicated console caused SOLVE to attempt to sign the console on. The indicated user ID was not a valid SOLVE user. The signon thus failed.
System Action:
The signon fails and the command is ignored.
User Action:
Define the user ID if required.
Reason:
A command entered from a system console is rejected because the userid definition of the user associated with the console is not profiled with OCS authority.
System Action:
None.
User Action:
If necessary, redefine the console userid to have OCS authority.
Reason:
The SHOW LICENCE command is now obsolete and will be withdrawn in a future release. Use the STATUS command to display the system CPU and product status information.
System Action:
None
User Action:
None
Reason:
The SOLVE optional feature indicated by feature_name is about to expire or has already expired.
System Action:
None.
User Action:
Contact your product support representative.
Reason:
SOLVE has detected that some features will expire within the next thirty (30) days. A message N04E01 will be on the SOLVE log for each of the features due to expire. This message will be issued every night until the system is refreshed with a new license.
System Action:
Processing continues.
User Action:
Check the SOLVE log for the list of features due to expire and contact your product support representative.
Reason:
Release of the specified logical unit failed with the specified error information.
System Action:
None. The terminal may not be properly disconnected.
User Action:
Refer to the VTAM Programming manual for explanation of the error codes.
Reason:
A logon request was received from a logical unit that was not defined as another SOLVE system and that does not have BIND parameters indicating it to be a supported terminal type. This may include an LU-1 terminal attempting to logon to SOLVE by bypassing EASINET.
System Action:
The logon is rejected.
User Action:
If the device attempting to logon is a supported device type, or an application simulating a supported device, ensure that the correct LOGMODE table entry is specified on the device definition.
Reason:
The specified LU has been unexpectedly disconnected.
System Action:
None.
User Action:
Refer to the VTAM Programming manual for the cause of the LOSTERM event. The OPNDST command can be used to re-acquire the LU if necessary.
Reason:
A remote system attempted to establish a session with the system that issued this message, but during the connection process a VTAM OPNSEC or SESSIONC macro failed with the indicated error codes.
System Action:
The session is not established.
User Action:
Determine the cause of the error from the appropriate VTAM Programming manual.
Reason:
The ACBs have closed because VTAM is terminating or the primary APPL has
System Action:
Waits for a reply.
User Action:
Restart VTAM or activate the APPL definition and reply as appropriate.
Reason:
The ACBs have been closed because VTAM is terminating or the primary
System Action:
Waits for 30 seconds before attempting to reopen the ACBs.
User Action:
None.
Reason:
The system ACB has been successfully re-opened following an earlier N05901 message.
System Action:
Processing resumes.
User Action:
None.
Reason:
The VTAM PPO ACB has been closed and SOLVE is no longer receiving PPO messages. PPO messages are sent by VTAM to the system console.
System Action:
None.
User Action:
Use the PPO START command to restart the PPO interface if necessary.
Reason:
A CLSDST macro, issued for the terminal luname shown, received from VTAM the non-retryable return codes displayed in the message.
System Action:
CLSDST processing continues, but the terminal may not be successfully disconnected from SOLVE.
User Action:
Investigate the error condition.
Reason:
A VTAM macro -aaaa is CLSDST or TERMSESS - has failed because of a VTAM temporary storage shortage. This message will be automatically repeated at one minute intervals while the shortage persists.
System Action:
The VTAM function is retried every five seconds.
User Action:
If the message persists investigate the cause of the VTAM storage shortage.
Reason:
An error has been detected in the datastream for LU luname. The offset into the datastream before compression is given by pos1 which corresponds to the offset pos2 in the datastream after compression. The code cc is a 3270 control character order, which can be determined from the 3270 Component Description Manual.
System Action:
Compression is aborted, and a snapshot of the datastream is sent to the log.
User Action:
Determine the cause of the error.
Reason:
This message follows N06701. An error having been detected, a snapshot of the offending datastream, is written to the log to facilitate in determination of the problem.
System Action:
None.
User Action:
Determine the cause of the error.
Reason:
Tracing of LU luname has been requested using the LUTRACE command.
System Action:
The data for LU luname will be traced based on the SYSPARMS TRACEOPT values.
User Action:
None.
Reason:
This line contains the trace data as requested at offset off. The data is formatted in hex on the left and character format on the right.
System Action:
None.
User Action:
None.
Reason:
Denotes the end of tracing for this datastream.
System Action:
None.
User Action:
None.
Reason:
The panel being processed has exceeded the size of the internal processing buffer and has been truncated.
This may be caused by a panel that contains an excessive number of attribute bytes which has resulted in a datastream being generated that exceeds the internal buffer which is 8K- 12 bytes (by default) or as set by the SYSPARMS PANLBFSZ operand.
System Action:
Processing continues, however processing may be impacted by the truncation of the panel.
User Action:
Determine the cause for the error. If necessary re-organize the panel to reduce the number of fields and attribute bytes. Alternatively, use SYSPARMS PANLBFSZ to increase the internal buffer size for panel support. If the problem persists report it to your product support representative.
Reason:
This is the heading message for a SHOW INDEX command. One or more N06B02 messages follow. The heading identifies the messages contents with the following meaning. NAME is the index name, identifying the index type. ADDED and DELETED are counts of all entries ever added to or deleted from the index. CURRENT is a count of current entries in the index. The remaining fields are internal debug guides. #SEQ is the number of sequence set elements, #INDX the number of index elements, DEPTH is the current depth of the index elements, REORG is the number of times a reorg has occurred, FREESPC is the amount of free space in the index.
System Action:
None.
User Action:
None.
Reason:
This is the detail line of a SHOW INDEX command. Its contents are explained under the heading message N06B01.
System Action:
None.
User Action:
None.
Reason:
This terminates a SHOW INDEX message sequence and provides a count of the number of name index sets processed. aaaa = count of index sets processed.
System Action:
None.
User Action:
None.
Reason:
The number of Non-Roll Delete messages received has exceeded the hold limit and as a result one or more have been lost.
System Action:
The NRD messages are discarded.
User Action:
Some of the NRD messages currently being retained should be deleted so the queue can accept more NRD messages, otherwise the losses will continue. The SYSPARMS NRDLIM operand can be used to increase the limit.
Reason:
The number of Non-Roll Delete messages received has reached or exceeded 75% the hold limit.
System Action:
None.
User Action:
When the hold limit is reached, message N06D01 will be issued; refer to message N06D01 above.
Reason:
SOLVE has opened a session with terminal luname . This message is issued only if the SYSPARMS CONMSG=YES command has been issued.
System Action:
None.
User Action:
None.
Reason:
Connection of terminal aaaaaaaa has failed. errdescr describes the error which occurred.
System Action:
The terminal is not connected.
User Action:
From the error description, determine the cause of the error.
Reason:
A Fullscreen terminal session has been rejected by the device aaaaaaaa. The M2RETRY system parameter setting indicates that the system should automatically retry session establishment using a default screen size. This message is logged and indicates that the session request is to be reissued using the default screen size.
System Action:
A session is requested with the named device using a default model 2 logmode.
User Action:
None.
Reason:
The connection attempt for the specified logical unit failed because the terminal is already in session with another application.
System Action:
None.
User Action:
Reissue the OPNDST command requesting the owning application to release the terminal.
Reason:
A SYSPARMS MAIMDTAB command was previously specified to provide a supplied mode table for MAI sessions. An attempt was made to match the bind parameters for the logical unit, LUNAME aaaaaaaa, with an entry in the supplied table but no match was found.
System Action:
The logmode table name is ignored.
User Action:
Check the user logmode table.
Reason:
An error occurred when a message was sent to the specified terminal. The codes given are the RPL return codes following the send.
System Action:
The session is ended.
User Action:
Refer to the VTAM Programming manual for explanation of the error codes.
Reason:
An attempt to read input from a terminal has failed because the terminal is powered off. On non-SNA terminals this condition may only be detected when the terminal is powered on again.
System Action:
If this occurs in an active user region then a disconnection is performed. If an EASINET terminal then the EASINET procedure is redriven.
User Action:
Logoff to release system resources before powering off the terminal. A subsequent reconnection may be performed to resume the interrupted work.
Reason:
The system was unable to correlate an input from the screen with an active function. Pressing CLEAR will ensure synchronisation of processing.
System Action:
The input is ignored.
User Action:
Hit the Clear key to redisplay the current screen image and re-enter the data.
Reason:
Tracing of the inbound datastream has been requested for LU luname via the LUTRACE command.
System Action:
The inbound datastream will be traced.
User Action:
None.
Reason:
This message is preceded by N07503. This message contains the requested trace data from the specified LU.
System Action:
The datastream is logged.
User Action:
None.
Reason:
Denotes the end of tracing for this datastream.
System Action:
None.
User Action:
Tracing can be terminated using the LUTRACE command.
Reason:
This message will appear whenever any messages are discarded because the limit to the number of messages that can be held for this OCS Operator has been exceeded. If the OCS window is not fully closed, the 'MSGS LOST' caption will be displayed above the command entry line to warn that messages are being discarded.
System Action:
One or more messages are discarded and processing continues. The hold limit is imposed to avoid excessive storage being allocated to queued messages.
User Action:
The number of messages that will be held is determined by the HOLD operand of the PROFILE command. A value in the range 10 to 999 can be specified by the user. By default 200 messages will be held. Refer to the PROFILE command for more information.
Reason:
A message flagged as a Delete Operator Message does not contain a DOM identifier component.
System Action:
DOM processing is not performed.
User Action:
Determine if an NCL process has incorrectly generated or modified a DOM message. In particular, ensure that MSGPROC processing is not deleting the DOMID component when propagating messages.
Reason:
The NCL procedure specified has resumed processing because the character string specified on an earlier &WAIT statement has been received.
System Action:
NCL procedure processing resumes.
User Action:
None.
Reason:
The region indicated, luname, has been processed for termination.
System Action:
The region is terminated.
User Action:
None.
Reason:
The CLSDST command has been issued to terminate the session between the LU 'luname' and SOLVE. The session is already being terminated and this message is sent to the user to notify them.
System Action:
The CLSDST command is ignored. Termination of the session between the LU and SOLVE continues.
User Action:
None.
Reason:
A VTAM SEND to a terminal connected to SOLVE has failed with Return Code, Feedback and Sense values as shown. This message precedes a hexadecimal dump of the datastream (see messages N08503 and N08504).
System Action:
None.
User Action:
Contact your systems administrator to have the source of the datastream error located.
Reason:
A VTAM SEND to an LU connected to SOLVE has failed, with Return Code, Feedback and Sense codes shown in message N08502. The dump of the datastream being sent is contained in the N08503 messages following message N08502.
System Action:
None.
User Action:
Contact you systems administrator to have the source of the datastream error located.
Reason:
This message terminates the hexadecimal dump of a datastream which was being sent to an LU connected to SOLVE when a VTAM SEND fails. Refer to message N08502 for return code, Feedback and Sense code information.
System Action:
None.
User Action:
Contact your systems administrator to have the source of the datastream error located.
Reason:
A VTAM RECEIVE for an exception response associated with a terminal connected to SOLVE has failed with the indicated Return Code, Feedback.
The occurrence of this message indicates an abnormal condition in the VTAM API. A SEND request has failed with an X'0C0D' sense code indicating an error in chain. The RECEIVE request issued to process the associated exception response has failed.
System Action:
If the terminal is still in session the failing SEND operation is retried.
User Action:
If the condition continues notify your product support representative and supply them with the error information.
Reason:
When a procedure issues a command using the &INTCMD statement, there is a limit to the number of messages queued to the procedure's dependent response queue or dependent request queue as a result of command or other process execution. This limit, with a default of 32767, is set in the NMIQLIM parameter. If this limit is exceeded as a result of messages queued to a process's &INTREAD queues, this message is queued as the NMIQLIM + 1 message.
NMIQLIM affects the number of messages queued to &PROMPT environments and to the total number of Remote Operator Facility (ROF) messages
System Action:
One or more messages are discarded and processing continues. The hold limit is imposed to avoid excessive storage being allocated to queued messages. Messages are discarded until the queue depth drops below
User Action:
Reason:
This message acknowledges that a request by the user with the userid shown to reconnect to a previously disconnected user region has been successful.
System Action:
The user's terminal is connected to the disconnected region.
User Action:
Continue using the reconnected region.
Reason:
This message acknowledges that the DISCONN command or session failure has caused the disconnection of a user region. The reconnection identifier nnnnn and userid show the user who has been disconnected. This message is written to the activity log only.
System Action:
The user region has been disconnected.
User Action:
To reconnect to the region at a later stage, use the RECONN command.
Reason:
A reconnection for the user P2 has completed successfully. P1 is the terminal name of the disconnected region.
System Action:
The terminal is connected to the disconnected region.
User Action:
Press the Enter key to resume processing.
Reason:
An attempt has been made to reconnect to a session which was disconnected from a terminal with different physical characteristics (eg. previous session was an LU2 terminal and reconnection was attempted from an LU-1 terminal). The reconnection attempt has been rejected.
System Action:
The reconnection attempt has been rejected.
User Action:
Try reconnecting from a device with characteristics similar to those which the original terminal possessed.
Reason:
An attempt was made to reconnect to a disconnected session, but the reconnection failed because either the current or original region was terminating.
System Action:
The reconnection attempt is rejected.
User Action:
None.
Reason:
This message appears on VOS3 systems only. It confirms that terminal aaaaaaaa which is currently connecting to SOLVE is a bbbbbb device type. bbbbbbb is either 3270 or 560/20.
System Action:
None.
User Action:
None.
Reason:
Tracing of outbound datastreams to LU luname has been requested. If compression was requested, this datastream is after compression has been performed. ccc is either FIC, LIC, MIC or OIC, indicating a first, last, middle or only in chain message.
System Action:
The datastream is traced to the activity log.
User Action:
Tracing may be terminated by use of the LUTRACE command.
Reason:
This message is preceded by N09003. This is the trace of the outbound datastream to the specified LU.
System Action:
None.
User Action:
Tracing may be terminated by the LUTRACE command.
Reason:
Denotes the end of the trace messages for this datastream.
System Action:
None.
User Action:
None.
Reason:
A split screen operation was attempted which would provide a window of insufficient size for the current function. Certain functions require a minimum sized window for their operation, for example OCS mode. Minimum requirements apply if an OCS mode screen is executing an NCL procedure in fullscreen mode.
System Action:
If the error occurs when attempting to split a screen being operated by an NCL procedure that is operating as a full screen processor out of OCS mode the screen split will be ignored and this message will be queued for display when the procedure reverts to standard OCS mode of operation.
User Action:
Select a larger window size.
Reason:
VTAM SPO message receipt has stopped. This is typically due to a VTAM error indicated in the previous message N09B02. If, however, the SPO interface has been stopped, no N09B02 will have been issued.
System Action:
The VTAM SPO interface is inactive.
User Action:
Refer to message N09B02.
Reason:
A RCVCMD macro failed when issued to receive VTAM SPO messages. The error codes are explained in the appropriate VTAM Programming manual.
System Action:
Replies can no longer be received to VTAM commands.
User Action:
Determine the cause of the failure by referring to the VTAM Programming manual. Restart SOLVE. The SPO interface may be restarted using the SPO START command.
Reason:
A RCVCMD macro failed when issued to receive VTAM SPO messages because of a VTAM storage shortage.
System Action:
Replies can no longer be received to VTAM commands.
User Action:
SOLVE will continue to issue the RCVCMD macro every 5 seconds until an SPO STOP command is entered or until the storage shortage is relieved.
Reason:
The NCL verbs &PPOREAD, &PPODEL, &PPOCONT and &PPOREPL are valid only if issued from PPOPROC.
System Action:
The procedure terminates.
User Action:
Correct and retry.
Reason:
An invalid VTAM message number has been specified on the &DEFMSG NCL statement.
System Action:
The PPOPROC NCL procedure is terminated. Standard PPO and SPO messages delivery is resumed.
User Action:
Correct the NCL procedure and restart PPOPROC.
Reason:
VTAM PPO message receipt has stopped due to a VTAM error. This message will follow N09B02 which details the VTAM error.
System Action:
The VTAM PPO interface is inactive.
User Action:
Refer to message N09B02.
Reason:
A RCVCMD macro failed when issued to receive VTAM PPO messages. The error codes are explained in the appropriate VTAM Programming manual.
System Action:
The VTAM PPO ACB is closed, so no more unsolicited messages will be received from VTAM.
User Action:
Determine the cause of the failure by referring to the VTAM Programming manual. Use the PPO START command to re-open the ACB, or restart SOLVE.
Reason:
The SOLVE PPO ACB has been opened successfully.
System Action:
VTAM PPO messages will now be routed to those operators authorized to receive them.
User Action:
If you do not wish to receive PPO messages at this stage, the PROFILE command PPO=NO operand can be used to suppress them.
Reason:
The SOLVE PPO ACB failed to open. The code specified is the value of ACBERFLG following the OPEN.
System Action:
None.
User Action:
Determine the cause of the error by referring to the appropriate VTAM Programming manual. When corrected, issue a PPO START command to retry the operation.
Reason:
Signifies that SOLVE has closed its PPO ACB and stopped receiving PPO messages.
System Action:
None.
User Action:
PPO may be started by the PPO START command.
Reason:
The system's primary ACB did not open for the stated reason code. The code is the value of the ACBERFLG following the OPEN macro.
System Action:
Waits for a reply of RETRY or END.
User Action:
Reply as required. Refer to the VTAM Programming manual for a description of ACB open error codes.
Reason:
The system's primary ACB did not open for the stated reason code. The code is the value of the ACBERFLG following the OPEN macro. The system retries every nn seconds (the default value is 30) if SYSPARMS ACBRETRY is set or defaulted to YES.
System Action:
The system automatically retries the open attempt every nn seconds.
User Action:
Refer to the VTAM Programming manual for a description of ACB open error codes.
Reason:
The primary ACB has successfully opened. This message is normally issued during initialization but may also be issued if VTAM is restarted or the primary ACB varied inactive and active.
System Action:
Communication between SOLVE and VTAM is now possible.
User Action:
None.
Reason:
This message appears in the log during system initialization. It displays the installation VTAM level information. VTAM LEVEL is the version of VTAM your system is running on. COMPID displays the component name returned by VTAM, and FUNC STRING the function vector data converted to hexadecimal display.
System Action:
None.
User Action:
None.
Reason:
This message appears in the log during system initialization. It indicates that VTAM generic resources are not supported in this environment, and that the SYSPARMS GENRSRC=name command was entered.
System Action:
The generic resource name is ignored.
User Action:
Remove the SYSPARMS GENRSRC command from the NMINIT deck.
Reason:
This message is written to the activity log during initialization when an attempt to activate the requested generic resource fails. The VTAM return code (RTNCD) and feedback (FDB2) information is displayed ( P1 ).
Note: RTNCD=X'10' (16) and FDB2=X'19' (25) is described in message N09708.
System Action:
The generic resource is ignored and the SYSPARM value is cleared.
User Action:
Investigate the failure information. VTAM RTNCD and FDB2 codes are documented in the IBM Communications Server SNA Programming guide. When the problem has been resolved, recycle the region to reactivate the generic resource.
Reason:
An attempt to set the VTAM Generic Resource System Parameter (GENRSRC) to NO failed.
System Action:
The region remains registered to the VTAM Generic Resource and the GENRSRC system parameter remains unchanged.
User Action:
It is likely that there is an operating system issue in the parallel sysplex. Investigate the failure reason codes to determine the cause of the problem.
Reason:
This message is written to the hardcopy log during initialization when an attempt to activate the requested generic resource fails. A generic resource is activated using the SETLOGON macroinstruction but this activation has failed with RTNCD=X'10' (16) and FDB2=X'19' (25). These values indicate that the coupling facility for this host is not accessible.
The coupling facility may be inaccessible because:
System Action:
The generic resource is ignored and the SYSPARM value is cleared.
User Action:
Determine why the coupling facility is inaccessible. When this has been resolved, recycle the region to reactivate the generic resource.
Reason:
The region with ACB, P1, has successfully registered as the generic resource P2.
System Action:
Users logging on to the generic resource, P2, can be directed to this region.
User Action:
Check the status of the $NM SSI parameter group to help ensure that the region is able to communicate with other members of the generic resource group.
Reason:
A RCVCMD macro failed when issued to receive VTAM SPO or PPO messages (xxx is SPO or PPO) because of a VTAM storage shortage.
System Action:
Replies can no longer be received to VTAM commands.
User Action:
SOLVE will continue to issue the RCVCMD macro every 5 seconds until an SPO STOP or PPO STOP command is entered or until the storage shortage is relieved.
Reason:
A RCVCMD macro failed when issued to receive VTAM SPO or PPO messages (xxx is SPO or PPO). The error codes are explained in the appropriate VTAM Programming manual.
System Action:
Replies can no longer be received to VTAM commands.
User Action:
Determine the cause of the failure by referring to the VTAM Programming manual. Restart SOLVE. The appropriate interface may be restarted using the SPO START or PPO START command.
Reason:
An attempt to obtain storage to pass a PPO or SPO message to PPOPROC has
System Action:
User Action:
Reason:
The PPO queue limit has been reached. This may occur if PPOPROC is not clearing messages from the PPO queue quickly enough and may indicate
System Action:
No more PPO messages are queued to PPOPROC until the queue length drops
User Action:
Determine which statement PPOPROC is executing using the SHOW NCL command. If it is held up on one particular statement, review PPOPROC
Reason:
An ISR command for unsolicited VTAM message traffic on the specified link has been accepted and is the process of being established. Additional message(s) will follow to indicate whether the establishment was successful or not.
System Action:
None.
User Action:
None.
Reason:
Contact with a remote PPO system has been successfully established across an an ISR link.
System Action:
None.
User Action:
None.
Reason:
Contact with a remote PPO system across an an ISR link has been lost. PPO messages can not flow between the two systems. This is probably due to the INMC link becoming disabled.
System Action:
PPO ISR traffic is suspended on this link. The ISR link will be automatically restarted following a link failure.
User Action:
Determine the cause of the link failure.
Reason:
This message is issued as a part of the SHOW ISR command. The current settings of the local, remote, and actual ISR/PPO conversation are shown. This includes the message attribute option, whether PPO message are sent/received, whether SPO message are sent/received, and whether VTAM (SPO) commands are sent/received.
System Action:
None.
User Action:
Refer to the description of the PPO options of the ISR command.
Reason:
This message is issued as a part of the SHOW ISR command. The current settings of the local, remote, and actual ISR/PPO conversation are shown. This includes whether VTAM (SPO) commands are sent/received, and the setting of the DELIVER option.
System Action:
None.
User Action:
Refer to the description of the PPO options of the ISR command.
Reason:
The option specified on the ISR ENA=PPO OPTION DELIVER= operand was invalid. Valid operands are PPO, LOCAL, REMOTE, ALL, or DEFMSG.
System Action:
The ISR command is ignored.
User Action:
Refer to the description of the PPO options of the ISR command and correct the operand.
Reason:
The DEFMSG= operand is no longer supported on the ISR PPO command.
System Action:
DEFMSG=ASIS will be changed to mean DELIVER=PPO, and DEFMSG=LOCAL will be changed to DELIVER=DEFMSG.
User Action:
Refer to the description of the PPO options of the ISR command.
Reason:
This message is the heading for a group of messages issued as a result of the SHOW DEFMSG command. It is followed by multiple occurrences of message N09K02 which detail individual VTAM message numbers. The fields in each line are: VTAM MSG# The VTAM message number. This is a message number, or message number range, and corresponds to message ISTnnnI or JCEnnnI. For DOS/VSE prior to VTAM R3.2 it is the 5AnnI to 5JnnI equivalent. Refer to the VTAM Messages and Codes manual. PPOPROC, LOCAL, REMOTE YES or NO. Show the message delivery indicators for PPOPROC, LOCAL, and remote destinations which have been set using the DEFMSG command, or which are set in the default message table
DEFAULT YES or NO. Indicates whether this message number is in the default table supplied by SOLVE.
ACT YES or NO. Indicates whether a DEFMSG SET command was issued for this message.
EVENTNAME SNA event name suffix for EDS event notification.
System Action:
None.
User Action:
None.
Reason:
Part of the SHOW DEFMSG display.
System Action:
None.
User Action:
Refer to message N09K01.
Reason:
This message is the heading for the SHOW PPOSTAT display. Message N09K05 follows.
Headings are:-
PPO-RCV The number of message lines received on the
PPO ACB. SPO-RCV The number of message lines received via the SPO interface.
Q-PPOPROC The number of message lines queued to PPOPROC.
#-PPOCONT The number of implicit or explicit PPOCONTs issued.
#-PPODEL The number of PPODELs issued.
#-LOCAL The number of PPO messages delivered to local receivers.
System Action:
None.
User Action:
None.
Reason:
This message is contains details for the SHOW PPOSTAT command. It follows message N09K04 which contains the headings.
System Action:
None.
User Action:
See message N09K04.
Reason:
A SHOW DATACOM command was unable to obtain storage. The command requires approximately 12 KB of storage to process.
System Action:
The command is not processed.
User Action:
Increase the region size to at least 12 KB.
Reason:
A SHOW DATACOM command was entered but could not be processed. The CA Datacom API module, DBSVWPR, could not be loaded during region initialization. The LOAD macro returned a nonzero return code in register 15.
p1 is the return code, and p2 is the failure reason code.
System Action:
The command is not processed.
User Action:
Ensure that the CAILIB data set allocated to STEPLIB is for the latest release of CA Datacom installed.
Reason:
A SHOW DATACOM command was entered but could not be processed. The CA Datacom API module, DBSVWPR, could not be loaded during region initialization.
System Action:
The command is not processed.
User Action:
Ensure that the CAILIB data set allocated to STEPLIB is for the latest release of CA Datacom installed.
Reason:
A SHOW DATACOM command was entered. The CA Datacom API module, DBSVWPR, returned a nonzero return code in register 15.
System Action:
The command is not processed.
User Action:
Ensure that the CAILIB data set allocated to STEPLIB is for the latest release of CA Datacom installed.
For assistance, contact Technical Support.
Reason:
A SHOW DATACOM command was entered but could not be processed. The CA Datacom API module, DBNTRY, returned a nonzero return code in
Register 15.
p1 is the decimal return code, and p2 is the decimal internal code.
System Action:
The command is not processed.
User Action:
For information about the return code, see Message Guide for CA Datacom.
For assistance, contact Technical Support.
Reason:
A SHOW DATACOM command was entered. This is the heading line for the list of DATACOM systems displayed in following messages.
System Action:
The N0D209 messages list DATACOM instances.
User Action:
None.
Reason:
A SHOW DATACOM command was entered. This shows the detail of a DATACOM instance.
System Action:
None.
User Action:
None.
Reason:
A SHOW DATACOM command was entered. This is the detail line for the TABLE=IDENTITY operand.
System Action:
None.
User Action:
None.
Reason:
A SHOW DATACOM command was entered. This is the detail line for the TABLE=DATABASES operand.
System Action:
None.
User Action:
None.
Reason:
A SHOW DATACOM command was entered. This is the detail line for the TABLE=DATASETS operand.
System Action:
None.
User Action:
None.
Reason:
A SHOW DATACOM command was entered. This is the detail line for the TABLE=TABLES operand.
System Action:
None.
User Action:
None.
Reason:
A SHOW DATACOM command was entered. This is the heading line for the TABLE=IDENTITY operand.
System Action:
The N0D210 messages list the MUF details.
User Action:
None.
Reason:
A SHOW DATACOM command was entered. This is the heading line for the TABLE=DATABASES operand.
System Action:
The N0D211 messages list the details of each database for the MUF.
User Action:
None.
Reason:
A SHOW DATACOM command was entered. This is the heading line for the TABLE=DATASETS operand.
System Action:
The N0D212 messages list the details of each data set for the MUF.
User Action:
None.
Reason:
A SHOW DATACOM command was entered. This is the heading line for the TABLE=TABLES operand.
System Action:
The N0D213 messages list the details of each table for the MUF.
User Action:
None.
Reason:
A SHOW DATACOM=mufname command was entered. The version of the targeted CA Datacom is not supported.
System Action:
The command is not processed.
User Action:
For assistance, contact Technical Support.
Reason:
A SHOW DATACOM=mufname command was entered. The loaded CA Datacom API module, DBSVWPR, does not support the targeted version of MUF.
System Action:
The command is not processed.
User Action:
Ensure that the CAILIB data set allocated to STEPLIB is for the latest release of CA Datacom installed.
For assistance, contact Technical Support.
Reason:
The command string entered exceeded the internal processing buffer size; this can occur with the use of long Prefix PFKs or commands entered within NCL procedures. This message is also issued if an attempt is made to ROUTE a command to a system which does not support commands longer than 256 bytes.
System Action:
The excess command text is discarded.
User Action:
Change the command to operate within system limits.
Reason:
Recursive command execution has been detected. This may be because CMDREPLs or EQUATEs have been constructed in a way that cause a command to be executed recursively.
System Action:
Command execution is aborted.
User Action:
Remove the recursive command definitions.
Reason:
The execution of an SOLVE command failed because the command's processing load module ( aaaaaaaa ) could not be loaded for the indicated reason.
System Action:
The command is ignored.
User Action:
Check that the indicated load module is in a dataset that is included in your run-time load library concatenation.
Reason:
The command string cccccccc was not recognized as a valid system command.
System Action:
The command string is ignored.
User Action:
Determine why the command is incorrect. This error may result from the execution of an NCL statement which has invalid syntax, perhaps resulting from an unexpected null variable. In such cases, if a statement is not recognized, the product region attempts to execute it as a command or as an equated command string, which may in turn result in this error. If this is the case, correct the NCL procedure and retry. The &CONTROL TRACE statement may help in determining the source of errors within an NCL procedure.
Reason:
Certain commands can be accepted only when they form part of an NCL procedure or are entered from a particular operating mode.
System Action:
The cccccccc command is rejected.
User Action:
Refer to the description of the rejected command.
Reason:
Issued in response to an LTITLE command.
System Action:
The new LOGO title becomes immediately effective.
User Action:
None.
Reason:
The aaaaaaa command issued from a dependent environment is not supported from this source. For example fullscreen commands such as K, PAGE, and CLEAR.
System Action:
The command is rejected.
User Action:
Correct the NCL procedure issuing the INTCMD or executing under a dependent environment.
Reason:
The command entered is not a valid command under this operating system.
System Action:
The command is rejected.
User Action:
None.
Reason:
A command string was abbreviated to the point at which it cannot be uniquely interpreted.
System Action:
The command string cccccccc is rejected.
User Action:
Re-enter the relevant command with further qualification to make it unique or invoke the online help facility for further information.
Reason:
The user is not authorized to issue the command.
System Action:
The command is rejected.
User Action:
Userid authorization is set in the userid definition. Authorization may be raised by authorized personnel.
Reason:
An invalid operand was specified on the AUTOHOLD command. Valid operands are ON, OFF, AUTO, NOAUTO or blank.
System Action:
The command is ignored.
User Action:
Refer to the description of the AUTOHOLD command for correct syntax.
Reason:
This confirms that AUTOHOLD type is set to the given status, where type is MODE or AUTO and status is ON or OFF.
System Action:
If AUTOHOLD is set on, the window will be `frozen' whenever the last line is filled, necessitating operator action to view any further messages.
User Action:
None.
Reason:
A TITLE command has been processed.
System Action:
The new Operator Control Services title line has been set.
User Action:
Press the CLEAR key to view the new title.
Reason:
The requested NCL procedure name procname is longer than 8 characters or it contains invalid characters.
System Action:
The command is rejected.
User Action:
Correct the procedure name and re-enter.
Reason:
The command is not valid for entry in this mode.
System Action:
The command is rejected.
User Action:
Refer to the command description for restrictions on its use.
Reason:
The command is not valid for entry by a system console environment.
System Action:
The command is rejected.
User Action:
Reissue the command from a standard user environment, For example from Operator Console Services. Alternatively, if executing NCL, then correct the procedure to not issue the command.
Reason:
The specified USERID has issued a LOGSWAP command.
System Action:
The current log will be closed and the next available one opened.
User Action:
None.
Reason:
A LOGSWAP command is rejected because no further logging can take place.
System Action:
The command is rejected.
User Action:
Should logging be required, SOLVE must be terminated and restarted.
Reason:
A command was ROUTED to a remote SOLVE system via the Remote Operator Facility, but the command is one that can be executed only in the local system.
System Action:
The command is rejected.
User Action:
None.
Reason:
An `X' (Exit) command was ROUTED to a remote SOLVE system, causing the user's ROF session to be terminated.
System Action:
None.
User Action:
None.
Reason:
The TITLE command contains invalid characters, possibly associated with entry from a DBCS capable terminal.
System Action:
The command is rejected.
User Action:
Correct and Retry. Ensure that the title text does not contain DBCS character strings.
Reason:
The command TITLE DBCS= was executed successfully to define a title that will be displayed on terminals that are DBCS capable.
System Action:
None.
User Action:
None.
Reason:
The TITLE DBCS= command was executed specifying a string that is longer than is acceptable for the command.
System Action:
The command is rejected.
User Action:
Refer to the TITLE command documentation.
Reason:
The LTITLE command has specified an invalid character stream as the logo title, possibly associated with entry from a DBCS capable terminal.
System Action:
The command is rejected.
User Action:
Ensure that the title text does not contain DBCS characters.
Reason:
The command LTITLE DBCS= was executed successfully to define a title that will be displayed on terminals that are DBCS capable.
System Action:
None.
User Action:
None.
Reason:
LTITLE DBCS= command was executed specifying a string that is longer than is acceptable for the command.
System Action:
The command is rejected.
User Action:
Refer to the LTITLE command documentation.
Reason:
The requested command is not valid once the system has commenced shutdown.
System Action:
The command is ignored.
User Action:
None.
Reason:
The entered command was not recognized by SOLVE as a valid command or equate name.
System Action:
The command is not executed.
User Action:
Correct the command and re-enter it.
Reason:
A CLSDST command specified an LU which is not connected.
System Action:
The command is rejected.
User Action:
None.
Reason:
An attempt was made to issue a CLSDST command to disconnect the system console aaaaaaaa from the system, but this is invalid as the console is not a VTAM terminal.
System Action:
The command is rejected.
User Action:
None.
Reason:
A CLSDST command was issued but the name of the terminal to be disconnected was omitted.
System Action:
The command is rejected.
User Action:
Retry, including the required terminal name.
Reason:
An OPNDST or CLSDST command was issued for a terminal whose name has an invalid length.
System Action:
The command is rejected.
User Action:
Correct the terminal name and re-enter.
Reason:
An invalid operand was specified on the OPNDST or CLSDST command.
System Action:
The command is rejected.
User Action:
See the description of the OPNDST command in the Command Reference.
Reason:
A CLSDST command specifying the WAIT=YES operand was entered and has been accepted. The command will complete when all messages queued for all terminals have been sent. The CLSDST command may be used with the GENERIC operand to affect multiple terminals. The number of terminals (nnn) is noted in the message.
System Action:
The command is accepted.
User Action:
None.
Reason:
A CLSDST command with the GENERIC operand has failed to match on any logical unit names.
System Action:
The command is ignored.
User Action:
Check the generic mask aaaaa and retry. Use the SHOW SESS or SHOW USERS commands to list the LUNAMES of terminals with which SOLVE has a session.
Reason:
A queued logon request for the specified LU has been cancelled by the CLSDST command.
System Action:
When the LU is connected to SOLVE it will be immediately discarded.
User Action:
None.
Reason:
A CLSDST command was rejected because your command authority restricts you to LU1 Printers. This message can arise when either:
- the luname specified is not an LU1 printer, or,
- you specified GENERIC.
System Action:
The command is rejected.
User Action:
Contact your systems administrator.
Reason:
This is the first line of the display issued as a result of a PROFILE command. userid is the name of the user currently logged on to this terminal which is known as termid.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display; shows the DD name that will be used by NCL when loading NCL procedures for this user ID. This is specified as part of the UAMS definition and allows users to reference different libraries.
System Action:
This library will only be used when loading procedures. If a preloaded copy of the procedure exists and your OCS profile specifies NCLTEST=NO, a copy of the preloaded procedure will be used.
User Action:
This ID can only be changed by altering your user ID definition.
Reason:
Part of the PROFILE display; shows the user's command authority level (x) and the status of the message (MSGPROC) NCL procedure associated with the user (zz) if any is defined. The MSGPROC can be `NOT DEFINED', `ACTIVE' or `INACTIVE'. Inactive means the procedure was loaded and initially active but has terminated at some stage either due to an error or because it logically ended and is no longer effective.
System Action:
None.
User Action:
If the MSGPROC NCL procedure is required and has failed, you must correct the procedure and either exit and re-enter Operator Control Mode or use the PROFILE MSGPROC command to reinstate the MSGPROC procedure.
Reason:
Part of the PROFILE display; indicates the status of the VTAMNUM profile option.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display; indicates whether the user will receive PPO messages, and if so, at what severity class. `yyyy' may be INFO, WARN, NORM or SER.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display; indicates the current roll-delay time for this OCS environment in seconds.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display; indicates the user's command stack size.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display; indicates the character used to form the roll-delimiter line.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display; indicates the number of messages which will be held for this window while the window is in HOLDING or AUTOHOLD state.
System Action:
None.
User Action:
None.
Reason:
Signifies the end of the PROFILE display.
System Action:
None.
User Action:
None.
Reason:
Confirms successful processing of a PROFILE command, aaaaaaa specifies the executing environment (CURRENT or PRIMARY).
System Action:
New PROFILE options are in effect.
User Action:
None.
Reason:
The value of the specified operand is invalid.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
The DELCHAR or NRDELCH characters cannot conflict with DBCS shiftin characters, value X`0E'.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
The user's USERID definition does not specify PPO authority, and therefore this attempt to change the user's profile to receive PPO messages is rejected.
System Action:
None.
User Action:
None.
Reason:
A PROFILE command was entered requesting that the user start receiving PPO messages but the system is not receiving PPO messages from VTAM at the moment.
System Action:
None.
User Action:
Determine whether the system should be receiving PPO messages, and if so issue a PPO START command.
Reason:
Part of the PROFILE display. Indicates that the user is privileged to receive Monitor messages.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. Indicates that no initial command is executed automatically when the user enters OCS mode.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. Indicates that an initial command is executed automatically when the user enters OCS mode.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. Indicates that when a command is entered from the OCS window command line the command text is (is not) retained on the command line.
System Action:
If CMDKEEP=NO is in effect commands will be erased from the command input line. In this case they will still be added to the command stack and can be retrieved in the normal manner.
User Action:
None.
Reason:
The text of the INITCMD operand of the PROFILE command must be enclosed in quotes.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
The INITCMD operand text is limited to 40 characters.
System Action:
The command is rejected.
User Action:
Reduce INITCMD text to 40 or fewer characters.
Reason:
A PROFILE MSGPROC= command has been issued by a user who does not have a command authority level high enough for this operand of the PROFILE command.
System Action:
The command is ignored.
User Action:
Refer to your systems administrator.
Reason:
Heading line within a PROFILE display.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. Indicates that no NPF command control member has been specified for the user. The user is entitled to issue VTAM commands referring to any network resource.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. Indicates that the user may issue VTAM commands that refer only to those network resources defined by the NPF tables associated with the command control member ccmem.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. Indicates that the user will not receive unsolicited VTAM messages.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. This provides a heading for the subsequent messages that describe which unsolicited messages will be sent to the user.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. Indicates that if unsolicited (PPO) messages are to be sent to the user, the messages concerned may refer to any network resource.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. Indicates that the user will receive all unsolicited (PPO) messages generated by VTAM.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. Indicates that the user will receive unsolicited messages that refer to network resources for which no logged-on operator is partitioned, or those that do not refer to any network resource.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. Indicates that the user will receive unsolicited (PPO) messages that refer to network resources defined by the NPF tables associated with message control member mcmem.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. Indicates that the user will/will not receive PPO messages referring to network resources outside their partition.
System Action:
None.
User Action:
None.
Reason:
The INITCMD operand of the PROFILE command cannot be entered from a terminal under control of EASINET or from a user region which does not have OCS access authority.
System Action:
The command is rejected.
User Action:
None.
Reason:
Part of the PROFILE display. MSGALARM specifies the number of times that the terminal alarm will be rung to notify the operator that a message has arrived at a closed OCS window. MSGALARM applies to all operational windows, including MAI, regardless of function.
System Action:
The alarm will be rung only the first time a message arrives. Subsequent arrival of additional messages will not cause the alarm to be rung.
User Action:
MSGALARM can be in the range 0 to 9. 0 indicates that the alarm is not to be rung.
Reason:
An attempt was made, using the PROFILE MSGCODE=mm command, to set additional bits in your msgcode profile that you are not entitled to set. The mask, mm, specifies 2 hexadecimal digits, 00-FF. The MSGCODE operand allows a user to specify a mask that is used to determine whether or not a user is to receive messages caused by an &WRITE MSGCODE=mm. If the bits set in xx are also set in the users msgcode profile mm then the message will be written to the screen.
System Action:
The command is rejected.
User Action:
Refer to the description of this command in the SOLVE Command Reference manual.
Reason:
Part of the PROFILE display. Displays the current setting of the AUTOHOLD option, governing the automatic control of screen wraparound.
System Action:
None.
User Action:
See the Command Reference for details of the AUTOHOLD command.
Reason:
Part of the PROFILE display. NRDELCH specifies the character to be used to form the delimiter line that separates the non-roll delete area on an OCS window from the roll delete area.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. RDMIN specifies the minimum number of lines that the roll delete area of the OCS window may shrink to, to make room for non-roll delete messages.
System Action:
None.
User Action:
None.
Reason:
The user issued a PROFILE MONMSG= command but the userid is not authorized for the receipt of monitor messages.
System Action:
None.
User Action:
None.
Reason:
Part of the Profile display. It displays the users Monitor message receipt status.
System Action:
Monitor class messages will now be directed to this user's OCS window.
User Action:
None.
Reason:
An attempt has been made to flush MSGPROC using PROFILE MSGPROC=FLUSH but has failed because no MSGPROC was running.
System Action:
None.
User Action:
None.
Reason:
An attempt has been made to start MSGPROC but has failed because of a shortage of storage.
System Action:
MSGPROC is not started.
User Action:
Try again later. If the problem persists, notify your systems administrator.
Reason:
An attempt was made to start MSGPROC in an environment which does not support the use of MSGPROC, e.g: from an internal environment using
INTCMD.
System Action:
MSGPROC is not started.
User Action:
None.
Reason:
An attempt was made to start MSGPROC but failed because MSGPROC had already been started.
System Action:
MSGPROC is not started again.
User Action:
None.
Reason:
This message is issued to confirm that a request to start MSGPROC was successful.
System Action:
MSGPROC is started.
User Action:
None.
Reason:
This message is issued to confirm that a request to flush MSGPROC was successful.
System Action:
MSGPROC processing is terminated.
User Action:
None.
Reason:
The ENV= operand on a PROFILE command has been entered twice and the second occurrence has been ignored.
System Action:
The second occurrence of the ENV= operand is ignored.
User Action:
None.
Reason:
A PROFILE command has been entered but either an operand or the command itself (without operands) is not applicable to the environment specified on the ENV= operand supplied or defaulted.
System Action:
The PROFILE command is rejected.
User Action:
None.
Reason:
This message is part of the PROFILE LIST display. It shows the name of the users NPF RESOURCE LIST member.
System Action:
None.
User Action:
None.
Reason:
This is a line of output from the PROFILE command. It shows the user's assigned time zone name and the time zone offset.
System Action:
None.
User Action:
None.
Reason:
A SPLIT or SWAP command has been issued but the operation cannot be performed due to lack of storage.
System Action:
The command is rejected.
User Action:
None.
Reason:
A SPLIT or SWAP command has been issued whilst the current window is locked.
System Action:
The command is rejected.
User Action:
Terminate the LOCK process before retrying the function.
Reason:
The SPLIT or SWAP was command was issued in a region not authorized for multiple windows.
System Action:
The command is rejected.
User Action:
Contact your installation Help Desk if authorization is required.
Reason:
Confirms a PFnn command has been processed, setting the specified Program Function Key.
System Action:
None.
User Action:
None.
Reason:
An invalid operand was entered in a PF command.
System Action:
The command is rejected.
User Action:
Correct and re-enter the request.
Reason:
The PF command supports PFKs in the range 1-24.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
A PF command has been issued from an environment which does not support PF Key usage eg: an internal environment via &INTCMD.
System Action:
The command is rejected. If issued from within an NCL procedure, the procedure will be terminated.
User Action:
Check which operands are supported in the environment specified.
Reason:
A valid ENTER command has been used to equate the ENTER key to a command.
System Action:
None.
User Action:
None.
Reason:
The ENTER command has been used to set the ENTER key to a command but there is no PF key set to the standard ENTER key function. At least one key must be defined to execute the command line text.
System Action:
The ENTER command is ignored.
User Action:
Specify a PF key to take the role of the ENTER key before attempting to equate the ENTER key to another command.
Reason:
A PFnn command has been executed by a SUBMIT command but the user who issued the SUBMIT command does not have the authority to do so.
System Action:
The command is rejected.
User Action:
This is a security related condition. The user authority may be too low.
Reason:
Confirms that a LOG command has been processed.
System Action:
The message has been written to the activity log. The `===>' indicator will prefix the text of the message written to the log.
User Action:
None.
Reason:
The DEFMSG command was entered with an invalid value specified on the DELIVER= operand.
System Action:
The DEFMSG command is rejected.
User Action:
Correct the DELIVER operand. The valid values are PPO, LOCAL, REMOTE, ALL and NONE.
Reason:
A LIST command has been entered from OCS but the procedure name supplied, procname, is not a valid procedure name.
System Action:
None.
User Action:
Correct the syntax of the procedure name.
Reason:
The log number specified on a LOGSWAP command msut be in the range 1 to 9. Note that the log number is ignored unless SYSPARMS LOGWRAP=YES is specified.
System Action:
The LOGSWAP command is ignored.
User Action:
Reissue the corrected command.
Reason:
An invalid VTAM message number has been specified on the DEFMSG command, or one of the other DEFMSG operands specified is invalid.
System Action:
The command is ignored.
User Action:
Reissue the corrected command.
Reason:
A DEFMSG command is valid and has been accepted.
System Action:
None.
User Action:
None.
Reason:
An NCLTEST command is valid and has been accepted. This message shows the (new) NCLTEST values.
aaa will be NOW if the NCLTEST command had operands, else it is not present. bbb will be OFF, ON, or LOG ccc will be blank, or if bbb is ON, may be LOG.
System Action:
None.
User Action:
None.
Reason:
The NCLTEST command may have a single operand of either 'ON' or 'OFF'. The operand value specified is neither of these.
System Action:
The command is ignored.
User Action:
Correct the command and retry.
Reason:
An NCLTEST command has additional operands following 'ON' or 'OFF'. No further operands are required.
System Action:
The entire command is ignored.
User Action:
Correct the command and retry.
Reason:
A request has been made to invoke the EDIT Services function of SOLVE. A storage shortage condition has occurred and the request has failed.
System Action:
The EDIT Services function is not invoked.
User Action:
Investigate cause of storage shortage condition.
Reason:
No value has been defined (via the PF command) for the PF key that was pressed.
System Action:
The PF key request is ignored.
User Action:
Set the PF key using the PF command if required.
Reason:
The system supports PFKs in the range 1-24 only.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
Processing has successfully completed for the NCLTRACE command.
System Action:
If NCLTRACE has been used to start or reset tracing then the target NCL process will begin tracing upon resumption of execution.
User Action:
Review trace messages if required.
Reason:
An NCLTRACE VARS= command has been issued, but the target procedure is an OML procedure. OML does not support the use of NCLTRACE VARS=. Use the NCL DEBUG facility to perform variable update tracing.
System Action:
None.
User Action:
None.
Reason:
An NCLTRACE command failed as the target NCL process was not executing an NCL procedure.
System Action:
None.
User Action:
Try an option that does not require a currently executing procedure.
Reason:
The NCLTRACE command was unable to locate the specified NCL process identified as aaaaaa via the ID operand.
System Action:
None.
User Action:
Correct the ID= operand value. Use SHOW NCL if necessary to determine the processing identifier of the desired NCL process.
Reason:
An NCLTRACE START has determined that the target process, aaaaaa, has already reached the system tracing limit. No further tracing will be performed.
System Action:
None.
User Action:
Review existing trace messages. If further tracing is required use the RESET keyword on the NCLTRACE START request so that tracing may be restarted.
Reason:
The NCLTRACE command failed to obtain the necessary storage to continue processing. The request is ignored.
System Action:
None.
User Action:
Review existing trace messages and if possible reduce storage held by clearing message queues. Retry the request.
Reason:
An NCLTRACE command has specified a variable range greater than the maximum allowed.
System Action:
The command is rejected.
User Action:
Correct the variable specification.
Reason:
The variable prefix supplied combined with the range generates variable names greater in length than the maximum of 12 characters.
System Action:
The command is rejected.
User Action:
Specify a smaller range or prefix so that all names within the requested range are valid.
Reason:
Your userid has not been authorized to perform the function requested.
System Action:
None.
User Action:
Contact your installation help desk if you require this authority.
Reason:
A SETMODE command has specified a mode not recognized by the system.
System Action:
None.
User Action:
The SETMODE command is used by primary menu procedures to control processing. Refer the problem to your installation help desk for problem determination.
Reason:
The SHOWMSG command may only be issued from a dependent environment.
System Action:
None.
User Action:
None.
Reason:
A SETMODE command to modify the primary environment has completed successfully.
System Action:
Any change in the primary environment manager will be actioned when the current primary environment manager terminates.
User Action:
None.
Reason:
A SETMODE command has been issued from a non-terminal region.
System Action:
The command is rejected.
User Action:
None. The command environment is not valid for issuing SETMODE.
Reason:
The DEFMSG command could not obtain sufficient storage to build the DEFMSG table entry.
System Action:
The DEFMSG table entry is not build.
User Action:
Try to determine why the SOLVE address space is short on storage.
Reason:
A limit of 256 unique PPO event names exists for the DEFMSG table. You have tried to specify a new name on the DEFMSG EVENTNAME operand but have exceeded the limit.
System Action:
The DEFMSG table entry is not built.
User Action:
Normalize PPO event names to reduce the number of discrete event names. The other attributes of the PPO message may be used by the event listener procedures to achieve greater granularity if required.
Reason:
An attempt was made to issue a DEFMSG command but NPF initialization did not complete successfully.
System Action:
The DEFMSG command is ignored.
User Action:
Look for a message from SOLVE initialization which indicates the reason for initialization failure. This will most likely be an N180xx message. Correct the error and re-start SOLVE.
Reason:
A TIMEZONE ADD command has added the named time zone to the TIMEZONE table.
System Action:
None.
User Action:
None.
Reason:
The named time zone already exists in the TIMEZONE table.
System Action:
The command is ignored
User Action:
Correct the TIMEZONE name and retry if required.
Reason:
A TIMEZONE DELETE command has removed the named time zone from the TIMEZONE table.
System Action:
None.
User Action:
None.
Reason:
The named time zone could not be deleted as it does not exist in the TIMEZONE table.
System Action:
The command is ignored
User Action:
Correct the TIMEZONE name and retry if required.
Reason:
The time zone name on a TIMEZONE command is not valid. A time zone name must be a 1 to 8 character PDSNAME-format name, except that the values USER and SYSTEM are not accepted.
System Action:
The command is ignored.
User Action:
Correct the time zone name.
Reason:
The time zone offset on a TIMEZONE command is not valid. A time zone offset must be either 0 or in the format shhmm where s is + or -, hh is an hours value (00 to 23) and mm is a minutes value (00 to 59).
System Action:
The command is ignored.
User Action:
Correct the time zone offset and retry.
Reason:
An attempt to start user NCL cputime accounting reporting failed due to insufficient storage being available for work buffers.
System Action:
None.
User Action:
Contact System Administrator.
Reason:
The USERACCT command entered by the user was accepted without any syntax errors.
System Action:
Command processed.
User Action:
None.
Reason:
An attempt to start user NCL cputime accounting reporting failed because one of the operands had an invalid value. aaaaaaaaaa is operand name.
System Action:
None.
User Action:
Correct and re-submit command.
Reason:
The value used on the FROM= operand on the USERACCT command is invalid syntax for a time value.
System Action:
None.
User Action:
Correct and retry.
Reason:
It is invalid to specify the FROM or INTERVAL operands when user NCL cputime reporting is active.
System Action:
None.
User Action:
Either don't use these operands, or inactivate user NCL cputime accounting using a USERACCT STOP before restarting it.
Reason:
User NCL cputime accounting reporting was in the process of deactivating when the USERACCT command was entered.
System Action:
None.
User Action:
Wait till user NCL cputime accounting reporting deactivation finishes and retry.
Reason:
The USERACCT START command failed because the system was not started with the system cputime accounting option. (JCL PARM OPT=01).
System Action:
User NCL cputime accounting reporting not started.
User Action:
In order to use the user NCL cputime accounting facility, SOLVE must be re-started with JCL parm OPT=01.
Reason:
The USERACCT command was processed succesfully.
System Action:
User NCL cputime accounting reporting commenced if USERACCT START specified. User NCL cputime accounting stopped if USERACCT STOP was specified. Also any additional parameters specified (for USERACCT START or USERACCT SET) have been modified and will apply for the next report.
User Action:
None.
Reason:
The USERACCT command failed because an invalid value was specified on the INTERVAL= operand. The INTERVAL operand value must be a whole factor of 24. (i.e. 1,2,3,4,6,8,12 or 24).
System Action:
User NCL cputime accounting reporting not commenced.
User Action:
Correct and re-try.
Reason:
The USERACCT command failed because the START operand was used when user NCL cputime reporting was already active.
System Action:
None.
User Action:
Either STOP user NCL cputime reporting in order to re-start it, or use the USERACCT SET option to modify user NCL cputime reporting parameters.
Reason:
The USERACCT command failed because the STOP operand was used when user NCL cputime reporting was already inactive.
System Action:
None.
User Action:
Use the USERACCT START operand to start user NCL cputime reporting. Use the USERACCT SET operand to modfiy user NCL cputime reporting parameters without affecting the current active/inactive status of user NCL cputime reporting.
Reason:
An attempt to produce a user NCL cputime accounting SMF report failed because the system is not authorized to produce SMF reports, or the operating system does not support SMF reporting.
System Action:
User NCL cputime accounting reporting is terminated.
User Action:
Re-start system authorized in order to generate user NCL cputime accounting SMF reports.
Reason:
An attempt to produce a user NCL cputime accounting SMF report failed due to a storage shortage.
System Action:
User NCL cputime accounting reporting is terminated.
User Action:
Contact system administrator.
Reason:
An attempt to produce a user NCL cputime accounting SMF report failed because SMF is inactive.
System Action:
User NCL cputime accounting reporting is terminated.
User Action:
Start SMF and then restart user NCL cputime accounting reporting, using the USERACCT START command.
Reason:
The SMF record id specified for user NCL cputime accounting reporting is invalid.
System Action:
User NCL cputime accounting reporting is terminated.
User Action:
Modify the SMF record id using the USERACCT SMFRECID= operand when re-starting user NCL cputime accounting reporting.
Reason:
An attempt to write a user NCL cputime accounting report to SMF failed in SMF with an SMF return code of retcode.
System Action:
User NCL cputime accounting reporting is terminated.
User Action:
Refer to SMF manual.
Reason:
A report containing details of user NCL cputime usage has been written to SMF.
System Action:
User NCL cputime accounting report was generated.
User Action:
None. (Note that SHOW USERACCT will show current status of user NCL cputime reporting, including the SMF record id for user NCL cputime accounting SMF records).
Reason:
This message is issued when the ALTLIB SET command is used to alter the NCL library name. The new name is displayed.
System Action:
All following NCL procedure requests for this user session are loaded from the indicated library.
User Action:
None.
Reason:
This message is issued when the ALTLIB SET command is used to alter the PANEL path name. The new name is displayed.
System Action:
All following PANEL definition requests for this user session are loaded from the indicated library.
User Action:
None.
Reason:
This message is issued when the ALTLIB RESET command is used to reset the NCL library name and PANEL path name.
System Action:
All following NCL procedure and PANEL requests for this user session are loaded from the default library/path (normally COMMANDS for NCL and PANELS for Panel requests).
User Action:
None.
Reason:
This message is issued when the ALTLIB command is issued from an environment where it cannot be used. For example, an EASINET session.
System Action:
The command is ignored.
User Action:
None.
Reason:
This message is a response to the SYNCTIME command, and shows that a local time offset change was detected.
The previous offset (in hours and minutes) and new offset are shown.
System Action:
The system uses the new local time offset.
User Action:
None.
Reason:
This message is a response to the SYNCTIME command, and shows that no local time offset change was detected.
The previous offset (in hours and minutes) and new offset are shown.
System Action:
None.
User Action:
None.
Reason:
This message is a response to the SYNCTIME command, and shows that
the command was ignored. Possible reasons are as follows:
System Action:
None.
User Action:
None.
Reason:
A heading line for the reponse to a SHOW IOSTATS command.
System Action:
None.
User Action:
None.
Reason:
A detail line for the reponse to a SHOW IOSTATS command.
The fields are:
ddname The ddname for this file c# The relative concatenation number; '-' if not a part of a concatenation #-excp The number of I/O requests to this file (via this allocation) t-conn The total connect time (seconds.milliseconds) dsn The dataset name (and member name if available)
System Action:
None.
User Action:
None.
Reason:
This message is produced if the SHOW IOSTATS command is issued in an operating system environment that does not support it.
This command is supported on MVS/ESA and OS/390 only.
System Action:
The SHOW IOSTATS command is ignored.
User Action:
None.
Reason:
This is the response to a TIME command and a SYSPARMS TIMEZONE= command. It shows the current time, and the current date in Gregorian and Julian date formats. Also, the system GMT time offset, and if the JCL PARM TZ=GMT is specified, this is indicated with TZ=GMT.
System Action:
None.
User Action:
None.
Reason:
This is the response to a TIME command and a SYSPARMS TIMEZONE= command. It shows GMT time, and the current date in Gregorian and Julian date formats.
System Action:
None.
User Action:
None.
Reason:
This is the response to a TIME command. It shows the user time, date, time zone offset and name.
If the user time offset is greater than one day, the offset shown is only the remaining hours, and the message also contains (DAYS: ddd) following the offset.
System Action:
None.
User Action:
None.
Reason:
Confirms the acceptance of an FSTOP command.
System Action:
An irreversible system shutdown begins. Logged on users will receive a 10 second warning prior to Shutdown completing.
User Action:
None.
Reason:
A SHUTDOWN command was entered when an earlier one had already been entered.
System Action:
The command is ignored.
User Action:
None.
Reason:
An EVERY command was entered specifying an interval greater than 24 hours.
System Action:
The command is rejected.
User Action:
Correct the error and retry.
Reason:
The TIME operand of an AT or EVERY command is invalid or out of range. range.
System Action:
The command is rejected.
User Action:
Correct the error and retry.
Reason:
One or more required operands of an AT or EVERY command has been omitted.
System Action:
The command is ignored.
User Action:
Supply the missing operand(s) and retry.
Reason:
The command text for an AT or EVERY command has been omitted.
System Action:
The command is rejected.
User Action:
The command text must be specified as the last operand of an AT or EVERY command. Correct and retry.
Reason:
You are not authorized to use the KEEP or ROUTE operands of the AT and EVERY command.
System Action:
The command is rejected.
User Action:
Contact your systems administrator if you need to use either of these operands.
Reason:
The system has a limit to the number of timer based commands that may be active concurrently. This limit has been reached.
System Action:
The command is rejected.
User Action:
Retry the command later, when some timer based commands may have been purged. This limit may be increased by your systems administrator if required.
Reason:
The command text in an AT or EVERY command may not be longer than 80 characters.
System Action:
The command is rejected.
User Action:
Split the command into multiple commands or abbreviate commands and operands where possible.
Reason:
The time interval on an EVERY command may not be less than sssss seconds.
System Action:
The command is ignored.
User Action:
Choose an interval greater than sssss seconds.
Reason:
An AT or EVERY command has been accepted. The purge ID number shown can be used in a subsequent PURGE command to manually terminate the command. This number will also be displayed in the ID field of the SHOW TIMER display.
System Action:
The command is queued for execution at the specified interval.
User Action:
None.
Reason:
An invalid time has been specified in the AT command.
System Action:
The command is rejected.
User Action:
Correct the error and retry.
Reason:
Propagation of an `EVERY' timer command is not supported from other `EVERY' commands.
System Action:
The command is rejected.
User Action:
Correct the error and retry.
Reason:
The user-assigned timer identification (TID=aaaa) is already assigned to another timer command.
System Action:
The command is rejected.
User Action:
Specify a different TID= value and retry.
Reason:
A time offset expression is only valid on an AT command.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The ROUTE= operand on an AT or EVERY command contains invalid characters.
System Action:
The command is ignored.
User Action:
Correct the command and retry.
Reason:
ID=ALL or ID=OWN are not valid on an AT or EVERY command.
System Action:
The command is ignored.
User Action:
Specify a correct ID= operand and resubmit the command.
Reason:
A repeat timer interval of zero has been specified on an EVERY command but no LIMIT has been specified.
System Action:
The command is rejected.
User Action:
Specify either a limit, or a non-zero repeat interval.
Reason:
This is the response to a MAXUSERS command with no operands.
System Action:
None.
User Action:
None.
Reason:
Confirms that a MAXUSERS command has been processed.
System Action:
The new MAXUSERS limit is now nnnn.
User Action:
None.
Reason:
The MAXUSERS operand specified is not numeric, or is longer than 4 digits.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
The MAXUSERS operand specifies a number greater than that allowed.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
No operands are expected on the STATUS command.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
This is the first message in response to the STATUS command.
DDD Is the abbreviation of the day of the week.
dd Is the number of the day in the month.
MMM Is the abbreviation of the month.
yyyy Is the year.
hh Is the hour in 24-hour format.
mm Is the minute of the hour.
ss Is the second of the minute.
System Action:
None.
User Action:
None.
Reason:
Part of the STATUS display. Indicates the number of users logged on to SOLVE.
System Action:
None.
User Action:
None.
Reason:
Part of the STATUS display. Indicates that SOLVE's PPO ACB is open, and that SOLVE will receive unsolicited VTAM messages.
System Action:
None.
User Action:
None.
Reason:
Part of the STATUS display. Indicates that SOLVE's PPO ACB is not open, or a PPO START command has been issued but an error was encountered and the ACB was not opened.
System Action:
None.
User Action:
Issue a PPO START command if SOLVE is to receive unsolicited VTAM messages.
Reason:
Part of the STATUS display. A SHUTDOWN or FSTOP command has been entered.
System Action:
SOLVE is in the process of terminating.
User Action:
None.
Reason:
Part of the STATUS display. Indicates the number of logged-on users eligible to receive unsolicited VTAM messages.
System Action:
None.
User Action:
None.
Reason:
Part of the STATUS display. The domain ID is specified on the NMDID initialization parameter and must be unique in a network of connected SOLVE systems. The SOLVE System User Prefix is a 1 to 4-character value that forms the prefix for all system users, for example, BLOG, BMON. This value is specified on the NMSUP initialization parameter and if omitted defaults to the NMDID value.
System Action:
None.
User Action:
None.
Reason:
Part of the display resulting from a STATUS command. P1 is the local identifier of this region, as defined by the SYSPARMS ID= parameter at system initialization. The started task/job name is shown ( P2 ) where available. If not available, for example before the VTAM interface is available, N/A is shown.
System Action:
None
User Action:
None
Reason:
Part of the display resulting from a STATUS command, this indicates the number of active (nnnn) or inactive (mmmm) links that exist from this SOLVE system to remote SOLVE systems.
System Action:
None.
User Action:
Use the SHOW LINKS command for detailed information on the status of the individual links.
Reason:
An error during system initialization has caused NPF message partitioning to be disabled. Users will be treated as though no NPF message member has been defined for their userids.
System Action:
None.
User Action:
Refer to the system activity log for details of the error that occurred. Correct the error and restart the system.
Reason:
Gives the name of the current PPOPROC, CNMPROC or LOGPROC NCL procedure and whether it is executing.
System Action:
None.
User Action:
None.
Reason:
Denotes the end of the STATUS display.
System Action:
None.
User Action:
None.
Reason:
This region includes the displayed product feature.
P1 is the product feature name key. The key is in a PROD statement in the RUNSYSIN member.
P2 shows the product LMP code (if applicable).
P3 is the product feature release.
P4 is the service pack (if applied).
System Action:
None.
User Action:
If a required product is not indicated by one of these messages, add its product name key in a PROD statement in the RUNSYSIN member.
Reason:
Part of the STATUS display. Indicates that the system is operating with the EASINET feature, and the feature is driven by the NCL procedure procname.
System Action:
None.
User Action:
None.
Reason:
Part of the STATUS display, this message specifies the current release ( P1 ) of the system services base and the service pack (LEVEL P2 ) applied.
System Action:
None.
User Action:
None.
Reason:
CPU measurement is active in the region. A SHOW NCL command will return an N11946 message showing the NCL procedure's CPU usage in seconds.
If P1 is blank, CPU accounting is controlled by the XOPT=CPU statement in the region's RUNSYSIN startup parameters, and it adds to the region's CPU usage.
If P1 is (HIGH PERFORMANCE), the region is running on at least an IBM z9 system supporting the ECTG machine instruction. CPU accounting is enabled automatically, and it adds little to the region's CPU usage.
System Action:
None.
User Action:
None.
Reason:
Part of the STATUS display. Indicates that logging to the system activity log has terminated. This happens only if I/O errors occur on the activity log. The system should not be run any longer than necessary without logs since no audit trail of system actions will be available.
System Action:
None.
User Action:
Determine the cause of the error that terminated logging.
Reason:
Part of the STATUS display shows the local time offset in hours and minutes (with a sign indicating ahead (+) or behind (-) GMT/UTC.
If the offset exceeds one day, the offset is only the remaining hours, and the number of days is shown as (DAYS: nnn).
If the region is not operating in normal local time mode, an additional literal indicates the mode as follows:
(JCL TZ=SHHMM) JCL parm TZ=offset was specified
(JCL TZ=GMT) JCL parm TZ=GMT was specified
(##TOFF TEST MODE) The ##TOFF command is in use
System Action:
None.
User Action:
None.
Reason:
Part of the STATUS display. Indicates that the system is operating with an installation provided security exit. type indicates the type of exit in use, either PARTIAL or FULL.
System Action:
None.
User Action:
None.
Reason:
Part of the STATUS display. Indicates the VTAM version and release level with which SOLVE is operating, and the SSCPNAME and NETWORK name of the VTAM system.
System Action:
None.
User Action:
None.
Reason:
Part of the STATUS display which shows the text of the ABEND command.
System Action:
None.
User Action:
None.
Reason:
Part of the STATUS display which shows the status (ACTIVE/INACTIVE) of the VTAM SPO interface. If the status is ACTIVE then the domain ID of the owner of SPO interface is also shown.
System Action:
VTAM commands fail with message N12106.
User Action:
Refer to the user action for message N12106.
Reason:
A shortage of VTAM storage has occurred which has affected the operation of the PPO and/or SPO interface(s).
System Action:
Responses to VTAM commands and/or the processing of unsolicited messages will not be received due to the inactive state of the interface(s). SOLVE will attempt to restart the interface(s) every 5 seconds until a PPO STOP or SPO STOP command is entered or until the storage shortage is relieved.
User Action:
None.
Reason:
This message is part of the STATUS display. It indicates the primary name with which the region is operating.
System Action:
None.
User Action:
None.
Reason:
This message is part of the STATUS display. It identifies the name and version of the SSL provider used by the region.
System Action:
None.
User Action:
None.
Reason:
This message is produced as part of the response to a STATUS command. It indicates the requested and in-effect execution mode (the requested mode is the mode specified on the XM=aaaa JCL parm).
The possible requested mode values are as follows:
N/S-No execution mode was requested.
TASK-Task mode was requested.
ZIIP-zIIP mode was requested.
BEST-The best available mode was requested.
The possible in-effect execution mode values are as follows:
TASK-The region is executing in TASK mode.
ZIIP-The region is executing in SRB mode, possibly utilizing a zIIP if one is available.
System Action:
None.
User Action:
None.
Reason:
This message is produced as part of the response to a STATUS command, when the requested and actual execution modes differ (except when the requested mode is BEST and the actual mode is ZIIP).
The fields in the message are as follows:
A reason code (related to the description)
A system service return code
A system service reason code
A textual description of the problem:
MODE N/S ON THIS OPSYS
APF AUTHORIZATION REQUIRED
NO ZIIP SUPPORT IN OPSYS
NO DEFINED ZIIP PROCESSORS
NO ONLINE ZIIP PROCESSORS
GETMAIN FAILURE
LOAD OF PAUSE SERVICE FAILED
PEL DEFINE FAILED
WLM REGISTRATION FAILED
WLM ENCLAVE DEFINE FAILED
WLM ZIIP ACTIVATION FAILED
SRB MODE WAIT SETUP FAILED
System Action:
None.
User Action:
Examine the description to determine why the requested mode was not activated.
Reason:
This message indicates whether passwords are used as entered (case sensitive) or folded to uppercase (when p1 displays NOT).
Passwords are case sensitive if the XOPT JCL parameter of the region specifies the PWMIX option in the dsnpref.rname.TESTEXEC(RUNSYSIN) member. The default is to fold passwords to uppercase.
System Action:
None.
User Action:
To permit mixed case passwords, add PPREF='XOPT=PWMIX' to the RUNSYSIN member.
Reason:
Issued in the group of messages that form the response to the STATUS command. This message displays the date and time that SOLVE completed its initialization.
System Action:
None.
User Action:
None, for information only.
Reason:
Displays the CPUID returned from the operating system where; ff is the CPU format code; iiiiii is the CPU identification number; mmmm is the CPU model number. If the product is running in an unauthorized environment and the CPUID cannot be determined the text (UNKNOWN) will be displayed.
System Action:
None.
User Action:
None.
Reason:
Acknowledges a PPO START command.
System Action:
An attempt will be made to open the VTAM PPO ACB, if successful, PPO messages received will be distributed to authorized users. Individual operators that are authorized to receive PPO messages will be notified that the PPO interface is now active.
User Action:
If PPO messages are not required, use the PROFILE PPO=NO command to suppress them from your OCS window.
Reason:
Acknowledges a PPO STOP command.
System Action:
The VTAM PPO ACB will be closed. Each operator that is authorized to receive PPO messages will be notified that the PPO interface has been disabled.
User Action:
None.
Reason:
The PPO command must include either the START or STOP operand.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
A PPO START command was issued when an earlier PPO START command was still in effect.
System Action:
The command is rejected.
User Action:
None.
Reason:
A PPO STOP command was entered but the PPO ACB was not open.
System Action:
The command is rejected.
User Action:
None.
Reason:
Acknowledges successful completion of the SPO START command.
System Action:
The SPO interface has been started and replies to VTAM commands may now be returned to the users that issued them.
User Action:
None.
Reason:
Acknowledges successful completion of the SPO STOP command.
System Action:
The VTAM SPO interface will cease processing. Replies to VTAM commands will now be lost and will not be returned to the user who issued the command.
User Action:
None.
Reason:
The SPO command must include either the START or STOP operand.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
An SPO START command was issued when the SPO interface was already active.
System Action:
The command is rejected.
User Action:
None.
Reason:
An SPO STOP command was entered but the SPO interface was not active.
System Action:
The command is rejected.
User Action:
None.
Reason:
A VTAM storage shortage has halted operation of the SPO interface.
System Action:
SOLVE will try to restart the SPO interface every 5 seconds until an SPO STOP command is entered or the storage shortage is relieved.
User Action:
None.
Reason:
An attempt was made to redirect SPO commands to a remote domain, however, there is no active link to the remote domain.
System Action:
The SPO start fails.
User Action:
Start a link to the remote domain and reissue SPO START command.
Reason:
SPO commands have been redirected to domain dddd .
System Action:
All SPO commands will be routed to the remote domain indicated.
User Action:
None.
Reason:
A SHUTDOWN command has been entered by an authorized user. If users are still logged on the message indicates the number still active and if any are disconnected.
System Action:
If the message does not indicate users are still logged on then the shutdown sequence has been initiated. Otherwise, further logons are rejected, and the shutdown sequence will start when the last user logs off.
User Action:
If users remain then these may be informed of the shutdown via a broadcast.
If necessary, enter SHUTDOWN CANCEL to reset the pending shutdown, or use the FSTOP command to shut down the system immediately.
Reason:
A SHUTDOWN CANCEL command was entered, but no SHUTDOWN command had been entered earlier.
System Action:
The command is rejected.
User Action:
None.
Reason:
A SHUTDOWN CANCEL has been processed successfully.
System Action:
The previous pending shutdown is cancelled.
User Action:
None.
Reason:
An invalid operand was specified on a SHUTDOWN command.
System Action:
The command is rejected.
User Action:
None.
Reason:
A SHUTDOWN CANCEL command was entered but system termination had already started.
System Action:
The system will terminate.
User Action:
None.
Reason:
A SHUTDOWN command has been entered and shutdown processing is already in effect. The message also indicates the number of currently logged on users of which 'bbbbb' are active and 'ccccc' are disconnected.
System Action:
None.
User Action:
The shutdown can be cancelled with a SHUTDOWN CANCEL command or you can immediately terminate the system with an FSTOP command. You may also wish to notify the users via broadcast etc.. that a shutdown is pending.
Reason:
This message is written to the system console at the beginning of the product's termination. P1 is the product name and P2 is the system name as set by the PRI= initialization parameter.
System Action:
System shutdown processing begins.
User Action:
Logoff from the system if you are logged on.
Reason:
This message is written to the system console at the completion of the product's termination. P1 is the product name and P2 is the system name as set by the PRI= initialization parameter.
System Action:
The job terminates.
User Action:
None
Reason:
No operand was specified on a DEFLOGON, DELLOGON, ACTLOGON, SUSLOGON or REPLOGON command.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
The specified operand is incorrect.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
The specified operand is incorrect.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
One of the messages issued as a result of an ACTLOGON or SUSLOGON APPL=ALL.
System Action:
SOLVE has taken the specified action to either allow or prevent all logon attempts to any application through the use of EASINET.
User Action:
None.
Reason:
The specified action ( xxxxxxxx = ACTIVATED, SUSPENDED, ADDED, DELETED, or REPLACED) has been taken in respect of the nominated DEFLOGON path.
System Action:
None.
User Action:
None.
Reason:
The specified operand is not valid for the command.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
INPUT is a required operand of a DEFLOGON or REPLOGON command.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
One of the messages issued as a result of an ACTLOGON or SUSLOGON APPL=applname.
System Action:
SOLVE has taken the specified action to either allow or prevent all logon attempts to this application through the EASINET.
User Action:
None.
Reason:
The INPUT= operand of a SUSLOGON, ACTLOGON or DELLOGON command specified an undefined LOGON entry.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
The DEFLOGON or REPLOGON command could not be processed because of storage shortage.
System Action:
The command is rejected.
User Action:
Retry.
Reason:
An ACTLOGON, DEFLOGON, DELLOGON, REPLOGON or SUSLOGON command has been issued with conflicting or duplicated operands, aaaa.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
A REPLOGON command has been successfully processed for a logon path which was previously suspended by a SUSLOGON command. The logon path remains suspended.
System Action:
None, for information only.
User Action:
If the path is to be activated also, issue the ACTLOGON command.
Reason:
A DEFLOGON command was issued specifying the name of an existing LOGON entry.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
A DELLOGON command specified an APPL name for which no DEFLOGON entries have been defined.
System Action:
The command is rejected.
User Action:
Correct the APPL name and retry.
Reason:
Confirms that the specified number of DEFLOGON entries for application applname have been suspended, deleted or activated, depending upon the command entered.
System Action:
None.
User Action:
None.
Reason:
A SUSLOGON, DELLOGON or ACTLOGON command failed to specify either the INPUT or the APPL operand, one of which is required.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
The SUSLOGON command TEXT operand may not exceed 50 characters.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Confirms that the specified number of DEFLOGON entries have been suspended, deleted or activated, depending upon the command entered.
System Action:
None.
User Action:
None.
Reason:
A SHOW command was entered without an operand.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
Occurs when SHOW NCLVARS=procname is issued and the procedure name is not found.
System Action:
none
User Action:
none
Reason:
A SHOW PARMS command was issued but no initialization parameters have been supplied.
System Action:
None.
User Action:
None.
Reason:
A SHOW command was entered but the command authority of the user was not as high as the command authority level required for one or more operands entered.
System Action:
The command is rejected.
User Action:
Obtain authorisation.
Reason:
Indicates the end of a multi-line SHOW command display.
System Action:
None.
User Action:
None.
Reason:
This is the title line of the SHOW BUFF display. It will be followed by a series of N11909 messages indicating internal SOLVE buffer usage by buffer pool type.
TYPE Identifies the buffer pool to which following information on this line is referring.
SIZE Length of buffer.
B-USE Current number of buffers in use.
B-MAX Maximum number of buffers ever in use.
WAITS Number of waits against this pool.
B-AVL Number of buffers currently available.
FRMES Total number of frames used.
F-MAX Maximum number of frames ever in use.
SOURCE Storage source.
System Action:
None.
User Action:
None.
Reason:
The numbers given in this message line up in columns under the column titles, specified by message N11908.
System Action:
None.
User Action:
This information exists for possible problem determination. Contact your product support representative in the event of a system problem.
Reason:
This message appears at the end of a SHOW BUFF command and indicates the total amount of working storage being used by SOLVE at the time of the display, and the maximum ever obtained.
System Action:
None.
User Action:
None.
Reason:
This message is part of a SHOW BUFF command. It precedes message N11910 when running in an XA environment and shows how much of the storage summarized in N11910 is above and below the 16MB line.
System Action:
None.
User Action:
None.
Reason:
A request for storage above the 16MB line has been refused.
System Action:
SOLVE will get the required storage from below the line.
User Action:
Notify your systems administrator.
Reason:
This message is issued as part of a SHOW BUFF command and gives totals for the number of GETMAIN (GETVIS) and FREEMAIN (FREEVIS) operations performed.
System Action:
None
User Action:
None
Reason:
A SHOW SESS command was issued when no terminals were connected to the system.
System Action:
None.
User Action:
None.
Reason:
The SHOW SESS display consists of a series of these messages, listing the LUNAMES of each connected LU in connection order from left to right.
System Action:
None.
User Action:
None.
Reason:
The last line of a SHOW SESS display, giving the number of sessions displayed.
System Action:
None.
User Action:
None.
Reason:
This message is issued during a SHOW NCL command and is accompanied by an N11936 message that identifies an NCL process. This message indicates the current state of that process. The process may be currently loading a procedure, executing the NCL verb nclverb at statement nnnn or executing a command. The 'status' field may contain the following values:
PROCESSING indicates that the NCL process is executing normally and is not under the control of the NCL debug facility.
IN-DEBUG indicates that the NCL process is executing normally and is under the control of the NCL debug facility.
SUSPENDED indicates that the NCL process is under control of the NCL debug facility and execution of the process has been suspended due to a user command or a breakpoint being reached.
The additional text string may contain a number of phrases that further describe the process:
'MSGS LOST' indicates that the process's dependent environment has exceeded message queueing limits resulting in loss of data.
'FORCED IDLE' is displayed if the process is currently in a wait state due to NCL performance controls.
'P=panel-name' displays the active panel display if the current verb is PANEL.
System Action:
None.
User Action:
Reason:
The response to a SHOW BRO command when no system broadcast is currently set.
System Action:
None.
User Action:
None.
Reason:
The response to a SHOW BRO command when no Primary Menu broadcast is currently set.
System Action:
None.
User Action:
None.
Reason:
The response to a SHOW BRO command when a system broadcast is set. The broadcast text follows this message.
System Action:
None.
User Action:
None.
Reason:
The response to a SHOW BRO command when a Primary Menu broadcast is set. The broadcast text follows this message.
System Action:
None.
User Action:
None.
Reason:
Follows message N11924 and gives details of a SHOW LOG command.
logid - JCL DD name of this log.
status - defines the current status of the log. This will be "IN USE", "SWAPPED" or "AVAIL".
yy.ddd hh.mm.ss - date and time logging commenced to this DD.
yy.ddd hh.mm.ss - date and time logging ceased for this DD.
pages - the number of pages printed.
swapped-by - the reason the activity log was swapped. This will be either a USERID if a user entered the LOGSWAP command, "FULL" if the log swapped because the log filled up, or "IO-ERROR" if the log was swapped due to a write failure.
System Action:
None.
User Action:
None.
Reason:
The title line of the SHOW LOG display.
System Action:
None.
User Action:
None.
Reason:
Part of the SHOW LOG display. Issued if all logs have been closed and no logging is taking place. This can normally only happen if an I/O error occurs while logging to the last available log, or if the last available log is full.
System Action:
None.
User Action:
SOLVE should be re-started as soon as possible if logging is necessary.
Reason:
The response to a SHOW NCL/NCLVARS command if your NCL processing region has no active NCL processing running.
System Action:
None.
User Action:
None.
Reason:
The response to a SHOW PAUSE command if the user has an NCL procedure which is paused because of an WAIT statement.
System Action:
None.
User Action:
The GO, END or FLUSH commands may be used to resume or terminate execution of the NCL procedure if the waiting text is not expected to arrive.
Reason:
Issued in response to SHOW PAUSE command when an NCL procedure is suspended pending completion of processing by the module module, invoked by the procedure via an &CALL statement.
System Action:
None.
User Action:
None.
Reason:
Issued in response to a SHOW PAUSE command and indicates that the loading of an NCL procedure is in progress prior to execution. The loading of NCL procedures is performed in conjunction with a subtask that performs the OPEN and CLOSE processing. It is possible that the loading of an NCL procedure could be delayed as a result of interference with the disk sub-system.
System Action:
None.
User Action:
Exiting OCS mode at this point in time will terminate the load process and flush the procedure. Excessive delays may be as a result of RESERVES being placed on the volume on which the NCL library resides. Check if this is the case and if necessary relocate the library to a less active volume.
Reason:
Issued in response to a SHOW PAUSE command and indicates that the user has an NCL procedure waiting for completion of a VSAM I/O operation which has been delayed due to a string shortage or an exclusive control lockout.
System Action:
None.
User Action:
The user may allow the procedure to complete or flush the procedure if desired.
Reason:
The heading of the response to a SHOW NCL command.
System Action:
None.
User Action:
None.
Reason:
The description of an NCL process following the N11935 heading line. The columns line up under the headings in message N11935. Values are:
aaa - The NCL identifier of the process.
bbb - The name of the base procedure in the process.
ccc - The name of the procedure currently executing in the process.
d - The nesting level of the current procedure.
e - The window in whose NCL processing environment the process is executing. Value is 1 or 2.
fff - The type of process, eg: MSGPROC.
gggg - Normally the userid that originated the process's execution. Alternatively this may be the luname of the terminal if the NCL procedure was started via the EASINET procedure without effecting user signon.
hhhh - The userid under whose NCL region the process is running.
i The NCL performance group of the process.
j - The dispatch priority of the process within its performance group.
kkk - The number of NCL processing units consumed by this process's execution so far.
System Action:
None.
User Action:
None.
Reason:
This message follows the previous N11936 message to indicate the displayed NCL procedure is running.
System Action:
None.
User Action:
None.
Reason:
No user region of the requested name was found. No NCL procedures can be displayed.
System Action:
None.
User Action:
None.
Reason:
The requested NCL region had NCL procedures active, but none matched the selection criteria on the SHOW NCL command.
System Action:
None.
User Action:
None.
Reason:
The displayed operand value is not valid.
System Action:
The command is not processed.
User Action:
Correct the operand and retry.
Reason:
No procedure with the requested NCLID was found. message is issued for a show ncl/nclvars statement.
System Action:
None.
User Action:
Ensure the correct NCLID is supplied. The procedure may have terminated.
Reason:
The limit on the number of messages displayed by this command has been reached.
System Action:
No further output will be produced by this command.
User Action:
Provide operands to limit the number of matching NCL procedures.
Reason:
A heading line for the reponse to a SHOW LUTRACE command.
System Action:
None.
User Action:
None.
Reason:
A detail line issued in response to a SHOW LUTRACE command. The various fields are as follows:
P1 the name of the terminal.
P2 the userid of the user who started the trace.
P3 the date on which the trace was started.
P4 the time at which the trace was started.
P5 the number of messages sent to the terminal during the current session.
P6 the number of messages received from the terminal during the current session.
P7 the total number of messages sent to the terminal since tracing was started.
P8 the total number of messages received from the terminal since tracing was started.
P9 the current status of the LUTRACE request (either ACTIVE or PENDING).
P10 the NCLID of an NCL process that will receive the trace messages, if any. Trace messages are directed to an NCL when the trace is started using the LUTRACE START with ENV=CURRENT specified.
System Action:
None.
User Action:
None.
Reason:
The SHOW NCL/NCLVARS command had invalid syntax for the reason shown:
ID IS INVALID. nclid is not in range 1-999999. PRTY IS INVALID. The operand should have a length of 1. PG IS INVALID. The operand should have a length of 1. PROC IS INVALID. The length of the operand should be in range 1-8. NAME IS INVALID. The length of the operand should be in range 1-8. LIST IS INVALID. The operand may have a value either ALL or SUMMARY.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
Shows the total used cputime for an NCL procedure. Issued during a SHOW NCL command.
System Action:
None.
User Action:
None.
Reason:
Shows who updated the primary menu broadcast message, and when. Issued during a show broadcast command.
System Action:
none
User Action:
none
Reason:
A heading line for the reponse to a SHOW SESS command with extended operands.
System Action:
None.
User Action:
None.
Reason:
A detail line issued in response to a SHOW SESS command. The various fields are as follows:
luname The name of the terminal
userid The userid logged on at this terminal ('-' if none)
env The SOLVE environment type
am The access method used for this terminal; note that 'SYSTEM' means an internal SOLVE access method.
am-information For access methods other than 'SYSTEM', information that is specific to the access method. For example, terminals using VTAM will display the network name and VTAM CID.
System Action:
None.
User Action:
None.
Reason:
This line details the number of sessions listed by a SH SESS command. The total number of sessions listed is shown, as well as the total number of sessions. The number of sessions that are EASINET sessions is also displayed.
System Action:
None.
User Action:
None.
Reason:
This message is produced in response to a SHOW SESS command with extended operands. It indicates that an operand was in error.
System Action:
The SHOW SESS command is ignored.
User Action:
Correct the operand(s) in error and retry the command.
Reason:
The ALLOC and UNALLOC commands require one or more operands that have been omitted.
System Action:
The command is rejected.
User Action:
Refer to the description of the ALLOC and UNALLOC commands in the Command Reference.
Reason:
The operand is either unrecognized, or contains invalid syntax.
System Action:
The command is rejected.
User Action:
Refer to the description of the ALLOC and UNALLOC commands in the Command Reference.
Reason:
The ALLOC or UNALLOC command failed due to insufficient storage.
System Action:
The command is rejected.
User Action:
Retry. If problem persists increase region size.
Reason:
The requested suboperand is in error.
System Action:
The command is rejected.
User Action:
Correct the error and retry.
Reason:
An operand has been specified more than once on an ALLOC command.
System Action:
The command is rejected.
User Action:
Correct the error and retry.
Reason:
Operands specified are mutually exclusive.
System Action:
The command is rejected.
User Action:
Correct the error and retry.
Reason:
Use of the FOLD option requires a UCS entry to nominate the universal character set being used.
System Action:
The command is rejected.
User Action:
Include a UCS name and retry.
Reason:
Confirms that the ALLOCate or UNALLOCate command has been accepted for processing.
System Action:
None.
User Action:
Other messages indicating the success or failure of this processing will follow.
Reason:
An attempt was made to ALLOC or UNALLOC a reserved DDNAME.
System Action:
The command is rejected.
User Action:
SOLVE itself has allocated to it ddnames such as those used for panel libraries, command libraries etc., which are reserved for its use only. Use a DDNAME that is not reserved.
Reason:
An ALLOC command was issued, but no dataset name or sysout class was specified.
System Action:
The command is rejected.
User Action:
The allocate command is used to allocate either a dataset or a sysout dataset. Determine the requirements for the task and re-enter specifying either a sysout class or dataset name.
Reason:
An attempt was made to issue the allocate command using a DD name previously allocated.
System Action:
The command is rejected.
User Action:
Use a DD name that is not currently being used. The SHOW ALLOC command can be used to display those files SOLVE previously allocated with the ALLOCate command. Other DD names may also be in use that were part of the System Startup JCL.
Reason:
An attempt has been made to change the status (eg. ALLOC, UNALLOC) of a dataset of a format other than SYSOUT and the user has insufficient command authority. Unless changed by your installation, the status of SYSOUT format datasets can be changed by users with a command authority of 0. Changing the status of all other datasets requires a higher command authority, usually authority level 2.
System Action:
The command is rejected.
User Action:
Contact your systems administrator.
Reason:
Use of the USERID option requires a DESTID to nominate the destination node where the userid is defined.
System Action:
The command is rejected.
User Action:
Include a DESTID and retry.
Reason:
The specified terminal has been locked due to an inactivity timeout.
System Action:
The lock panel is displayed until the users password is entered.
User Action:
Enter your password to resume your work.
Reason:
Confirms that the TERMINAL command has been accepted.
System Action:
None.
User Action:
None.
Reason:
The specified terminal has been locked by the user issuing the LOCK command.
System Action:
The lock panel is displayed.
User Action:
Enter your password to unlock the terminal and resume your work.
Reason:
The LOCK command has been issued to lock a terminal, but the terminal is not valid for LOCK processing. Only LU1 and LU2 devices which have a signed-on user may be locked.
System Action:
The LOCK command is rejected.
User Action:
None.
Reason:
The LOCK command has been issued to lock a terminal, but the terminal is already in a locked state.
System Action:
The LOCK command is rejected.
User Action:
None.
Reason:
The LOCK command has been entered to lock a terminal. The terminal is in a disconnected state, so the LOCK command is invalid and has been rejected.
System Action:
The LOCK command is rejected.
User Action:
None.
Reason:
This message is first line of the response to e TERMINAL command with no operands. It describes the terminal type (VIRTUAL/STD/FJ/FJ3), LU-name and region type (LU1/LU2/BSYS/BMON/ROF/etc).
System Action:
None. More information follows in subsequent messages.
User Action:
None.
Reason:
This message is part of the TERMINAL COMMAND device characteristics display, and shows the default (aa,bb) and alternate (cc,dd) screen sizes for the device.
System Action:
None.
User Action:
None.
Reason:
This message is part of the TERMINAL command device characteristics display and shows which device characteristics (such as color, DBCS support and highlighting) are supported by the terminal.
System Action:
None.
User Action:
None.
Reason:
The SUBMIT command has been issued without operands.
System Action:
The command is rejected.
User Action:
Refer to the Command Reference for a description of this command.
Reason:
The SUBMIT command has been issued but the first operand, which specifies the target of the command, is not valid.
System Action:
The command is rejected.
User Action:
Refer to the Command Reference for a description of this command.
Reason:
The SUBMIT command has been issued without any command text.
System Action:
The command is rejected.
User Action:
Refer to the Command Reference for a description of this command.
Reason:
The SUBMIT command has been issued successfully to the nominated virtual region or real user for processing.
System Action:
None.
User Action:
None.
Reason:
The SUBMIT command has been issued correctly but the target virtual userid is not active and cannot receive the command.
System Action:
The command is rejected.
User Action:
Refer to the Command Reference for a description of this command.
Reason:
The SUBMIT command has been used with the USER= operand to execute a command in another user's OCS window. The command is rejected because the specified user is not logged on or has no OCS windows.
System Action:
The command is rejected.
User Action:
Ensure the correct userid has been specified.
Reason:
The SUBMIT command was issued with the AUTH parameter but the value specified in the AUTH parameter is not valid or has been omitted.
System Action:
The SUBMIT command is rejected.
User Action:
Correct the AUTH parameter value and retry. The value must be numeric and in the range 0-255.
Reason:
The SUBMIT command has been entered with the USER= operand but the command authority of the command issuer is not high enough to use the USER= operand.
System Action:
The SUBMIT command is rejected.
User Action:
The authority level required can be set using the SYSPARMS CMDAUTH command. Check with your systems administrator to find out why you do not have sufficient authority.
Reason:
An LUTRACE command was entered without any operands.
System Action:
The command is rejected.
User Action:
Re-enter the command with the appropriate operands.
Reason:
An LUTRACE command was entered requesting a trace of luname. However, a trace of this LUNAME is already active.
System Action:
The command is ignored.
User Action:
None.
Reason:
An LUTRACE command was entered requesting that a trace of luname be terminated. However, no trace is currently active for this LUNAME.
System Action:
The command is ignored.
User Action:
None.
Reason:
An LUTRACE command requesting a trace of luname has been accepted.
System Action:
If the LU is currently in session with SOLVE, a subsequent message will indicate that tracing has started. Otherwise, the request will remain in a pending state until the LU connects.
User Action:
None.
Reason:
An LUTRACE command requesting a trace of luname has resulted in the tracing of this LU. lutype indicates the type of LU.
System Action:
Trace messages will be sent to the activity log as traffic occurs on the session.
User Action:
None.
Reason:
A trace of luname is currently active as a result of an LUTRACE command. The device is a 3270-type device, and this message gives the screen dimensions which it is currently utilizing, and any alternate dimensions.
System Action:
None.
User Action:
None.
Reason:
LU tracing for the LU 'luname' has been terminated. The reason for the trace to be terminated is given. The LUTRACE STOP command may be used to disable the trace on an LU. LU traces are also terminated when the session between the LU and SOLVE is terminated.
System Action:
Tracing is terminated.
User Action:
None.
Reason:
An LUTRACE command requested that a trace of one or more LUs be terminated. This message confirms that the trace of luname has been terminated.
System Action:
Tracing is terminated.
User Action:
None.
Reason:
An LUTRACE command requested that tracing of all LUs be terminated. However, no tracing is currently active.
System Action:
The command is ignored.
User Action:
None.
Reason:
There is insufficient storage available to process an LUTRACE command.
System Action:
The command is ignored.
User Action:
If the problem persists, it is possible that the SOLVE partition or region size needs to be increased.
Reason:
This message confirms that the Abend Command has been cleared by the entry of the ABENDCMD command with no message text.
System Action:
The Abend Command is cleared.
User Action:
None.
Reason:
Confirms the successful setting of the Abend Command with the ABENDCMD command. The Abend Command set will be submitted to the operating system if SOLVE terminates abnormally.
System Action:
The text of the Abend Command is set.
User Action:
None.
Reason:
An attempt to set the Abend Command was refused because the command text supplied exceeded the maximum acceptable length of 60 characters.
System Action:
The command is rejected.
User Action:
Change the text so that it is not more than 60 characters long.
Reason:
An attempt to set the Abend Command has been refused because SOLVE does not have APF authorization to issue operating system commands.
System Action:
The command is rejected.
User Action:
If you wish to have an Abend Command, you will need to obtain APF authorization for SOLVE.
Reason:
A DEFLOGON or related command as incorrectly specified the use of the operand supplied in the message text.
System Action:
The command is rejected.
User Action:
Remove or correct the operand in error and retry the command.
Reason:
A DELLOGON, SUSLOGON or ACTLOGON command has been entered without the INPUT= or APPL= operand specified. This is invalid because one of these operands must be entered to identify which logon path is to be the subject of the command.
System Action:
The command is rejected.
User Action:
Specify the INPUT= or APPL= operand and retry.
Reason:
The OPSYS or NOTIFY command was entered without text.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
The OPSYS command may be used only if the region has APF authorization to issue operating system commands.
System Action:
The command is rejected.
User Action:
Refer this message to your systems administrator.
Reason:
An OPSYS or NOTIFY command has been passed to the operating system successfully and been accepted as syntactically correct.
System Action:
None.
User Action:
None.
Reason:
The text of the OPSYS command was not valid, and has been rejected by the operating system.
System Action:
None.
User Action:
Correct the command being passed and re-enter.
Reason:
The text of an OPSYS command has been passed to the operating system. No information will be available as to whether or not the command passed was valid.
System Action:
None.
User Action:
None.
Reason:
The OPSYS command is supported only under MVS or MSP.
System Action:
The command is rejected.
User Action:
None.
Reason:
An OPSYS CP command has failed because SOLVE could not obtain storage to receive the replies.
System Action:
The command is ignored.
User Action:
Investigate why SOLVE has a storage shortage.
Reason:
This message details one line of the response to an OPSYS CP command. The responses are terminated by message N12009.
System Action:
None.
User Action:
None.
Reason:
The message terminates the responses to an OPSYS CP command. The return code provided by VM/SP (nnn) is shown.
System Action:
None.
User Action:
None.
Reason:
The total size of the messages provided by VM/SP in response to an OPSYS CP command exceeds 8K. N12008 messages detailing responses up to this point will have been issued prior to this message. Message N12009 is not issued.
System Action:
None.
User Action:
None.
Reason:
The text of the command exceeds 126 characters and has been rejected by the operating system. This applies to MVS and MSP only which place a limit on the size of the (operating system) command. The NOTIFY command is equivalent to an OPSYS SEND command. It is the resultant OPSYS command which is restricted to 126 characters.
System Action:
The command is rejected.
User Action:
Shorten the command being passed and re-enter.
Reason:
A VTAM command was entered and a required operand was either missing or incorrect.
System Action:
The command is rejected.
User Action:
Refer to the command description in the Command Reference.
Reason:
A VTAM VARY, MODIFY or DISPLAY command was issued specifying a network resource which is not within the user's Network Partitions.
System Action:
The command is rejected.
User Action:
Network Partitions define the resources which a user is entitled to reference. If access to the resource is required, the appropriate NPF tables must be available to the user. Refer to the SHOW NPF and SHOW NPTAB commands to determine the resources which you are entitled to reference.
Reason:
A REPLY command was entered but the system is not at present receiving PPO messages.
System Action:
The command is rejected.
User Action:
Issue a PPO START command if required.
Reason:
A VTAM command was issued whilst the Secondary Program Operator (SPO) interface was inactive. The command cannot be processed until the SPO interface is active.
System Action:
The command is rejected.
User Action:
Check that the primary ACB has been defined with the SPO attribute.
Issue the STATUS command and review message N11423. If SPO is defined to run on the local domain use the SPO START command to re-activate SPO.
If SPO has failed due to a VTAM error then review the activity log for instances of message N09B02. Save the details and contact Technical Support.
Reason:
A SHOW TSO/TSS command was issued but SOLVE is not running in an operating system under which this command would be meaningful.
System Action:
The command is rejected.
User Action:
None.
Reason:
A SHOW TSO/TSS command cannot be processed unless your product region is authorized.
System Action:
The command is rejected.
User Action:
The product region must be APF authorized.
Reason:
The title line of the SHOW TSO/TSS display.
System Action:
None.
User Action:
None.
Reason:
Part of the SHOW TSO/TSS display, showing the number of users displayed, the number logged on, and the number of `starting' address spaces..
System Action:
None.
User Action:
None.
Reason:
Part of the SHOW TSO/TSS display; the current TSO/TSS MAXUSERS value.
System Action:
None.
User Action:
None.
Reason:
A SHOW TSO=data command was entered with the supplied data being longer than 8 characters.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
Underlines N12203.
System Action:
None.
User Action:
None.
Reason:
The detail line of a SHOW TSO/TSS command. Identifies the TSO/TSS userid, the terminal to which the user is logged on (node), the TSO/TSS applid used for their terminal session, the terminal type, the address space ID of the user and their TSO/TSS logon procedure name.
System Action:
None.
User Action:
None.
Reason:
The MSG command did not specify a destination for the message text.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
The destination name specified in a MSG command is invalid.
System Action:
The command is rejected.
User Action:
Use the SHOW USERS command to determine the names of userids or terminals to which you can send messages. Correct and retry.
Reason:
Destination name must be 1 to 8 characters in length.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
A MSG command was entered with no text.
System Action:
The command is rejected.
User Action:
Correct and re-enter. Text must be separated from destination name by a blank.
Reason:
The destination of a MSG command is not available.
System Action:
The command is rejected.
User Action:
Use the SHOW OCS command to determine the OCS operators or terminals to which you can send messages. Correct and retry.
Reason:
The destination of a MSG command cannot receive the message because the user is not at present in Operator Control Mode.
System Action:
The command is rejected.
User Action:
None.
Reason:
Confirms that the message from a MSG command has been successfully dispatched.
System Action:
If possible the message will be delivered to an active OCS window, if the OCS window is closed the message will be queued.
User Action:
None.
Reason:
A MSG ALL command has been executed.
System Action:
The message will be sent to all operators in OCS mode.
User Action:
None.
Reason:
An attempt was made to send a message to terminal or userid xxxxxxxx using the MSG command, but that terminal is currently either powered off or otherwise unavailable.
System Action:
The message has not been sent.
User Action:
The terminal could be unavailable because it is in 'test' mode or in an SSCP session (SYSREQ pressed), or powered off. Retry later.
Reason:
An attempt was made to send a message to terminal or userid xxxxxxxx using the MSG command, but that environment has a profile which prevents the message being received.
System Action:
The message has not been sent.
User Action:
None.
Reason:
A GO or END command was entered, but the target NCL process is not currently PAUSED.
System Action:
The command is ignored.
User Action:
None.
Reason:
A flush command has been entered and accepted.
System Action:
The current NCL procedure is terminated without further processing.
User Action:
None.
Reason:
A FLUSH command was entered, but there was no EXEC, FSPROC, NCLCHECK, START or LIST in progress to flush.
System Action:
The command is ignored.
User Action:
None.
Reason:
The command aaaa cannot be issued for the target NCL process.
System Action:
The command is ignored.
User Action:
None.
Reason:
A GO, END, INTQ or FLUSH command was entered, but the target process is not running in the nominated NCL processing environment.
System Action:
The command is ignored.
User Action:
Check that you have specified the correct NCL identifier.
Reason:
A GO, END, INTQ or FLUSH command was issued without specifying an NCL identifier. More than one NCL process is active in the NCL processing region and an identifier is required.
System Action:
The command is ignored.
User Action:
Specify the identifier of the required target process.
Reason:
An INTQ command specified no text to be passed to the target process.
System Action:
The command is ignored.
User Action:
Supply the INTQ text as required.
Reason:
An INTQ command was issued to pass a message to an NCL process. The process already had a backlog of messages queued to its &INTREAD queues. No more messages can be queued to the process until the backlog is reduced.
System Action:
User Action:
Establish why there is a backlog of unprocessed messages queued to the
Reason:
The NCL identifier used to identify an NCL process that is the target of a command is not valid. It should be a number in range 1-999999.
System Action:
The command fails.
User Action:
Correct and retry.
Reason:
A FLUSH or END command operand is unrecognized.
System Action:
The command is rejected.
User Action:
Review the command string in error. The ID operand may have been incorrectly specified.
Reason:
An INTQ command was issued which specified an unrecognized value for the TYPE operand.
System Action:
The command is ignored.
User Action:
Correct and retry.
Reason:
An END command has been entered, but the target procedure is an OML procedure. OML does not support the use of the END command to terminate
System Action:
User Action:
Reason:
An END command has been entered but the target NCL procedure has called an OML procedure. OML does not support the use of the END command to terminate a nesting level.
System Action:
None.
User Action:
None.
Reason:
The TIMER command with the purge ID of x has been automatically purged as the limit specified in the LIMIT operand when the command was defined has been reached.
System Action:
None.
User Action:
The timer command must be re-entered if further execution is required.
Reason:
The TIMER command with the purge ID of x has been automatically purged as the specified USERID xxxxxx has exited Operator Control Mode.
System Action:
None.
User Action:
None.
Reason:
The operand xxxxxxxx of the PURGE command is invalid.
System Action:
The command is rejected.
User Action:
Correct the error and retry.
Reason:
The value of the operand xxx in the PURGE TIMER=xxx command is invalid or out of range. The valid operands are OWN, ALL or purge id number (nnnn).
System Action:
The command is rejected.
User Action:
Correct the error and retry.
Reason:
Operands of the PURGE command that must be entered have been omitted.
System Action:
The command is rejected.
User Action:
Correct the error and retry.
Reason:
The purge ID number specified in the PURGE command does not exist.
System Action:
The command is rejected.
User Action:
You may have inadvertently specified an incorrect ID number, or the timer command may have already been automatically purged due to its execution limit having been reached. Use the SHOW TIMER command to verify the purge ID, correct the error if necessary, and retry.
Reason:
You attempted to purge a timer command created by another user. This function requires a higher authority level than you have.
System Action:
The timer command is not purged.
User Action:
Have your authority level increased if it is necessary to perform this function.
Reason:
Issued in response to a PURGE TIMER=OWN, ALL or id command.
System Action:
nn timer commands have been purged.
User Action:
None.
Reason:
You have entered a PURGE TIMER=ALL command and are not authorized to do so.
System Action:
No timer commands have been purged.
User Action:
Have your authority level increased if it is necessary for you to be able to purge all timer commands.
Reason:
Issued in response to a PURGE TIMER=nn command.
System Action:
The indicated timer command has been purged.
User Action:
None.
Reason:
You attempted to purge a timer command, but none are active.
System Action:
The command is rejected.
User Action:
The timer command(s) you were attempting to purge may have already been automatically deleted.
Reason:
The nominated LOCK request either does not exist or is not in a waiting state.
System Action:
The command is rejected.
User Action:
None.
Reason:
The nominated LOCK has been successfully purged.
System Action:
None.
User Action:
None.
Reason:
The PURGE command for the nominated LOCK was not successful in deleting the LOCK.
System Action:
The command fails.
User Action:
Identify the holder(s) of the lock and cancel the associated NCL processes if the LOCK is causing problems to other NCL processes.
Reason:
You do not have authority to purge LOCKs.
System Action:
The command is rejected.
User Action:
None.
Reason:
A PURGE NRD= command has been issued by a user who does not have a command authority level high enough for the command.
System Action:
The command is ignored.
User Action:
Refer to your systems administrator.
Reason:
A PURGE NRD= command to purge non-roll delimiter (NRD) messages based on domainid aaaa has been successful.
System Action:
None.
User Action:
None.
Reason:
A PURGE NRD= command to purge Non-Roll Delete (NRD) messages based on a time interval has been successful and has deleted aaaa messages.
System Action:
None.
User Action:
None.
Reason:
A PURGE NRD= command to purge non-roll delimiter (NRD) messages based on NCLID aaaa has been successful.
System Action:
None.
User Action:
None.
Reason:
The PURGE command was issued to cause cessation of INQUIRE APPSTAT processing for the nominated application. The application was not subject to APPLSTAT processing. See the SYSPARMS APPLSTAT command and the &APPSTAT NCL verb for more details.
System Action:
The command is rejected.
User Action:
None.
Reason:
A PURGE APPLSTAT=aaaaaaaa command has been issued to cancel INQUIRE APPSTAT processing for application aaaaaaaa. INQUIRE APPSTAT processing has now been terminated for the application.
System Action:
None.
User Action:
None.
If you want to monitor the application status periodically, use the APPLSTAT command to start this monitoring.
Reason:
A PURGE APPLSTAT= command has been rejected. The SOLVE system is not running under VTAM, so the APPLSTAT operand is invalid.
System Action:
The PURGE command is rejected.
User Action:
None.
Reason:
An invalid operand was entered on a SHOW TIMER command.
System Action:
The command is rejected.
User Action:
Correct the error and retry.
Reason:
Issued in response to a SHOW TIMER=ALL command, when no timer commands are active.
System Action:
None.
User Action:
None.
Reason:
This is the heading line for the SHOW TIMER display.
The heading message is followed by pairs of detail lines (N12704 and N12707) for each TIMER command.
Is the timer command purge ID.
Is AT (AT), EV (EVERY), AF (AFTER), or *+ (AT *+interval), indicating the type of timer.
Is, for EVERY, the repeat frequency, or, for AT, the time of day at which command will next execute. The interval is in the format hh.mm.ss.
If this is an AT timer with TZ=GMT or TZ=UTC, a Z follows the interval (time of day) to indicate that this is the GMT or UTC time.
Is the user ID under whose control command will be executed. Commands executing under the Background Monitor show a user ID of B/G-MON, and those executing under the Background Logger show a user ID of B/G-LOG. A user ID of STARTUP indicates that the commands are in the NMINIT or NMREADY initialization procedures where no specific user ID is assigned.
Displays an asterisk (*) if this timer command was routed to this user ID by the ROUTE operand. This command will not be purged automatically if the user ID is not logged on, unless a limit is specified using the LIMIT operand.
Specifies the number of times the command will be executed before automatic purging takes place. A limit of zero indicates that no limit applies.
Is the number of times the command has already been executed. This count is not incremented if the timer interval expires and the user ID is not logged on.
Specifies the value of the KEEP operand if it was entered when the command was created.
NO indicates that no KEEP function is in effect.
MON indicates that if the user ID is not logged on and the timer interval expires, the command will execute under control of the Background Monitor and the results will be routed to all monitor terminals.
LOG indicates that if the user ID is not logged on and the timer interval expires, the command will execute under the control of the Background Logger and the results will be routed to the activity log.
If specified, the KEEP operand takes precedence over the ROUTE operand if the user ID is not logged on.
Displays a set of 1-character flags:
E identifies the environment: P is primary, and C is current.
P displays the Pmsg option: Y is Yes, and N is No.
Z identifies the time zone: L is Local, and U is UTC or GMT.
F displays the FTC (Forward Time Change) option: S is Skip, and T is Trip. A dash (-) indicates that the FTC option is not relevant because the timer was defined with TZ=UTC or TZ=GMT.
B displays the BTC (Backward Time Change) option: S is Skip, and R is Repeat. A dash (-) indicates that the BTC option is not relevant because the timer was defined with TZ=UTC or TZ=GMT.
Is the user assigned timer identification. Purge message is issued when the timer command expires.
Is the *local* time at which the timer will pop next. If a backward time change occurs for a timer that has BTC=SKIP, the next logical pop time will be skipped and is indicated by a plus sign (+) following the time.
System Action:
Further display lines follow.
User Action:
Read the display lines that follow.
Reason:
Follows message N12703 and gives details of a timer command. See message N12703 for details. The command or message text is detailed in the following message, N12707.
System Action:
None.
User Action:
None.
Reason:
Gives a count of the number of preceding N12704 messages.
System Action:
None.
User Action:
None.
Reason:
Issued in response to a SHOW TIMER command, where the default operand of OWN has taken effect, and there are no active timer commands for the user.
System Action:
None.
User Action:
Use the SHOW TIMER=ALL command if timer commands other than those created by this userid are to be displayed.
Reason:
Follows message N12704 and gives details of the command or message that is associated with a timer command.
System Action:
Command text may wrap to a second line if length exceeds available display space.
User Action:
None.
Reason:
An attempt was made to change the authority of a command using the SYSPARMS CMDAUTH= command. You do not have authority to do so.
System Action:
The command is rejected.
User Action:
Have your authority level increased if it is necessary to perform this function.
Reason:
The operand xxxxxxx of the SYSPARMS command has an invalid or out-of- range value.
System Action:
The operand is rejected and processing continues.
User Action:
Correct the invalid value and enter the SYSPARMS command with that operand only.
Notes:
- SYSPARMS UNLOAD, MODDEL, MAPDEL, and MAPRESET have been replaced by the UNLOAD command.
- SYSPARMS PRELOAD, MODLOAD, and MAPLOAD have been replaced by the LOAD command.
- SYSPARMS APPLSTAT has been replaced by the APPLSTAT command.
Reason:
A SYSPARMS command was entered with no operands.
System Action:
The command is rejected.
User Action:
Specify an operand.
Reason:
Issued in response to a SYSPARMS command.
System Action:
The operand is now in effect. A completion message may follow for some operands.
User Action:
None.
Reason:
Certain operands of the SYSPARMS command may only be used in the NMINIT initialization procedure. One of these, oprnd, has been specified after system initialization.
System Action:
The operand is rejected.
User Action:
If the operand is required, it should be included in a SYSPARMS command in the NMINIT procedure, which is processed before the region initialization is complete.
Reason:
To change the SOLVE ACB name the ACB must first be closed.
System Action:
None.
User Action:
Close the ACB and retry the command.
Reason:
A SYSPARMS PRIACBNM= command has been unsuccessful because a VTAM MODCB macro failed. The R15 and R0 feedback from MODCB is shown.
System Action:
The command is rejected.
User Action:
Refer to the VTAM Programming manual, return codes.
Reason:
A SYSPARMS command has been rejected because the specific operand aaaa is not valid for this operating system.
System Action:
The command is ignored.
User Action:
None.
Reason:
SYSPARMS operand aaaaaaaa is obsolete.
System Action:
The SYSPARMS command is rejected.
User Action:
None.
Reason:
If SYSPARMS SYSPGCHK=YES is specified (by default), all SYSPARMS operands that have been set using a Customizer parameter group can be updated only by using Customizer. You cannot execute SYSPARMS operands using the SYSPARMS command.
A request to set SYSPARMS operand ( P1 ) has failed because it was previously set by execution of the identified parameter group ( P2 ) and SYSPARMS SYSPGCHK=YES.
System Action:
The SYSPARMS command is rejected.
User Action:
To maintain integrity, this SYSPARMS operand should be updated using the Customizer parameter group identified.
If this SYSPARMS command was executed in an NCL procedure (either directly or using the &INTCMD verb), update the procedure to remove it. The value must be set by updating and actioning the parameter group. To bypass integrity checking, specify SYSPARMS SYSPGCHK=NO and reissue the (original) SYSPARM. Any SYSPARMS outside of Customizer are not reflected in the parameter group. If you bypass checking, we recommend that you synchronize the system with Customizer as soon as possible.
To synchronize the system: 1. Issue SYSPARMS SYSPGCHK=YES. 2. Update and action the Customizer parameter group.
Reason:
A SYSPARM COMMAND has failed because there is insufficient system storage to process the request.
System Action:
The SYSPARM command fails.
User Action:
Retry the command.
If the problem persists, check storage requirements and increase the region size if necessary.
Reason:
A SHOW OCS command was entered but no users logged on to the system are in Operator Control Mode.
System Action:
None.
User Action:
None.
Reason:
This message is title line of the SHOW OCS display. The messages following this message supply information about OCS operators.
System Action:
None.
User Action:
None.
Reason:
One of these messages is issued for each user currently logged on in Operator Control Mode. The display lines up under the title line (message N12902). The status (status) displayed may be REMOTE (the user has an ROF session from a remote system), ACTIVE, CLOSED (the user's OCS window is currently closed), or UNAVAIL (the user is logged on but the terminal is powered off).
System Action:
None.
User Action:
None.
Reason:
Signifies the end of the SHOW OCS display.
System Action:
None.
User Action:
None.
Reason:
A PROFILE command was used to change the user's INITCMD, but the user's userid information could not be accessed, either because of an I/O error on the UAMS dataset or because the security exit in use rejected the request to update the userid.
System Action:
The command is rejected.
User Action:
Retry. Report occurrence to the systems administrator if this condition persists.
Reason:
A PROFILE command was used to change the user's INITCMD but the update of the user's userid information failed.
System Action:
The command is rejected.
User Action:
Report the occurrence to the systems administrator for determination of the error cause.
Reason:
When calling a security exit to read a UDB insufficient storage was available to create the parameter list for the call.
System Action:
Request fails, system may eventually fall over due to lack of storage.
User Action:
Possibly wait until more storage is available. (if system stays up- system may eventually fall over due to lack of storage).
Reason:
This message is issued from nm000130 when processing a PROFILE INITCMD.
System Action:
Refer to the embedded message. It may be issued from local UAMS or by a security exit.
User Action:
Determine the origin of the message and refer to that message.
Reason:
A ROUTE command was entered without specifying the destination to which
System Action:
User Action:
Use the SHOW LINKS command to determine the destination name of the system to which the command is to be routed. A link name must be
Reason:
A ROUTE command was entered which did not specify any command text to be routed to the destination SOLVE for execution.
System Action:
The command is rejected.
User Action:
Include some command text on the ROUTE command.
Reason:
System Action:
User Action:
Retry the command. Notify your Systems Administrator if the condition
Reason:
A ROUTE command specified a destination system to which there is no
System Action:
User Action:
Use the SHOW LINKS command to determine the status of the link to the specified destination, and retry the command when the link is active.
Reason:
The ROUTE command has been issued with the LINK or DOMAIN or SSCP operand specified but the value of the operand is invalid.
System Action:
The command is rejected.
User Action:
Correct the value of the invalid operand and retry.
Reason:
An attempt has been made to execute a ROUTE command from an environment which does not support ROF connections. ROF connections are only supported from OCS, indirectly through ROF, from background regions (eg. BMON, BSYS, etc) and from &INTCMD environments.
System Action:
The command is rejected.
User Action:
Correct the way in which the ROUTE command is being executed. If the ROUTE command is to be executed from a fullscreen procedure then &INTCMD must be used.
Reason:
A ROUTE command to a remote system failed because the queue of messages already queued to that system for transmission exceeds the system
System Action:
User Action:
Establish whether there is a problem that is causing the backlog of
Reason:
A Remote Operator Facility command string exceeds 250 characters and the remote system does not handle commands beyond this limit.
System Action:
The command is truncated at the 250 character limit.
User Action:
Shorten the command string by using abbreviations.
Reason:
This message is issued in response to a SHOW DEFLOGON command to indicate that SOLVE has processed a SUSLOGON APPL=applname command, and will prevent all logon attempts to this application through the use of either MAI-FS or EASINET.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW DEFLOGON command to indicate that SOLVE has processed a SUSLOGON APPL=ALL command, and will prevent all logon attempts to any application through the use of either MAI-FS or EASINET.
System Action:
None.
User Action:
None.
Reason:
The SHOW DEFLINK command has been entered with an operand other than the TYPE= operand or the TYPE= operand was specified with an invalid value.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
A SHOW DEFLOGON command was issued but no logons have been defined to the system.
System Action:
None.
User Action:
If you wish to logon to an external application you will need to use the DEFLOGON command to establish a logon path.
Reason:
This is the title line of the display resulting from a SHOW DEFLOGON command. The message will be followed by detail lines (N13206 or N13208) each of which may be followed by messages N13207 and/or N13209 if relevant. The display is terminated by message N11907.
System Action:
None.
User Action:
None.
Reason:
The response to a SHOW DEFLOGON command. One of these lines is displayed for each DEFLOGON entry, and shows the contents of the entry. The fields line up under the title line display N13205.
System Action:
None.
User Action:
None.
Reason:
Part of the multiline SHOW DEFLOGON display. Details the DEFLOGON description for the logon path identified in the previous message (N13206 or N13208) only if the description is present.
System Action:
None.
User Action:
None.
Reason:
This message has the same content as message N13206, but is displayed in high intensity to indicate that its use has been suspended by a SUSLOGON command.
System Action:
None.
User Action:
None.
Reason:
Part of the multiline SHOW DEFLOGON display. Details the suspended logon text for logon path identified in the previous message (N13208).
System Action:
None.
User Action:
None.
Reason:
A SHOW DEFLINK or SHOW DEFLINK TYPE="aaaa" command was issued but no dynamic link definitions have been defined to the system.
System Action:
None.
User Action:
None.
Reason:
This is the title line of the display resulting from a SHOW DEFLINK TYPE=INMC command. It provides a heading or subheading for links defined using a mask.
System Action:
None.
User Action:
None.
Reason:
This is the detail line of the display resulting from a SHOW DEFLINK or SHOW DEFLINK TYPE=INMC command. One such line is displayed for each dynamic link definition in the system.
aaaa if the heading for this line is message N13211 this field is the mask value for this definition, with asterisks showing wildcard positions. When a remote system attempts to establish a link to this system, the mask value determines whether this dynamic link definition will be used to build the link. For the definition to be selected, the mask value must match the userdata passed on the logon from an NMPC system or the domain-id of the remote host SOLVE system. If the heading for this line is message N13214 this field is the luname of the remote system.
bbbb if the heading for this line is message N13211 this field is the 4-letter prefix which will be concatenated to the VTAM node name of the remote system to give its dynamic link name. If the heading for this line is message N13214 this field is the linkname.
cccc is the msgid which will be assigned to all dynamic links built from this definition.
dddd is the color to be used when displaying messages about any dynamic link built from this definition.
eeee is the highlight type to be used when displaying messages about any dynamic link built from this definition.
ffff is the retry interval (in seconds) to be used when restablishing any dynamic link built from this definition.
gggg is the access method that will be used to establish sessions for this link.
System Action:
None.
User Action:
None.
Reason:
This is a title line of the display resulting from a SHOW DEFLINK or SHOW DEFLINK TYPE=INMC command. It provides a heading or sub-heading for all links defined with an LUNAME operand.
System Action:
None.
User Action:
None.
Reason:
This is the title line of the display resulting from a SHOW DEFLINK TYPE=APPC command. It provides a heading or subheading for links defined using an LUNAME.
System Action:
None.
User Action:
None.
Reason:
This is the title line of the display resulting from a SHOW DEFLINK TYPE=APPC command. It provides a heading or subheading for links defined using a mask.
System Action:
None.
User Action:
None.
Reason:
This is the detail line of the display resulting from a SHOW DEFLINK TYPE=APPC command. Fields shown relate to the headings provided by message N13215 or N13216 and are as follows:
aaaa the complete luname of the remote end or an luname mask.
bbbb either the linkname (heading is N13215) or a four character prefix (heading is N13216).
cccc the four character qualifier to be used for this destination to qualify transaction identifiers.
dddd the name of the Option Set Control Table entry to be used to determine the options supported by the remote LU.
eeee is the color used when displaying any messages that relate to this link.
ffff is the highlight type used when displaying any messages that relate to this link.
gggg specifies whether or not link messages are to be displayed as monitor messages.
hhhh specifies whether APPC user region creation will be link dependent (ENV) or link independent (GBL) for a given userid.
iiii indicates whether LU 6.2 session tracing is to be used.
jjjj the access method that will be used to initiate sessions.
System Action:
None.
User Action:
None.
Reason:
This message displays the second header line of a SHOW DEFLOGON command. The heading identifies the attributes of a DEFLOGON detailed by an N13219 message.
System Action:
None.
User Action:
For more information, see the online help for the N13219 message.
Reason:
This message displays the second detail line from a SHOW DEFLOGON command. The following fields relate to the headings provided by the N13218 message:
Is the 1- to 5-character prefix used by MAI-FS as the basis for selecting a pseudo-terminal.
Identifies the function key that is recognized by the application as a request for screen refresh. For example, under CA SOLVE:Access, this key is CLEAR.
Is the BEFORE/AFTER value indicating whether MAI-FS is to propagate responses from the physical terminal or respond before sending the data to the terminal.
Is the time in minutes that is used by MAI-FS to set the period starting from keyboard unlock before MAI-FS initiates a time-out action.
Identifies the time-out action to be taken by MAI-FS:
Cancels the session conditionally.
Cancels the session.
Issues an Event Distribution Services message.
Invokes the session script in END mode.
Invokes the session script in SKIP mode.
Indicates whether EASINET uses the VTAM third-party notification facility when establishing sessions.
Indicates whether the application's status is queried before establishing sessions (MAI-FS and EASINET).
Is the number of active MAI-FS sessions using this entry.
Is the maximum number of concurrent active sessions.
Is the application name to use when encoding a passTicket. A '-' indicates that a passTicket is not generated.
System Action:
None.
User Action:
None.
Reason:
This is the third detail line of the display resulting from a SHOW DEFLOGON command. This line shows the session script details ( P1 ) and corresponds to the DEFLOGON SCRIPT parameter. The line is only displayed if the SCRIPT parameter is specified.
System Action:
None.
User Action:
None.
Reason:
An EQUATE command was entered but no character string to which the command string is to be equated was entered.
System Action:
The command is rejected.
User Action:
Correct and retry the command.
Reason:
The EQUATE command allows a string of between 1 and 8 characters to be equated to another text string. An EQUATE command has been entered which has attempted to set an equated value for a string of more than 8 characters.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
An EQUATE string has been entered which attempted to set an equate for a string which is not supported. The equate string may not have a suppression character (-) as the first character and may not contain ampersands ( ).
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
An EQUATE command was entered specifying an equate string but no text. This form of the EQUATE command is only valid when the EQUATE command is intended to delete an existing EQUATE.
System Action:
The command is rejected.
User Action:
The EQUATE may have already been deleted. If not, some text must be specified on the EQUATE command.
Reason:
An EQUATE command has been entered which specifies more than the maximum of 130 characters of text.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The EQUATE for string xxx has been deleted by an EQUATE command. There is no longer an equated value for the string xxx.
System Action:
None.
User Action:
None.
Reason:
An EQUATE command has been completed successfully. Entry of the string xxx will cause the equated text to be substituted in place of xxx before command execution.
System Action:
None.
User Action:
None.
Reason:
The specified string, defined as a global or system wide EQUATE value, has been reset for this particular operator window by the entry of an EQUATE command. It remains available for other operator windows that have not also reset it.
System Action:
If the equated string is entered in this environment, the global equated string will not be substituted in its place.
User Action:
None.
Reason:
The use of `+' indicates that a blank character is required at the end of the equated text or string, consequently a single `+' is equivalent to equating to a blank, which is invalid.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
You attempted to define an equate, but the selected equate string exactly matches an existing command. This is invalid after system initialization completes.
System Action:
The command is rejected.
User Action:
Select another string that does not conflict with another command. It is possible to replace an existing command with an equated string if you place the EQUATE command in the NMINIT NCL procedure that is executed automatically during system initialization. Using this technique, you can force an existing command to execute an alternative command or an NCL procedure if required. Another method of executing an NCL procedure in preference to executing a command is using the SYSPARMS CMDREPL command.
Reason:
You attempted to define an equate, but the selected equate string matches a valid abbreviation for an existing command. This is invalid after system initialization completes.
System Action:
The command is rejected.
User Action:
Select a string that does not conflict with another command.
Reason:
This message is issued when an EQUATE command in either NMINIT or NMREADY has exactly matched an existing SOLVE command and has replaced it. Each time the command is entered it will be translated into the equated string and the equated string will be executed in place of the original command.
System Action:
The equated string replaces the command for all users.
User Action:
If replacement of the command was intended, no action is required. If replacement was not intended, choose an alternative equate. The SHOW EQUATES command will show a TYPE of REPL for any equate that replaces a command. Local equates cannot be used to over-ride REPL equates. An alternative to replacing a command with an NCL procedure is to use the SYSPARMS CMDREPL command.
Reason:
You have defined an equate that matches an equate defined at system initialization, which was given the REPL attribute because it replaced an existing command. An equate that replaces an existing command is classified as fixed and cannot be replaced by a local equate.
System Action:
The command is rejected.
User Action:
Choose an alternative equate string.
Reason:
The EQUATE command may only be issued from an OCS environment, such as a logged-on user or a console. It cannot be issued from a system procedure environment. If the EQUATE command is issued using &INTCMD, the EQUATE command applies to the primary environment in which the procedure is executing.
System Action:
The command is rejected.
User Action:
None.
Reason:
Part of the PROFILE display. Indicates the name of the User Services NCL procedure that will be executed on selection of the User Services option from the SOLVE Primary Menu.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. MSGCODE specifies a mask of 2 hexadecimal digits, 00- FF . NCL procedures may specify &WRITE MSGCODE=aa to control delivery of messages. Only if the bits set on the &WRITE statement are also set in the users MSGCODE setting will the message will be written to that users screen.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. CMDSEP specifies whether or not semi- colons may be used to separate multiple commands entered on the command line.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE display. NCLTEST specifies whether preloaded, autoshared, or retained NCL procedures can be used by this NCL environment. NO indicates they can be used (not test mode). YES indicates a private copy of an NCL procedure will always be used, and that this copy will never be autoshared or retained.
System Action:
None.
User Action:
None.
Reason:
This message is part of the PROFILE display. It tells you whether or not all messages, including those from your local system, will be prefixed by the originating system id when displayed in this environment.
System Action:
None.
User Action:
None.
Reason:
This message is part of the PROFILE display. It tells you whether or not this environment is to receive messages generated by the MSG command.
System Action:
None.
User Action:
None.
Reason:
This message is part of the PROFILE display. It tells you whether or not unsolicited messages (PPO, AOM, monitor messages, broadcasts, etc) will be displayed in this environment. If UNSOL=YES, then unsolicited messages will be received as determined by individual message category options (such as PPOMSG=YES/NO). UNSOL=NO overrides 'YES' settings for individual message categories.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE command display. This message indicates the setting of the EXIT option for Operator Console Services. xxx indicates whether OCS allows termination whilst NCL processes remain active. Values are:
YES - OCS termination proceeds.
NCL processes are flushed.
NO - OCS termination is prevented when NCL processes are active.
WARN - A warning message is issued if NCL processes are active. A subsequent termination request without further command input will exit OCS.
An N23001 message is issued if OCS termination is prevented.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE list display, which supplies the current multi-line message indentation factor, nn. Messages to an OCS screen which are split over more than one line will have all lines other than the first indented by nn columns.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE list display, which supplies the Library Services Path name which is used to locate all Panels used by NCL procedures executing in this environment.
System Action:
None.
User Action:
None.
Reason:
Part of the PROFILE list display, which shows the number nn of Event Distribution Services profiles active in the environment.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a PROFILE display command. The NCLUCASE attribute of the Operator Console Service environment is set to either 'YES' or 'NO'. A value of 'YES' indicates that parameters passed to NCL will be uppercased. A value of 'NO' can be used to pass parameters as entered in the OCS command line.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a PROFILE display command. It shows the user time zone name and GMT (UTC) time offset.
Note: A time zone name of SYSTEM means that this user is using the region local time offset.
If the offset is greater than one day, the number of days is shown and the hhmm is the remainder.
System Action:
None.
User Action:
None.
Reason:
This is the title line of the SHOW EQUATES display.
System Action:
None.
User Action:
None.
Reason:
This is an information line from the SHOW EQUATES display. One of these display lines is issued for each equated string available to this operator window. string is the equated string, type signifies whether the value is global (GLBL) and hence available to all users on entry to Operator Control Mode or local (LOCL) to this window only, or has replaced a SOLVE command (REPL). text.... is the text equated to the string.
System Action:
None.
User Action:
Equates with a type of LOCL will be lost when exiting from Operator Control Mode. Equates with a type of GLBL will always be available unless a LOCL equate has been defined to replace the GLBL equate. LOCL equates are only valid for use from the operator window from which they were defined. Equates with a type of REPL have replaced a SOLVE command of the same name and cannot be overlayed or replaced by the definition of a LOCL equate.
Reason:
Signifies the end of the results of a SHOW command.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW EQUATES command if no EQUATE commands have been processed.
System Action:
None.
User Action:
None.
Reason:
This is the title line of a SHOW LINKS display.
System Action:
None.
User Action:
None.
Reason:
This is a display line issued as a result of a SHOW LINK command. One such line is issued for each link that matches the selection criteria on the SHOW LINKS command. Additional messages provide the status of each of the link's sessions.
linkname is the INMC name by which the remote system is known within the system.
status is the current link status. Possible values are:
ACTIVE One or more sessions are open between the two systems and traffic may flow between them.
PEND-ACT This system is attempting to contact the remote system.
STARTING The two systems have made contact and INMC initialization is underway. This involves a protocol exchange to authorize and aid startup. STOPPED The link between the two systems has been broken by use of a LINK STOP command.
FAILED An error has occurred on one or more of the sessions that comprise the link.
DISABLED The link between the two systems has been disabled due to inadequate licensing authorization.
mode is the mode in which the link operates, values being `S' (Simple mode) `P' (Preferential) or `R' (Rotate and Backup').
msgid is the default prefix assigned to messages received from the remote system.
node is the network node name of the remote system.
type is the link type, either DYN (dynamic) or STAT (static).
peer descibes the remote system as either a HOST or PC.
timediff is the difference between the internal (hardware) clock times on this system and the remote system. The difference is expressed as plus or minus hh:mm:ss.th (relative to this system). This value may not match the apparent difference between the time-of-day clocks on the two systems, since time-of-day may be offset from the internal clock values.
System Action:
None.
User Action:
If the link status is 'FAILED' then this indicates an unrecoverable error has occurred on the link. Additional log messages will provide the failure reason and should be reported to your product support representative.
A link status of 'DISABLED' indicates that one or both systems are not licensed sufficiently. Report the error to your product support representative.
Reason:
A SHOW LINKS command was specified but there are no links defined that match the specified name or prefix.
System Action:
None
User Action:
None
Reason:
This message is issued in response to a SHOW USERS display, if there are no users currently logged on to the system.
System Action:
None.
User Action:
None.
Reason:
This is the title line of the SHOW USERS display.
System Action:
None.
User Action:
None.
Reason:
This message forms part of the SHOW USERS display. One of these messages is issued for each user currently logged on to the system.
userid Is the logon user ID. This field is displayed in high intensity for the user that issued the display command.
terminal Is the region name. This is the logical unit name of the terminal at which the user is logged on. A numeric reconnection identifier is displayed for disconnected regions. *REMOTE* is displayed for users logged on from a remote system using ROF. This field is displayed in high intensity for the region that issued the display command.
type Is a mnemonic indicating the type of terminal being used:
AOMP - AOMPROC system procedure region
BAOM - background AOM region
BLOG - background logger region
BMON - background monitor region
BSVR - background server region
BSYS - background system region
CNMP - CNMPROC system procedure region
LOGP - LOGPROC system procedure region
OPER - system console
PPOP - PPOPROC system procedure region
3270 - display terminal (LU-type 2)
LU1 - line mode terminal (LU-type 1)
VDU - display terminal in a Fujitsu system
ROF - remote user (this is followed by the link name for the remote system)
status Contains additional information concerning the user region. The values may indicate the following:
LOCK The region is currently under the control of the LOCK function due to timeout or command.
DISC The region has been detached from the logical terminal due to timeout or the DISCONN command. Additional fields supply the terminal name and time of the disconnection.
TO link The user region has a ROF connection to the remote system named by 'link'.
FROM link The user region is a ROF connection from the remote system named by 'link'.
PENDING A ROF connection has been requested to a system for which the link is not active.
RECOVERY pending automatic recovery.
(U/A) An LUSTAT has been received indicating that the device is unavailable. This generally indicates that the device has been powered off.
System Action:
None.
User Action:
None.
Reason:
Issued at the end of a SHOW USERS command. Gives a count of the number of users logged on and the number logged on but currently disconnected.
System Action:
None.
User Action:
None.
Reason:
Provides an underline to the title line of the SHOW USERS display (N13509).
System Action:
None.
User Action:
None.
Reason:
Part of the SHOW USERS display, one such message appears for each connection that the user has to a remote SOLVE system. Type is INMC, NVC or APPC. Linkname is the name by which the remote SOLVE was defined in a LINK command and is the name to be used in ROUTE commands to that system. Status will be RECOVERY if the signon has failed at some time in the past owing to LINK failure. The signon will automatically be recovered when the link is re-established. Alternatively, status will be PENDING if a signon command was entered before a link to a remote SOLVE system was established. The signon will automatically complete when the link becomes active.
System Action:
None.
User Action:
None.
Reason:
A SHOW REPLIES command was issued but no VTAM messages that require replies are outstanding.
System Action:
None.
User Action:
None.
Reason:
The heading line of the SHOW REPLIES display.
System Action:
TIME is the time of day the message was intercepted. R/# is the reply number that will have to be used when replying to the message.
User Action:
See the following N13516 messages.
Reason:
The text and receipt time of a VTAM message that requires or required a reply.
System Action:
None.
User Action:
The REPLY command can be used to reply to a message if no reply has already been issued. The reply number is in the format x## where x is the letter `P' or `S' and ## is in the range 00-99. When replying to a message the exact format of the reply number must be used. The P and S is used internally by SOLVE to determine how to return the reply to VTAM. Example: REPLY P00,YES
Reason:
A SHOW NCLSTAT command was issued when there were no NCL procedures preloaded or auto-shared.
System Action:
None.
User Action:
None.
Reason:
The title line of the SHOW NCLSTAT display.
System Action:
None.
User Action:
None.
Reason:
The detail line of a SHOW NCLSTAT display.
NAME - identifies the name of the NCL procedure.
STATUS - states whether the procedure is PRELOADed, AUTO-SHRed, LOADING or P-UNLOAD, RETAINED, CMDREPL, PRIVATE or NCLTEST.
USERS - is the number of users referencing the procedure.
REFCNT - is the number of times this copy of the procedure has been referenced since it was loaded.
STMTS - is the number of statements in the procedure.
KBYTES - is the number of Kilo Bytes the procedure occupies in virtual storage.
LIBRARY - is the procedure's library DD name.
AGEUSE - is used to keep a count of the "age" of the retained procedure. Procedures that have a status of "P-UNLOAD", will be deleted only when the current user count reaches zero, subsequent requests for this procedure will result in a new copy of the procedure being loaded, and as such it is possible to have multiple copies of a procedure in storage at any one time.
USERID - is the userid initiated the procedure with the PRIVATE, LOADING or NCLTEST status (this field replaces AGEUSE).
System Action:
None.
User Action:
None.
Reason:
A SHOW VSAM command has failed, either due to a lack of storage or a VSAM error.
System Action:
The command is terminated due to error.
User Action:
If the condition persists contact your systems administrator.
Reason:
The heading in response to a SHOW UDB command. This information can be used to help determine the space requirements for the VFS dataset. It is extracted from the VSAM ACB; therefore, reflects VSAM calculations about the space remaining in the VFS dataset.
DDNAME The JCL DDname associated with this file.
FILEID For UDBs, this is the logical file ID assigned to the UDBCTL OPEN ID= operand. This FILE ID must be used when referring to this file with an NCL statement. For UDBs, a single dash ('-') in this field indicates that no file ID is assigned.
TYPE The type of VSAM datset: BASE (base cluster), AIX (Alternate Index), PATH (path), SYSO (sysout), ESDS or PDS.
A/U The number of active users that have a current logical connection to the file through VFS. This may include NCL procedures such as LOGPROC. It is not possible to logically stop access to a dataset (using the UDBCTL command) unless this number is 0.
SM Maximum strings used by VSAM to service this file. This can be used to tune the dataset.
DATA Percentage utilization of the data portion of the file.
EXT Number of extents used by the data portion of the file.
INDX Percentage utilization of the index portion of the file.
EXT Number of extents used by the index portion of the file.
RKP Relative key position of the dataset.
KYL The length of the key defined for the dataset.
UKY Indicates unique key requirement for alternate indices.
STUS Current file status. Can be SYS (SOLVE system dataset), AVAL (UDB available for use), STOP (UDB logically stopped by a UDBCTL command) or CLSD (UDB is physically closed because it failed to open or because a UDBCTL command closed it).
OPTNS The dataset may be opened with the following options:
R - Opened for reuse
I - Opened for input, updates not allowed
L - Local Shared Resource pool is used for buffers
S - Using Sequential Insert Strategy (SIS)
D - Using deferred writes
F - DBCS=FUJITSU is in effect for this file
N - EXIT=NO is in effect for this file
X - RLS is in effect for this file
System Action:
Multiple message lines (N13522) follow giving specific details.
User Action:
This information should be used only with the knowledge of the constraints of VSAM in calculating available space. The available space is based on control areas that are empty and have never been used. It is possible for a control area to have been used, the records deleted, and the control area to be empty again. VSAM does not classify this control area in its free space calculations; however, this information can be used to determine the largest amount of storage used at any time. When used in conjunction with the number of extents allocated, you should be able to predict when an increase in size is required. VSAM supports a maximum of 123 extents if the volume and/or available dataset permits.
Reason:
This message supplies the details for each VFS dataset or UDB as described by message N13521 or N15101.
System Action:
None.
User Action:
Refer to N13521 or N15101 for a description of the contents of the fields in this message.
Reason:
Part of the SHOW LINK display. This message is repeated for each active session maintained with the remote system.
Primary sessions are shown with x being a fullstop, and n being the relative session number, for example, SESS#....3.
Secondary sessions are shown with x being the letter S, and n being the relative session number. For example, SESS#...S2 (secondary sessions are displayed only if the SHOW LINK command has the DETAIL operand specified).
The status indicates the current session state. Values are:
The system is attempting to contact the remote system using this session.
The session between the two systems is open and traffic can flow across it.
The link between the two systems is being deactivated. The session is being terminated.
The link between the two systems has been broken by the use of a LINK STOP command. No session exists.
This session cannot start and the error is regarded as permanent. When the session was disabled, messages N35004 and N35005 were sent to MONITOR users and the log. See those messages for more information.
The mode indicates the session mode (displayed only if the DETAIL operand is specified). Values are:
Single-mode primary session.
Preferential-mode primary session.
Active/Backup mode normal active session.
Active/Backup mode backup session activated when normal active mode session fails or cannot be started.
Secondary session.
The AM=name shows the access method that the session is using (if the DETAILS operand is specified).
The KB=number shows the number of kilobytes of data that have been sent on this primary session.
System Action:
None.
User Action:
To monitor the status of your session links, enter /INMC at the prompt on any panel to display the INMC : Link Status List.
If a session is quiescing, the LINK cannot be restarted until the session terminates.
Reason:
This message is the last line of a SHOW LINKS display. It gives the total number of static links defined in the system (stot), the total number of dynamic links in the system (dtot) and the maximum possible dynamic links (dmax), set by sysparm DYNLMAX.
System Action:
None.
User Action:
None.
Reason:
This is the response to the SHOW COMP (compression) command if compression has been disabled.
System Action:
None.
User Action:
None.
Reason:
This is the heading message for a SHOW COMP command. One or more messages N13527 follow which contain values for each of the fields under this heading message, as described here. The SOURCE field specifies the source of the datastreams being compressed - either as MAI or PANEL (internally from SOLVE panels). Two OUTPUT values are shown, the BYTES sent, and SENDS - the number of sends. The COMPRESSED -BYTES field contains the number of bytes compressed. The SUCC% field indicates, as a percentage, how often compression was successful in reducing the output datastream size. The CMPR% indicates, as a percentage, the compression ratio when compression was successful, while TOTL% indicates, as a percentage, the total compression ratio.
System Action:
None.
User Action:
None.
Reason:
Detail line of a SHOW COMP display, as described in message N13526.
System Action:
None.
User Action:
None.
Reason:
This message is part of a SHOW USERS display. For users who are logged on more than once, this message displays details of their second and subsequent logons. The userid is given in the preceding line (message N13510). See N13510 for a description of individual fields.
System Action:
None.
User Action:
None.
Reason:
A detail line of a SHOW NCLSTAT display. The line shows several useful statistics totals. The NUM-PRELOAD count is the current number of NCL procedures preloaded. The NUM-AUTOSHR count is the current number of NCL procedures autoshared. The NUM- RETAIN count is the current number of NCL procedures retained.
System Action:
None.
User Action:
None.
Reason:
A detail line of a SHOW NCLSTAT display. The line shows several useful statistics totals. The NUM-PVT count is the current number of NCL procedures privately loaded. The NUM- NCLTEST count is the current number of NCL procedures loaded because of NCLTEST. The NUM-TOTAL count is the total number of NCL procedures loaded.
System Action:
None.
User Action:
None.
Reason:
A detail line of a SHOW NCLSTAT display. The line shows several useful statistics totals. The K-PRELOAD count is the current total Kbytes of NCL procedures preloaded. The K- AUTOSHR count is the current total Kbytes of NCL procedures autoshared. The K- RETAIN count is the current total Kbytes of NCL procedures retained.
System Action:
None.
User Action:
None.
Reason:
A detail line of a SHOW NCLSTAT display. The line shows several useful statistics totals. The K-PVT count is the current Kbytes of NCL procedures privately loaded. The K- NCLTEST count is the current Kbytes of NCL procedures loaded because of NCLTEST. The K-TOTAL count is the total Kbytes of NCL procedures loaded.
System Action:
None.
User Action:
None.
Reason:
A detail line of a SHOW NCLSTAT display. The line shows the current
System Action:
User Action:
Reason:
A detail line of a SHOW NCLSTAT display. The line shows several useful statistics totals. The TOT-EXECREQ count is the total number of NCL execution requests. The EXEC- PRLD count is the total number of NCL procedures that were executed from a preloaded copy of the procedure. The EXEC-AS/RT count is the total number of NCL procedures that were executed from an autoshared or retained copy of the procedure.
System Action:
None.
User Action:
None.
Reason:
A detail line of a SHOW NCLSTAT display. The line shows several useful statistics totals. The PHYS-LOADED count is the number of times that an NCL procedure was physically loaded from DASD. The PEND-UNLD count is the number of currently pending unload procedures that are still in use.
System Action:
None.
User Action:
None.
Reason:
A detail line of a SHOW NCLSTAT display. The line shows several useful statistics totals. The ASHR->RETN count is the number of times an NCL procedure migrated from autoshare status to retained status when its use count dropped to 0. The RETN->ASHR count is the number of times an NCL procedure migrated back to autoshare status when a new use commenced The RETN->DROP count is the number of NCL procedures purged from the retain list due to it being at the retain limit.
System Action:
None.
User Action:
None.
Reason:
This message forms part of the SHOW USERS display when IPDETAILS=YES is specified. This header line identifies the column that contains the IP address details for TN3270 connections.
For more information, see message N13539.
System Action:
None
User Action:
None
Reason:
The message is part of the SHOW USERS display when IPDETAILS=YES is specified. It displays the IP address for a TN3270 connection.
P1 is the address type (LOCAL or REMOTE).
P2 is the IP address.
System Action:
None.
User Action:
None.
Reason:
This is the second title line of a SHOW VSAMX display.
D-EXT is the heading for the number of extents allocated to the data component.
I-EXT is the heading for the number of extents allocated to the index component.
D-EXCP is the heading for the number of EXCP macros that VSAM has issued for access to the data component since the region started.
I-EXCP is the heading for the number of EXCP macros that VSAM has issued for access to the index component since the region started.
System Action:
None.
User Action:
None.
Reason:
This message supplies the details for each VFS dataset. Refer to N13551 for a description of the contents of the fields in this message.
System Action:
None.
User Action:
None.
Reason:
The operand xxxx specified in a LINK command is invalid or is syntactically incorrect.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Options for the link bbbbbbbbbbbb started with the LINK START command were obtained from the link definition aaaa.
System Action:
LINK START processing continues.
User Action:
None.
Reason:
A LINK START command was entered for a linkname which matched a link previously defined using a DEFLINK command and the APPLID for the LINK START was different to that of the DEFLINK definition.
System Action:
The command is rejected.
User Action:
Correct either the linkname or APPLID on the LINK START command, or review the DEFLINK definition.
Reason:
The RT operand specified on the LINK START command was invalid. The value specified must be in the range 60 to 28800 seconds.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
A LINK START=linkname command was entered including one or more definition operands, but the specified link has already been defined. The link will be placed in PEND-ACT status.
System Action:
None.
User Action:
The command will be accepted and this message is issued as a warning only.
Reason:
A LINK START=linkname command was entered, but the link to luname is already ACTIVE or in PEND-ACT status.
System Action:
The command is ignored.
User Action:
None.
Reason:
This message confirms that a LINK START= linkname command has been accepted and that the link between the two SOLVE systems will be activated.
System Action:
None.
User Action:
None.
Reason:
A request to activate an INMC link was made but the link is either already active or in the process of activating.
System Action:
The request is ignored.
User Action:
None.
Reason:
A LINK STOP= command was entered specifying linkname linkname, but the link is not currently active.
System Action:
The command is rejected.
User Action:
Check link name and retry if necessary.
Reason:
Confirms that a LINK STOP= command has been accepted. Sessions on the link linkname will be closed and the link disabled until a subsequent LINK START= command is entered to re-activate it.
System Action:
De-activation of the link is commenced.
User Action:
None.
Reason:
A LINK STOP= or LINK RESET= command was entered for link linkname, but no definition exists for that linkname.
System Action:
The command is rejected.
User Action:
Correct the linkname and retry.
Reason:
A LINK START command was entered for link linkname but the LINK is already the subject of another, currently processing, LINK START request.
System Action:
The command is rejected.
User Action:
Wait for the LINK to become active before issueing any other commands for it.
Reason:
Confirms that a LINK RESET= command has been accepted for the specified link, and that reset processing will start.
System Action:
Reset processing starts.
User Action:
None.
Reason:
The link name specified in a LINK command is the same as the name used to identify this SOLVE system, as defined by the SYSPARMS command ID= operand. The same name cannot be used to identify another SOLVE system.
System Action:
The command is rejected.
User Action:
Correct the link name and retry.
Reason:
This message confirms successful completion of a LINK STOP= linkname command where linkname is the link name of a remote SOLVE system and systemid is the local ID of this system.
System Action:
None.
User Action:
None.
Reason:
A LINK RESET command has been issued for link linkname, but one or more of the VTAM sessions associated with the link is still in the process of stopping. The link cannot be reset until all sessions have stopped. This situation usually occurs during a period of VTAM degradation.
System Action:
The link is not reset.
User Action:
Wait a minute or two and reissue the command.
Reason:
Confirms that a LINK START=linkname command has been accepted.
System Action:
None.
User Action:
None.
Reason:
There was insufficient storage to process a LINK START= command.
System Action:
Command processing terminates.
User Action:
Investigate the storage problem.
Reason:
This message confirms that a LINK STOP= aaaa TYPE=APPC command with option cccc has been entered and accepted.
System Action:
Link de-activation starts using option cccc. For the meaning of the different de-activation options see the Command Reference.
User Action:
None.
Reason:
This message confirms that a LINK STOP=aaaa TYPE=APPC FORCE command has been entered and accepted.
System Action:
Link de-activation will commence immediately. All active or pending conversations will be terminated.
User Action:
None.
Reason:
A LINK STOP=aaaa TYPE=APPC command was entered when link de-activation was already in progress.
System Action:
The system will proceed with link de-activation using the strongest de-activation option cccc specified so far. QUIESCE takes precedence over DRAIN while FORCE takes precedence over both DRAIN and QUIESCE.
User Action:
None.
Reason:
You entered a LINK STOP=aaaa TYPE=APPC with the FORCE operand. The link has not completed initialization but the force deactivation is scheduled.
System Action:
None.
User Action:
None.
Reason:
APPC tracing has been started or stopped, as indicated by "aaaaaaaa", for LINK "bbbbbbbbbbbb" to LU "cccccccc".
System Action:
As indicated by message.
User Action:
None.
Reason:
An attempt was made to stop an APPC link but no link by that name was active.
System Action:
The command is ignored.
User Action:
None.
Reason:
An attempt was made to RESET an APPC link but the link has not yet been stopped.
System Action:
The command is ignored.
User Action:
Issue STOP command to stop APPC link communication.
Reason:
An attempt was made to RESET an APPC link. The link is in the process of stopping and will be reset when all activity has ceased.
System Action:
Link reset is scheduled.
User Action:
None.
Reason:
An APPC link has been reset after all processing associated with the link has terminated.
System Action:
Link knowledge is removed from memory.
User Action:
None.
Reason:
A LINK START command was entered with an AM operand that specified an access method that is not available in this SOLVE system
System Action:
The command is rejected.
User Action:
Correct the AM operand.
Reason:
A LINK START command was entered with an AM operand that specified an access method that is invalid or unrecognized.
System Action:
The command is rejected.
User Action:
Correct the AM operand.
Reason:
A LINK START command was entered with an AM operand that specified an access method that does not support the LINK command.
System Action:
The command is rejected.
User Action:
Correct the AM operand.
Reason:
A LINK START command was entered with an AM operand that specified an access method that does not support this type of LINK (APPC or INMC).
System Action:
The command is rejected.
User Action:
Correct the AM operand.
Reason:
A LINK START command was entered with an AM operand which was specified as "NO" in the DOMAIN definition.
System Action:
The command is rejected.
User Action:
Correct the AM operand, or reissue the DOMAIN DEFINE command for the link.
Reason:
The only operand allowed in the SIGNON/SIGNOFF command is the linkname of the remote SOLVE system.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The specified link name of a remote SOLVE system exceeded the maximum supported for the operand. A linkname is 1 to 12 characters and a domain specification is 1 to 4 characters.
System Action:
The command is rejected.
User Action:
Correct the command operands and retry.
Reason:
The linkname of a remote SOLVE system was omitted from a SIGNON/SIGNOFF command, but is required.
System Action:
The command is rejected.
User Action:
Retry the command with the correct linkname.
Reason:
An invalid destination name was specified in a SIGNON/SIGNOFF command.
System Action:
The command is rejected.
User Action:
Retry the command with the correct linkname.
Reason:
Confirms that a SIGNON command without operands has been completed successfully and that the user region authorization has been re-initialized.
System Action:
None.
User Action:
None.
Reason:
The destination name specified on a SIGNON/SIGNOFF command is not defined to the system as the linkname of a remote SOLVE system.
System Action:
The command is rejected.
User Action:
Retry the command with the correct linkname. If the linkname is correct, a LINK START=linkname command may be required to define the linkname.
Reason:
A SIGNON command has been entered but a previous SIGNON command is already queued for the same linkname for the same user.
System Action:
The command is rejected.
User Action:
The existing queued SIGNON will complete when the link to the remote SOLVE system becomes active.
Reason:
A valid SIGNON command has been entered but the link to the destination SOLVE system is not yet active. The request is queued and will complete when the link is established.
System Action:
The command is suspended.
User Action:
If the queued SIGNON is no longer required a SIGNOFF command can be used to cancel it.
Reason:
Confirms successful completion of a SIGNOFF command.
System Action:
None.
User Action:
None.
Reason:
A SIGNOFF command was entered specifying the linkname of a SOLVE system to which the user is not signed on from the window from which the command was entered.
System Action:
The command is rejected.
User Action:
None.
Reason:
A SIGNON command issued earlier, but which has not completed because the link to the remote SOLVE system has not become active, has been cancelled by entry of a SIGNOFF command.
System Action:
None.
User Action:
None.
Reason:
A SIGNON/SIGNOFF command was issued but the destination name specified was the system identifier of the local system.
System Action:
The command is rejected.
User Action:
Retry the command with a remote linkname.
Reason:
An attempt was made to issue the SIGNON or SIGNOFF command from an environment that does not support this command.
System Action:
The command is rejected.
User Action:
Retry from another environment.
Reason:
A SIGNON command has been issued to refresh a current user or background environment. The refresh failed because an error occurred obtaining the security information. If you are using a full security exit, your exit may have issued an error return code for the `return userid information' request. Otherwise, there may be a problem with your UAMS dataset.
System Action:
The environment continues as before. It is not refreshed.
User Action:
For a user environment, refresh can be achieved by LOGOFF/LOGON.
Reason:
An invalid value was specified on the REGION= operand on a SIGNON command. Valid values are OWN, ALL or APPC. The default value is REGION=ALL.
System Action:
The command terminates.
User Action:
Correct operand value and retry the command.
Reason:
An attempt to refresh a user definition using the SIGNON command failed because the users owning environment was not found. Possible causes are because the user was in the middle of logging off, or the user region was terminating for some other reason.
System Action:
The refresh is not performed.
User Action:
Determine the state of the region, if the region still requires a SIGNON, then retry the operation.
Reason:
A SIGNON command using the REGION= operand, had additional operands specified. The REGION= operand is mutually exclusive with all other SIGNON command operands.
System Action:
the command terminates.
User Action:
Correct the problem and retry the operation.
Reason:
A SIGNON command was entered but was rejected because one or more operands specified required a higher Command Authority level than that of the user who issued the command.
System Action:
The command is rejected.
User Action:
Retry without the operand(s).
Reason:
This is the response to a SHOW NPF command if no Network Partitioning for either commands or messages has been defined for this userid. The definition of Network Partitions is a function of UAMS maintenance.
System Action:
None.
User Action:
None.
Reason:
The title line of the SHOW NPF display.
System Action:
None.
User Action:
None.
Reason:
The display heading line for the SHOW NPF display.
System Action:
None.
User Action:
None.
Reason:
Issued in response to the SHOW NPF command. A display line in this format is provided for each NPF table for which this userid has been defined.
resource This is the resource group name associated with this NPF table. The resource group name is the first operand on each NPF resource list control member entry.
table Table names refer to resource members in the NPTABLES dataset. Table names are specified as part of a RESOURCE LIST control entry with the resource- member=qualifier.tablename operand. It is also the name by which the table can be referenced with the SHOW NPTAB=tablename command and the NPTAB command.
network This is the qualifer which applies to the NPF resources in the NPF table. For network resources the qualifier defaults to the network ID in which the domain is executing. Resource qualifiers may be specified as part of a RESOURCE LIST control entry.
curstat This is the current status of the table for this user ID. This status can be ACTIVE if the table is currently available for use, or INACTIVE if the table is not available, either due to an NPTAB INACT=tablename command being entered by the user, or the table being specified in the NPF RESOURCE LIST control entry as having an initial status of INACTIVE (eg: NPTAB=tablname,I). A status of DELETED means the table was built, but has since been deleted by a NPTAB DEL=tablename command. Once a table has been deleted it is no longer available to any user that currently references that table. If the deleted table is later re-added by an NPTAB ADD= command, users that referenced the table when it was deleted and hence show a status of DELETED must logoff/logon to re- instate the deleted table entry so that table becomes available. A status of UNAVAIL means that this table is not available to this user because of an error when the NPF control member entry was validated or an error in building the table. A corresponding message will have been written to the log in this case.
initstat This is the initial status of the table when the NPF control entry was processed. initstat may indicate an error condition that was detected when the NPF control entry was processed.
System Action:
None.
User Action:
None.
Reason:
Designates the end of the SHOW NPF display.
System Action:
None.
User Action:
None.
Reason:
This message is issued at the end of a SHOW NPF display if one or more of the tables valid for the user contain errors.
System Action:
None.
User Action:
Use the SHOW NPTAB= command to determine the precise reason for the error(s) that exist.
Reason:
An unidentified operand was specified on a SHOW command.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
A SHOW NPTAB command was issued but no NPF tables have been built. NPF tables are either built automatically when a user requiring a particular table logs on, or can be added by the NPTAB ADD= command.
System Action:
None.
User Action:
None.
Reason:
The system function that performs Network Partition analysis and routing for unsolicited messages has been disabled because of an earlier error condition. The specific error was recorded on the system activity log under message number N18002. This message indicates that the delivery of unsolicited messages will be as though the users logged on had been defined without any NPF message restricions. NPF command restriction is still available.
System Action:
None.
User Action:
Analyze the associated log message and take corrective action. Report this problem to your product support representative if the problem cannot be rectified.
Reason:
The heading line of the SHOW NPTABS display.
System Action:
None.
User Action:
None.
Reason:
Information line for the SHOW NPTABS display. This message is issued for each attempt to build an NPF table either by a user requiring the table to logon, or by the entry of an NPTAB ADD= command.
All NPF tables in the system are displayed, not just those in use by this user. Use the SHOW NP command to determine the tables applicable to this user. `tablename` is the name of the table, and`errstat`(if present) is the error that occurred when the table was built.
System Action:
None.
User Action:
More information for certain error conditions can be obtained with the SHOW NPTAB=tablname command.
Reason:
A SHOW NPTAB= command requested a display of an NPF table that has either not been built or has been deleted by an NPTAB DEL= command. It is no longer available.
System Action:
The command is rejected.
User Action:
None.
Reason:
A SHOW NPTAB= command requested a display of an NPF table that was not found in the NPF library when the build was attempted.
System Action:
The command is rejected.
User Action:
Correct the problem and create the member if necessary. Having created the member, the NPTAB ADD= command can be used to bring the table into effect. Users referencing that table will be immediately affected and need not logoff/logon.
Reason:
A SHOW NPTAB= command requested a display of an NPF table that exists on the NPF library but is empty. A member that only contains comment cards or blank cards is not classified as empty.
System Action:
The command is rejected as there is nothing to display.
User Action:
None.
Reason:
A SHOW NPTAB= command requested a display of an NPF table, but an I/O error occurred when the table build was attempted.
System Action:
The command is rejected as the table cannot be displayed.
User Action:
Verify that the NPF dataset is not corrupted.
Reason:
The heading line of a SHOW NPTAB= display. Following this message is a description of the Network Partitioning tables active in the system.
System Action:
None.
User Action:
None.
Reason:
Response to a SHOW NPTAB= command. This is an expansion of the NPF table entries for the requested table. Each display line can contain several entries.
The leading A: or R: on the message indicates if the entries on this line are ACCEPT (A:) or REJECT (R:) entries.
ACCEPT entries that match a resource allow access to the resource. REJECT entries that match a resource prohibit access to the resource. (Note that not finding a match in the table results in a REJECT.)
Each entry is displayed in the wildcard format. A question mark in the value indicates a single-character wildcard (that matches any nonblank character). An asterisk in the value indicates a multi-character wildcard (that matches zero or more characters in the value). Other characters match themselves.
For example:
NY* matches resources that start with NY NY?1 matches resources that start with NY, are 4 characters long, and end in 1
*X matches resources that end in X
NOTE: Tables that were coded using the BASIC format used asterisks for both single and end-generic wildcards. These are translated to the new format with question marks and are displayed in the new format. For example, an old-format entry of 'NY*5*' would display as 'NY?4*'.
When a table contains syntax errors, message N13818 is displayed at the point at which the error is detected. Entries for subsequent records following a record containing an error are displayed after the N13818 message that describes the error.
System Action:
None.
User Action:
The SHOW NPTAB= command can be used to determine the particular resources which a user is entitled to reference in VTAM commands if NPF command restriction has been imposed, and/or the VTAM resources for which the user will receive unsolicited network messages if NPF message restriction has been imposed.
Reason:
This message is displayed as part of SHOW NPTAB= command when a syntax error is detected. This message may be preceded and followed by message N13817 which displays those entries which are not in error. When an NPF table is built, the processing for a record stops at the first entry in that record that is in error, and resumes on the following record. This message supplies the record sequence number from columns 73- 80 of the record in error and the first 8 bytes of the data where the syntax error was detected.
System Action:
The command is rejected.
User Action:
Correct the record in error, and use the NPTAB REP= command to immediately bring the changes into effect.
Reason:
The user's NPF RESOURCE LIST control member contained syntax errors or were empty and the result was that no NPF resource tables are available and no access to any network resource will be allowed.
System Action:
None.
User Action:
Correct the control member(s) and logon again.
Reason:
Provides an underline for the SHOW NPF display.
System Action:
None.
User Action:
None.
Reason:
Provides an underline for the SHOW NPTABS display.
System Action:
None.
User Action:
None.
Reason:
A SHOW NPTAB=tablname command was issued but the specified NPF table did not contain any valid resource entries or only contained comment cards.
System Action:
None.
User Action:
None.
Reason:
A warning issued after a SHOW NPF display that the specified control member aaaaaaaa contains errors of some sort.
System Action:
None.
User Action:
Correct the control member and logon again. It is most likely that the format of the control statements is incorrect.
Reason:
No resource table names match the name operand specified on the SHOW NPF=resource-name command.
System Action:
None.
User Action:
Check the command resource name operand.
Reason:
Part of the output of a SHOW NPTAB= display. The message indicates if the original table source was in the old format (BASIC), or the new format (ADVANCED).
System Action:
None.
User Action:
None.
Reason:
A SHOW EXEC command failed because the NCL procedure library for DD statement xxxxxxxx could not be opened.
System Action:
The command is rejected.
User Action:
Determine why the dataset failed to open. A corresponding system message will have been written to the system console and log.
Reason:
An I/O error occurred during the processing of a SHOW EXEC command. The NCL library involved is associated with DD statement xxxxxxxx . This could occur when a dataset in the concatenation has a larger blocksize than the first dataset in the concatenation for that DD statement.
System Action:
If SHOW EXEC,LIST=FULL or LIST=ALL was specified, the next dataset in the concatenation is listed, otherwise the command is terminated.
User Action:
Report the occurrence to your systems administrator.
Reason:
The information line of the SHOW EXEC command. This line contains the list of member names as requested.
System Action:
None.
User Action:
None.
Reason:
Signifies the end of the SHOW EXEC display and includes the number of members listed in the display.
System Action:
None.
User Action:
None.
Reason:
The SHOW EXEC command requested a range of members to be displayed, but the range given was invalid. The range must be in the format SHOW EXEC,start,end, where start and end must be a string from 1 to 8 characters long and where the end argument must be higher in collating sequence than the start argument.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The SHOW EXEC command can specify the ID of a library whose members are to be displayed. The ID operand specifies the DDNAME of the dataset. If specified, this operand must follow any member name range specification. The syntax of the command is incorrect.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
An information line of the SHOW EXEC command with LIST=ALL specified. A ddname may consist of several libraries concatenated together, each concatenated library is numbered from 0 upwards. Member names matching the requested specification within this dataset are listed following this message.
System Action:
None.
User Action:
None.
Reason:
The LIST= operand of the SHOW EXEC command allows you to display the member names in the FIRST library in the DD statement concatenation, the member names in ALL libraries or a FULL list, including member statistics for all libraries in the concatenation. If you specify LIST=, it must be LIST=FIRST, ALL or FULL.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
An information line of the SHOW EXEC command with LIST=FULL specified. name is the member name.
conc# is the concatenation number of the dataset within the ddname. The rest of the line contains ISPF/PDF statistics for the member (if present).
vv the version of the member.
mm the modification level of the member.
created the date (YY/MM/DD) the member was created.
changed the date (YY/MM/DD) and time (hh.mm) the member was last updated.
size the number of records in the member.
init the initial number of records in the member.
mod the number of records modified in the member.
id the userid or jobname which last updated the member.
System Action:
None.
User Action:
None.
Reason:
A heading line of the SHOW EXEC command with LIST=FULL specified. For more details refer to the description of the N13909 message.
System Action:
None.
User Action:
None.
Reason:
The SHOW EXEC command contained invalid syntax.
System Action:
Command is rejected.
User Action:
Correct and retry.
Reason:
A DEFLINK command was entered to add a dynamic link definition, but a definition already exists for the operands specified.
System Action:
The command is rejected.
User Action:
To change a dynamic link definition, use the REPLINK command. Use a `SHOW DEFLINK' command to display current dynamic link definitions.
Reason:
Confirms the successful completion of a DEFLINK or REPLINK command to add or change a dynamic link definition.
System Action:
None.
User Action:
None.
Reason:
Confirms the successful completion of a DELLINK command to remove a dynamic link definition.
System Action:
None.
User Action:
None.
Reason:
An attempt to delete a dynamic link definition using a DELLINK command has failed because the indicated definition does not exist.
System Action:
The command is rejected.
User Action:
Change the operands and reissue the command. If necessary, use a `SHOW DEFLINK' command to list the current dynamic link definitions.
Reason:
An attempt to add a dynamic link definition using a DEFLINK command has failed because the retry interval specified on the RT operand was too high or too low. Retry interval must be between 60 seconds and 8 hours.
System Action:
The command is rejected.
User Action:
Change the RT operand to a number between 60 and 28800 and reissue the command.
Reason:
A DEFLINK command was entered to add a dynamic link definition, but the dynamic link was already defined.
System Action:
The command is rejected.
User Action:
Change and retry.
Reason:
A DEFLINK command was entered to add a dynamic INMC link definition but it included operands which are only valid for DEFLINK TYPE=APPC.
System Action:
The command is rejected.
User Action:
Change the command to remove the APPC operands (or add TYPE=APPC).
Reason:
A DEFLINK command was entered to add a dynamic APPC link definition but it included operands which are only valid for DEFLINK TYPE=INMC.
System Action:
The command is rejected.
User Action:
Change the command to remove the INMC operands.
Reason:
A DEFLINK or REPLINK command was entered with the AM=name operand. The name supplied is not a recognized access method name
System Action:
The command is rejected.
User Action:
Correct the AM operand value.
Reason:
A DEFLINK or REPLINK command was entered with the AM=name operand. The name supplied is a recognized access method, however it is not active in this SOLVE system
System Action:
The command is rejected.
User Action:
Correct the AM operand value.
Reason:
A DEFLINK or REPLINK command was entered with the AM=name operand. The name supplied is a recognized active access method, however it does not support the requested link type (APPC or INMC).
System Action:
The command is rejected.
User Action:
Correct the AM operand value.
Reason:
This message is the result of a SHOW NCL command. It indicates that an NCL environment exists for which no NCL procedure was active at the time the command was issued, however the environment remains active because it is a registered object server.
System Action:
Information only.
User Action:
N/A
Reason:
A SHOW NCLVARS command has been entered to display variables from an active process. The target process has one or more OML procedures active, and OML does not support the SHOW NCLVARS command. Use the NCL DEBUG facility to display variable contents.
System Action:
None.
User Action:
None.
Reason:
This message is a heading line issued by a SHOW NCLVARS command. nnnnnn is the NCLID of the target process for which information is being displayed. bbbb is the nesting level of the current procedure aaaaaaaa.
System Action:
None.
User Action:
None.
Reason:
This is a detail line of the SHOW NCLVARS command summarizing the variable use of an NCL procedure.
aaaaaaaa is the ncl procedure name
bbb is the method level of the procedure
ccc is the nesting level of the procedure
The following fields are provided if LIST=SUMMARY is specified.
dddddd is the count of the number of variables
eeeeeeee is the total number of characters for all variables
ffffff is the average variable size (d/c)
gggggggg is the maximum chain depth
System Action:
None.
User Action:
Use the information to review the storage efficiency of the NCL process displayed. Excessive variable use may cause performance degradation.
Reason:
This is a subheading issued by a SHOW NCLVARS command. It is followed by one or more N13C51 messages summarizing the variable use of an NCL process. The first sub- heading is issued if the LIST=SUMMARY operand is specified.
System Action:
None.
User Action:
None.
Reason:
This is the first title line of the display resulting from a SHOW SERVER command.
svrtype is the type of server registered. This will be AGENT, METHOD, PROCESS, or SYSTEM.
server-name-attr is the object services attribute name of the server name field. For NCL servers this will be ZZZSERVER.
server-name is the name of the object for which the server is registered.
This message will be followed by detail line (N13E02).
System Action:
None.
User Action:
None.
Reason:
This is a detail line of the display resulting from a SHOW SERVER command.
zzzclass is the class of object for the server registration. For NCL procedure servers the class will be ZZZPROCESS. For servers registered as object services methods the class will be the class of the registered object.
aaaaaaaa is the scope for the server is registered.
bbbb is the SOLVE system domain ID. target will be LINK or LU if this is an object services SYSTEM server or NCLID if it is a process, method, or agent server.
cccccccc is the linkname or luname for a system server or nclid of the method, agent, or function server.
System Action:
For servers with scope of USER down, message N13E03 will follow.
User Action:
None.
Reason:
This the second detail line of the display resulting from a SHOW SERVER command for servers with scope of region or user.
aaaaaaaa is the userid that started the NCL process.
bbbbbbbb is the region name (ie the logical unit name of the terminal at which the user is logged on).
System Action:
None.
User Action:
None.
Reason:
This message displays the contextid for a server with scope of CONTEXT from a SHOW SERVER command. aaaaaa is the server contextid.
System Action:
None.
User Action:
None.
Reason:
This the termination line of the display resulting from a SHOW SERVER command. Where nnnnnnn is the number of server entries displayed.
System Action:
None.
User Action:
None.
Reason:
A SHOW SERVER command has been entered but the SCOPE= operand specifies an invalid value.
System Action:
The command is rejected.
User Action:
Refer to the help for the SHOW SERVER command to obtain a valid value for the SCOPE operand, and retry the command.
Reason:
A DOMAIN command has been successfully executed. The domain name is P1 and the result P2 ( ADDED, REPLACED or DELETED) is shown.
System Action:
None.
User Action:
None.
Reason:
A DOMAIN DEFINE command has failed because the domain name ( P1 ) alread exists.
System Action:
The command is rejected.
User Action:
To replace an existing domain definition use the DOMAIN REPLACE command.
Reason:
A DOMAIN DELETE command has failed because the domain name specified ( P1 ) does not exist.
System Action:
The command is rejected.
User Action:
None.
Reason:
A DOMAIN command failed because of insufficient storage.
System Action:
The command is rejected.
User Action:
Determine why there is insufficient storage. You can use the OCS command, SHOW BUFF, to view the statistics on storage utilization.
Reason:
A DOMAIN DEFINE or DOMAIN REPLACE command specified an invalid IP address.
System Action:
The command is rejected.
User Action:
Issue the command with a valid IP address.
Reason:
A DOMAIN DEFINE or DOMAIN REPLACE command specified an invalid IP proxy address or port number.
System Action:
The command is rejected.
User Action:
Issue the command with a valid IP proxy address or host name, and port number.
Reason:
The operand xxxx included in an NPTAB command was not recognized.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
An NPTAB command requires the name of an NPF table. The name was either omitted or too long.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
An NPTAB command was entered but is invalid because no operands have been specified.
System Action:
The command is rejected.
User Action:
Correct and retry. For a description of the operands refer to the NPTAB command in the Command Reference.
Reason:
An NPTAB ADD= command specified the name of an NPF table that is already known to the system.
System Action:
The command is rejected.
User Action:
If a new version of the table is to be brought into effect, the REP= operand must be used.
Reason:
An NPTAB DEL= or REP= command specified the name of an NPF table that is not known to the system.
System Action:
The command is rejected.
User Action:
None.
Reason:
Confirms successful completion of an NPTAB DEL= command.
System Action:
Users that are logged on that currently reference this table will no longer have it available. If a new user logs on that requires this table it will again be automatically added. It is the user's responsibility, when a table is deleted, to ensure that the table has been disabled or corrected as necessary to cater for this possibility.
User Action:
A SHOW NPF command display that includes this table will show a status of 'DELETED'.
Reason:
An NPTAB DEL= command was entered specifying the name of an NPF table that is in the process of being built. This is invalid until the build process is complete.
System Action:
The command is rejected.
User Action:
Retry after the build has completed.
Reason:
An NPTAB resource ACT= command specified the name of an NPF resource table that the user is not entitled to use.
System Action:
The command is rejected.
User Action:
Use the SHOW NPF command to determine which tables are available to your userid.
Reason:
An NPTAB resource ACT= command specified the name of an NPF resource table that is already active.
System Action:
The command is rejected.
User Action:
None.
Reason:
Confirms successful activation of NPF resource table tablname after an NPTAB resource ACT= command.
System Action:
Resources specified in the table will now be available to the user. If the table was an NPF message table (resource $NMMSG) the user will now receive unsolicited network messages for the resources included in table `network.tablename'.
User Action:
The NPTAB resource INACT= command may be used to return the table to INACTIVE status.
Reason:
An NPTAB ACT= command was entered but the user does not have any NPF resource tables declared.
System Action:
The command is rejected.
User Action:
None.
Reason:
An NPTAB resource INACT= command specified the name of an NPF table that is already inactive.
System Action:
The command is rejected.
User Action:
The SHOW NPF command can be used to determine the current and initial status of tables.
Reason:
Confirms successful completion of an NPTAB resource INACT= command for NPF table `network.tablename' in resource group `resource'.
System Action:
None.
User Action:
The SHOW NPF command can be used to determine the current and initial status of tables.
Reason:
An NPTAB resource INACT= command was attempted for an NPF command partitioning table (resource group $NMCMD). Command partitioning table status may not be modified.
System Action:
The command is rejected.
User Action:
Do not attempt to issue the NPTAB (IN)ACT command for command partitioning resource tables.
Reason:
An NPTAB ADD= or REP= command was entered but the user does not have a high enough command authority level.
System Action:
The command is rejected.
User Action:
None.
Reason:
An NPTAB ACT= command specified the name of an NPF table that has been deleted by an NPTAB DEL=tablname command. It is not available to be reactivated.
System Action:
The command is rejected.
User Action:
Contact your systems administrator to determine why the table has been deleted.
Reason:
An NPTAB ACT=tablename or INACT=tablename command specified the name of NPF table that cannot be processed because there were syntax errors in the user's RESOURCE LIST control member for the `network.tablename' resource table.
System Action:
The command is rejected because the resource table is not available due to control member syntax errors.
User Action:
The message control member should be corrected, and may be refreshed by logging on again.
Reason:
A resource group name was specified on an NPTAB ADD, DEL, or REP command The ADD, DEL, REP commands apply only to library members and are only associated with resource groups via the RESOURCE LIST CONTROL MEMBER in a user's UAMS definition.
System Action:
The resource name operand is ignored and processing continues.
User Action:
It is not necessary to specify a resource name on NPTAB ADD, DEL, REP commands.
Reason:
An attempt to build an NPF table failed because the system could not open the NPF dataset.
System Action:
The command is terminated.
User Action:
Report the occurrence to your systems administrator.
Reason:
This message warns that one or more errors occurred during the building of NPF table tablname. This may result in a user's access being restricted to validly defined resources.
System Action:
None.
User Action:
Use the SHOW NPTAB=tablname command to display the errors that were detected within the specified NPF table.
Reason:
Confirms successful building of the new NPF table tablname.
System Action:
None.
User Action:
None.
Reason:
Confirms successful completion of an NPTAB REP=tablname command.
System Action:
The new table is made available immediately to all users without the need to logoff and logon.
User Action:
None.
Reason:
You do not have a high enough authority level for the SHOW STOR command. The authority level needed is 255.
System Action:
THe command is ignored.
User Action:
Increase your command authority to 255 and try again.
Reason:
A request to load or unload a procedure or module was successful. In the message:
P1 is the type (PROCEDURE, MODULE, or NVPANEL)
P2 is the name
P3 is the action taken (LOADED or UNLOADED)
System Action:
None.
User Action:
None.
Reason:
A request to load a module ( P1 ) failed. The R15 ( P2 ) and R1 ( P3 ) return codes from the LOAD macro are shown.
System Action:
The module specified is not loaded.
User Action:
Determine the cause of the error and retry.
Reason:
A request to delete load module ( P1 ) failed.
System Action:
The specified module is not deleted.
User Action:
Specify the correct module name and retry.
Reason:
A request to unload a procedure ( P1 ) failed because the NCL procedure was not preloaded.
System Action:
The command is rejected.
User Action:
None.
Reason:
A request to unload a procedure ( P1 ) was issued. There are P2 current users of the procedure.
System Action:
The procedure will be unloaded when the last active user terminates. New users of the procedure will execute a fresh copy of the procedure read from the procedure library.
User Action:
None.
Reason:
An UNLOAD PROCEDURE= command has been issued specifying a generic procedure or DD name. This message shows the total NCL procedures unloaded as a result of the command.
System Action:
The procedures are reloaded, as required.
User Action:
None.
Reason:
An UNLOAD MAP= command has been issued specifying a generic map name. This message shows the total maps unloaded as a result of the command.
System Action:
The maps are reloaded, as required.
User Action:
None.
Reason:
An UNLOAD NVPANEL= command has been issued specifying a generic panel name. This message shows the total panels unloaded as a result of the command.
System Action:
The panels are reloaded, as required.
User Action:
None.
Reason:
A request to unload a panel ( P1 ) failed because the panel is not loaded.
System Action:
The command is rejected.
User Action:
None.
Reason:
Storage could not be obtained to process the LOAD or UNLOAD command.
System Action:
The command is not processed.
User Action:
Determine the cause of the storage shortage.
Reason:
Extended Options option P1 was set successfully.
System Action:
None
User Action:
None
Reason:
The name of the Extended Option to set is missing.
System Action:
None
User Action:
Repeat the command specifying the name of the Extended Option.
Reason:
The name of the Extended Option specified is not recognized.
System Action:
None
User Action:
Repeat the command specifying the correct name of the Extended Option.
Reason:
The Extended Option specified cannot be set at the current stage of the Region processing.
System Action:
None
User Action:
Make sure that the option to be changed can be changed after the initialization phase.
Reason:
The Extended Option specified is disabled or not supported.
System Action:
None
User Action:
Check which Extended Option you want to change. Repeat the command with the correct option.
Reason:
A ##TOFF command was entered and processed successfully.
System Action:
As per the request.
User Action:
None.
Reason:
A ##TOFF command was entered. It was ignored because the region had the TZ JCL parameter specified.
System Action:
The request is ignored.
User Action:
If you want to use the ##TOFF testing facility, remove any TZ parameters from the JCL PARM.
Reason:
A ##TOFF command was entered. The time offset specified was not valid.
The time offset must be in the following format:
0 or s0 or shhmm or shh.mm
where:
s is + or E (meaning east of or ahead of GMT/UTC), or W (meaning west of or behind GMT/UTC)
hh is the offset in hours (1 or 2 digits, max 99)
mm is the offset in minutes (2 digits, 00 to 59)
System Action:
The command is ignored.
User Action:
Correct the offset.
Reason:
Activation of xxxPROC was requested but the procedure is already active.
System Action:
The request is rejected.
User Action:
If you wish to restart the procedure you must first use the SYSPARMS xxxPROC=FLUSH command to terminate the current active procedure and then start the new version.
Reason:
An attempt to FLUSH the specified procedure cannot be processed because the procedure is not active.
System Action:
The request is rejected.
User Action:
If the procedure is active it should be waiting on the completion of an
xxxREAD statement. Check the procedure logic to ensure that it does not get suspended without an xxxREAD statement being issued.
Reason:
An attempt to start tracing NCL global variables using SYSPARMS NCLGBTRC has failed because tracing is already active.
System Action:
The request is rejected.
User Action:
Tracing must be stopped using SYSPARMS NCLGBTRC= (that is, no operand) before tracing may be restarted.
Reason:
You issued a SYSPARMS EASINET=procname or EASINET=NO command after system initialization. Activation of the EASINET feature can be specified only during system initialization and it cannot be deactivated by EASINET=NO after initialization is complete. The SYSPARMS EASINET=procname command may only be used after initialization to specify the name of a new EASINET procedure for security reasons.
System Action:
The command is rejected.
User Action:
The SYSPARMS EASINET=NO command must be issued by the ACINIT parameter group during system initialization. Update the parameter group and save the changes, but do not action it. The changes will take effect the next time the region is started. If necessary, recycle the region.
Reason:
A SYSPARMS UNLOAD= command specified the name of an NCL procedure that had not been preloaded.
System Action:
The command is rejected.
User Action:
Use the SHOW NCLSTAT command to determine the names of preloaded procedures.
Reason:
A SYSPARMS UNLOAD= command was issued. There are nn current users of the preloaded NCL procedure.
System Action:
The procedure will be unloaded when the last active user terminates. New users of the procedure will execute a fresh copy of the procedure read from the procedure library. Alternatively a SYSPARMS PRELOAD= command may now be issued to preload an updated copy of the procedure.
User Action:
The SHOW NCLSTAT command can be used to determine the current status of procedures that are waiting to be unloaded.
Reason:
This is the title line of the SHOW VSAM (SHOW VSAMX) display.
DDNAME the JCL DDNAME, or DLBL name, associated with this file.
RECSZ the defined maximum record size for the dataset.
D-CISZ the VSAM Control Interval size for the Data component of a KSDS.
I-CISZ the VSAM Control Interval size for the Index component of a KSDS.
CI-SP the number of Control Interval splits that VSAM has performed for this dataset.
CA-SP the number of Control Area splits that VSAM has performed for this dataset.
D-BF the maximum number of data buffers allocated for processing a string of the VSAM dataset. This value shows the maximum amount of storage used at any time and may be used in tuning the BUFND VSAM operand specified in the JCL or on the UDBCTL command. (Note that for MVS the value shown may exceed the specified BUFND value due to dynamic string expansion).
I-BF the maximum number of index buffers allocated for processing a string of the VSAM dataset. This value represents the maximum amount of storage used at any time and may be used in tuning the BUFND VSAM operand specified in the JCL or on the UDBCTL command. (Note that for MVS the value shown may exceed the specified BUFND value due to dynamic string expansion).
STRSH the number of times a string shortage condition caused a temporary delay in processing a file. SOLVE will write a monitor message the first time this occurs only.
BFRSH the number of times a buffer shortage condition caused a temporary delay in processing a file. This should only occur for datasets running with LSR=YES (see below).
LSR NO, YES, RLS, or a number, indicating whether or not this VSAM dataset is using the Local Shared Resource pool. NO means that it is not, YES means that it is, using pool 0 if multiple pools are supported, and a number means that it is, using the indicated LSR pool. RLS means that VSAM RLS is in effect for this file.
CTL DSN or DD, indicating whether VSAM is sharing control block structures at a Dataset name level (DSN) or at a DDname level (DD). This applies to MVS only. When processing with Alternative Indices or Paths sharing should be at the DSN level, which is the default.
Notes: Where a number exceeds 99999 then truncation will occur to allow the value to fit within the field bounds. The number's magnitude is represented by the units K, M or G.
System Action:
None.
User Action:
None.
Reason:
The title line issued in response to the SHOW PANELS command.
PANEL-NAME the name of a panel located in the active panel queue.
STATUS may be 'LOADED' indicating that the panel is actually resident in the active panel queue, or 'LOADING', indicating that a load is in progress for the particular panel.
HITS the number of times a requested panel has been found in the active panel queue, thus avoiding I/O.
PATH is the library path that the panel is registered on.
LIBRARY is the library in the path that the panel was found in.
AGEUSE is an aged use count used to decide when to drop a panel from the list of active panels.
System Action:
None.
User Action:
None.
Reason:
Issued in response to the SHOW PANELS command, this is the information line as described on N15104.
System Action:
None.
User Action:
None.
Reason:
Indicates the end of the SHOW PANELS display and provides summary data about the active panel queue. The number of panels currently on the active panel queue is aaaa . The MAXPANEL value is bbbb . The total number of requests for panels processed by the system is cccccc. The total number of times a recccccc. panel was found on the active panel queue is ddddddd.
System Action:
User Action:
This information can be used to help analyze the optimal size of the active panel queue as set in the region.
A low number of hits indicates that the queue may be too small; therefore, excessive I/O must be performed to obtain panel images. Conversely, if the queue is too large, virtual storage is wasted and
Reason:
This is the title line issued in response to a SHOW UDBUSER command.
System Action:
None.
User Action:
Refer to N15108 for details of these fields.
Reason:
The information line issued in response to a SHOW UDBUSER command. This display is ordered by UDB. Each user of a UDB is displayed following the first reference to that particular UDB. Therefore users that have connections to multiple UDBs will appear multiple times, once for each UDB to which they are connected.
ddname the JCL DDNAME associated with this UDB. The ddname will appear only for the first user that is referencing that UDB. Subsequent display lines for that UDB will contain a `-' to assist in clarifying the display.
fileid the logical fileid assigned to the UDB using the UDBCTL command. This is the name used by NCL in an &FILEID statement to obtain access to the UDB. The fileid will appear only for the first user that is referencing that UDB. Subsequent display lines for that UDB will contain a `-' to assist in clarifying the display.
userid the user or system task currently processing the UDB. Where access to the UDB is being performed from the EASINET facility, a userid of `EASINET' will be displayed. System tasks utilizing UDB processing may also be displayed as `LOG-PROC', `BG- MON', `BG-SYS' or `BG-LOG'. If the UDB was opened as NDB, this field will be displayed as `*NDB*'.
nclproc identifies the NCL procedure which issued the &FILEID statement to obtain access to this UDB. Where nested procedures are utilized this may not be the current NCL procedure that is processing.
nclid the nclid of the NCL process.
luname the luname (terminal) the user is logged on from. System tasks utilizing UDB processing may also be displayed as `LOG-PROC', `BG-MON', `BG-SYS' or `BG-LOG'.
(status) if displayed, this field indicates that processing the NCL procedure has been temporarily suspended waiting for system resources. A value of `(STRSH)' indicates that the procedure is waiting for VSAM processing strings. A value of `(BFRSH)' indicates that the procedure is waiting for VSAM buffers.
System Action:
None.
User Action:
If the (status) field is displayed it may indicate that system performance is being impacted and that attention should be given to tuning VSAM usage within the system. For Local Shared Resource (LSR) pools the LSRPOOL command may need to be used to alter the LSR pool to include additional VSAM strings and buffers. If not, the system JCL or the UDBCTL command can be used to specify additional strings and buffers as necessary. The SHOW UDB and SHOW VSAM commands can be used to further monitor system performance and obtain additional information about VSAM usage. Refer to the the VSAM Programming Guide for additional information on buffer and string control.
Reason:
This is the heading line issued in response to a SHOW NCLGLBL (full) or SHOW NCLGLBL=varname (selective) command.
System Action:
Subsequent information lines follow.
User Action:
None.
Reason:
This is a title line issued in response to the SHOW NCLGLBL=varname command. Varname refers only to the variable name following the global variable prefix, and does not include the prefix itself. This command may be used to determine the current length and value of each global variable beginning with varname.
System Action:
Information lines follow for each variable requested.
User Action:
None.
Reason:
This is the information line following N15109 for a full list of NCLGLBL variable names.
System Action:
None.
User Action:
None.
Reason:
This is the information line issued in reponse to the SHOW NCLGLBL=varname command. The full name of the variable is variablename and currently has a length of leng, and the actual contents of this variable is given be text.
System Action:
None.
User Action:
None.
Reason:
This message indicates the end of the SHOW NCLGLBL command and summarizes the number of variables displayed and the depth of the maximum chain. The maximum chain depth is an indication of the processing required to access specific variables. A normal value would be 2 or 3. The creation of many global variables will cause long chains and increase access time.
System Action:
None.
User Action:
None.
Reason:
The title line of the SHOW ALLOC display. Displays the DDname, the STATUS of the allocation, the user requesting the allocation, the time at which the allocation was performed, if the dataset is concatenated the ddname referred to in the CONCAT operand and the first 28 characters of the dataset name.
The STATUS field can contain one of 3 possible values :
ALLOCATED - the dataset is allocated to the SOLVE system
PENDING - the dataset is in the process of being allocated
UNKNOWN - the status of the allocation is unknown
System Action:
None.
User Action:
None.
Reason:
The information line of the SHOW ALLOC display. Refer to message N15114 for details.
System Action:
None.
User Action:
None.
Reason:
Your authority level is insufficient for use of the NCLGLBL operand of the SHOW command.
System Action:
The command is rejected.
User Action:
None.
Reason:
(VM/SP systems only) The title line issued in response to a SHOW ALLOC command. Displays the DDname, the filemode, the user requesting the allocation, the time at which the allocation was performed, the catalog in which the dataset is defined (the CATDD column) and the first 27 characters of the dataset name.
System Action:
None.
User Action:
None.
Reason:
The information line issued in response to a SHOW ALLOC command. Refer to message N15117 for details.
System Action:
None.
User Action:
None.
Reason:
First message returned on SHOW USERACCT command.
System Action:
None.
User Action:
None.
Reason:
Second message returned on SHOW USERACCT command. status is status of user NCL cputime reporting: ACTIVE,INACTIVE or P-INACT. smfrid is the SMF record id. Start is the FROM time for the reporting interval. interval is the reporting interval (in hours). mincpu is the minimum amount of cputime to be reported (in seconds).
System Action:
None.
User Action:
None.
Reason:
An NCL based command (EXEC, START, LIST etc.) failed because insufficient storage was available.
System Action:
The command is rejected.
User Action:
Restructure the procedure or increase the SOLVE region or partition size.
Reason:
A START, EXEC, FSPROC, LIST or NCLCHECK command specified an invalid operand.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
An FSPROC command was issued from a procedure that is not directly associated with a display terminal, eg: LOGPROC.
System Action:
The command is rejected.
User Action:
Restructure the procedure.
Reason:
A LIST command has been issued to list a member of a procedure library. The ID parameter specified on the command is not a valid ddname (MVS), filetype (VM) or sublib (VSE).
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
A START, EXEC, FSPROC, LIST or NCLCHECK command was issued but no procedure name was supplied. The PROC operand is mandatory.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
A START, EXEC, FSPROC, LIST or NCLCHECK command was issued but the PROC operand value xxxx is not a valid NCL procedure name.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
A START command was issued but the SERVER operand value xxxx is not a valid NCL server name.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
A START command was issued but the SCOPE value xxxx is invalid.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
A LIST command was issued but the ID operand value xxxx is invalid.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
The NOTIFY operand of the START command must be YES or NO.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
An EXEC or FSPROC command has been entered to begin execution of an NCL procedure. The EXEC or FSPROC command is concatenated with another command, This is invalid.
System Action:
The request to begin a new NCL procedure is rejected.
User Action:
The EXEC or FSPROC command must be entered as a single (ie. not concatenated) command. Correct the command and retry.
Reason:
The specified operand of an NSBRO command was invalid.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
A required operand for the entered NSBRO command has been omitted.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
Confirms deletion of the specified line of the broadcast text as a result of an NSBRO command.
System Action:
None.
User Action:
None.
Reason:
Confirms successful execution of an NSBRO command to set a broadcast line.
System Action:
None.
User Action:
None.
Reason:
An NSBRO command could not be serviced because of a storage shortage.
System Action:
The command is rejected.
User Action:
If necessary increase the SOLVE region or partition size.
Reason:
The text length that can be specified with NSBRO is a maximum of 78 characters.
System Action:
The command is accepted but excess text is discarded.
User Action:
Re-format the broadcast if required.
Reason:
The mask that defines the target terminals for a broadcast type xxxx is invalid or has been omitted.
System Action:
The command is rejected.
User Action:
Correct the mask and retry.
Reason:
An NSBRO command was issued to send a specific broadcast but no text had been defined by an earlier NSBRO command.
System Action:
The command is rejected.
User Action:
Define the specific broadcast text and retry. After each use of the SSEND= operand, the specific broadcast text must be set again using the SBn operands.
Reason:
An NSBRO broadcast has been accepted for processing. The ID assigned to the broadcast is aaaaaaaa. An N15501 message is issued when the broadcast has completed processing.
System Action:
The broadcast request is queued to process.
User Action:
Review the N15501 message to determine the results of the broadcast.
Reason:
AN NSBRO command contains conflicting operands.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The indicated operand of an NSBRO command was invalidly specified.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Confirms successful execution of an NSBRO command or broadcast services request. xxxxxxxx indicates the broadcast identifier associated with the request. yy indicates the number of terminals that received the broadcast. zz indicates the number of SOLVE users that received the broadcast.
System Action:
None.
User Action:
None.
Reason:
The specified broadcast request has been cancelled by the named user. The broadcast may be either an active broadcast or one queued. If the broadcast was active then the N15501 message indicates the number of receivers.
System Action:
The broadcast request is discontinued if active and the broadcast is discarded.
User Action:
None.
Reason:
The specified broadcast request has not completed due to the user logging off.
System Action:
The log procedure detects this message and decrements the number of outstanding broadcasts.
User Action:
None.
Reason:
A UDBCTL command has been entered either with no operands or with an invalid operand.
System Action:
The command is rejected.
User Action:
Refer to the command description in the Command Reference.
Reason:
A UDBCTL command has been entered with invalid syntax.
System Action:
The command is rejected.
User Action:
Correct the command and retry. This error normally indicates that the DDNAME specified in the command has invalid syntax or a logical fileid that is being assigned is invalid.
Reason:
A UDBCTL command has been completed successfully. xxxxxx is the type of request and will be OPEN, CLOSE, RESET or ASSIGN.
System Action:
None.
User Action:
If it was an OPEN request a logical file ID will still have to be assigned before the UDB is available for processing, unless the ID= operand was also specified.
Reason:
An attempt to assign a logical fileid to a UDB has failed because the specified name does not conform to system requirements.
System Action:
The command is rejected.
User Action:
Ensure that the specified name is from 1 to 8 characters in length, starts with an alphabetic or national character and contains only alphanumeric or national characters. Correct and retry.
Reason:
An OPEN or RESET request has been rejected because the nominated UDB is not CLOSED.
System Action:
The command is rejected.
User Action:
An attempt to OPEN an already open UDB is meaningless. Before a RESET request can be processed the UDB must be closed. This can be achieved by using the CLOSE operand. If necessary close the UDB and retry.
Reason:
An attempt to RESET the UDB associated with DD ddname has failed because of the error X`yy'.
System Action:
The UDB has not been reset and remains in closed status.
User Action:
The VSAM ACB open code X`yy' is described in the VSAM Programmer's Guide. VSAM imposes certain restrictions and requirements on datasets before they can be reset. The dataset cannot be allocated with the UNIQUE attribute, cannot use KEYRANGES or use ALTERNATE INDICES. In addition the dataset must have been defined with the REUSE attribute. The SHOW UDB command can be used at any time to redisplay the error code for the error that caused the failure. Determine the cause of the error and if possible retry it. Even though the RESET process failed, it may still be possible to re-open the UDB (with the OPEN operand) and resume processing until the error can be corrected.
Reason:
A UDBCTL command has been entered that references a DDNAME that was not included in the system JCL or has not been allocated by use of the ALLOC command.
System Action:
The command is rejected.
User Action:
This may result from a syntax error. If so correct the command and retry. If the DDNAME has been omitted, use the ALLOC command to allocate this UDB.
Reason:
A UDBCTL command has been entered to assign a logical fileid to the DDNAME dddddddd. However, the FILEID fileid has previously been assigned. Only one fileid per UDB can be used.
System Action:
The assignment is rejected and the original fileid remains operative.
User Action:
If a new fileid is required the UDB must first be logically stopped using the STOP operand. The assignment of the new fileid can then be performed.
Reason:
An attempt to change the status of a UDB by assigning a logical fileid, logically stopping or physically closing has been rejected because the UDB is in error status. This error will either have occurred during system startup or as the result of a subsequent OPEN or RESET attempt.
System Action:
The request is rejected.
User Action:
Use the SHOW UDB command to determine the nature of the open error. This will be displayed as a VSAM ACB open error code which can be interpreted using the VSAM Programmer's Guide. The UDBCTL command OPEN operand can be used to retry the open. Only when this condition has been corrected, can the status be further changed.
Reason:
An attempt to STOP or CLOSE a UDB using the UDBCTL command has been rejected because the UDB still has active users.
System Action:
The command is rejected.
User Action:
Before a UDB can be logically stopped or physically closed it must have no active users. Stopping or closing a UDB while it is being actively processed could impact processing and result in errors. The SHOW UDB command can be used to obtain a count of the number of active users. This is displayed in the A/U column. An active user is represented by an NCL procedure that has issued an &FILEID statement for that UDB. The connection is terminated either by the procedure ending or an &FILEFREE statement being issued. The SHOW UDBUSER command can be used to display the active users of this UDB. It should be remembered that specialized system procedures such as LOGPROC and CNMPROC represent active users of their respective UDBs and can be stopped using the SYSPARMS command LOGPROC=FLUSH etc. operand if required.
Reason:
An attempt to assign a logical fileid filename to a UDB has failed because the selected name has previously been assigned to another ddname dddddddd. A fileid can be assigned to only one UDB.
System Action:
The command is rejected.
User Action:
Select a different fileid or logically stop the conflicting UDB using the STOP operand and then proceed with assigning the fileid to the required UDB.
Reason:
An attempt has been made to change the status (eg. OPEN, CLOSE OR RESET) of a dataset to a format other than SYSOUT using the UDBCTL command and the user has insufficient command authority. Unless changed by the installation, the status of a SYSOUT format dataset can be changed by users with a command authority of 0. Changing the status of all other datasets requires a higher authority, usually authority level 2.
System Action:
The command is rejected.
User Action:
Contact your systems administrator.
Reason:
An attempt to OPEN the UDB associated with ddname dddddddd has failed because of the ACB OPEN error X`xx' or system abend code nnn.
System Action:
The UDB has not been opened and remains in closed status.
User Action:
Enter /VSAMRC.00xx at the ==> prompt to lookup VSAM ACB open error codes. Refer to the appropriate operating system manual (for example the VSAM Programmer's Guide) for a description of the error code. The SHOW UDB command can be used at any time to redisplay the error code that caused the failure. Determine the cause of the error, correct and retry.
Reason:
An attempt to assign a logical fileid has been rejected because the UDB is closed. The UDB has been closed by use of the UDBCTL command CLOSE operand.
System Action:
The assignment is rejected.
User Action:
Use the OPEN operand to re-open the UDB and retry the assignment.
Reason:
In the process of closing the last UDB that utilizes the LSR pool, SOLVE issues a DLVRP macro to delete the LSR pool. This macro has failed with the return code indicated.
System Action:
Processing continues.
User Action:
Determine the reason for the failure from the relevant VSAM manual.
Reason:
The RESET, SIS and DEFER operands of the UDBCTL command are mutually exclusive with the INPUT operand.
System Action:
The command is rejected.
User Action:
Determine the requirements of the UDB, correct the error and retry.
Reason:
The UDB to which the user was trying to assign a FILEID had not previously been opened successfully for either of two reasons: it is a dummy file, or its keylength is greater that 255 bytes. You may not assign a FILEID to a UDB that is not currently open.
System Action:
The request is rejected.
User Action:
The SHOW UDB command can be used to determine the status of the UDB.
Reason:
An attempt was made, using the UDBCTL OPEN=ddname command, to open a UDB using a system ddname that is reserved.
System Action:
The command is rejected.
User Action:
SOLVE itself has allocated to it DDnames such as those used for panel libraries, command libraries etc., which are reserved for its use only. Use a DDname that is not reserved.
Reason:
The ddname dddddddd specifies a dataset that is not a valid UDB, for one of the following reasons:
- It is a dummy file.
- Its keylength is greater than 255 bytes.
- Another reason specified in message N28511 which is written to the activity log.
System Action:
The UDB is not opened, and is flagged in error.
User Action:
If the reason for the error is unclear, check the activity log for additional messages, for example N28511. Determine your requirements for this UDB, correct and retry.
Reason:
Storage could not be obtained to process the UDBCTL command.
System Action:
The command is not processed.
User Action:
Determine the cause of the storage shortage.
Reason:
An attempt to attach or load module modlname has failed.
System Action:
The function in progress fails.
User Action:
Contact your systems administrator to determine the reason for the attach failing. Other messages will follow this describing any associated processing that is impacted.
Reason:
The module has abnormally terminated with the error SYS-yyy.
System Action:
The function in progress fails.
User Action:
Determine the reason for the failure. Other messages will follow this describing any associated processing that is impacted. If necessary report this problem to your product support representative.
Reason:
The maximum number of subtasks allowed by the DOS System Generation NTASK value has been reached.
System Action:
The function requesting this attach fails.
User Action:
Retry when the number of tasks in the system has decreased. If the problem persists, notify your systems administrator.
Reason:
The maximum number of subtasks allowed for any one partition has been reached.
System Action:
The current level of activity with FTS and/or MAI prevents the attach of a new subtask. The requested function fails.
User Action:
Retry when system activity declines.
Reason:
SOLVE failed to obtain sufficient storage for a task save area.
System Action:
The function in progress fails.
User Action:
Retry when system activity declines, or restart SOLVE in a larger partition.
Reason:
An SOLVE subtask has issued an internal abend. The reason code further clarifies the type of abend. A full list of internal abend codes may be obtained using the CAS : Message Definition menu. All internal abend codes are prefixed by $ABEND ie. $ABENDxxx-yy.
System Action:
The subtask terminates. SOLVE may also terminate.
User Action:
Use the internal abend code to obtain the cause and description of the internal abend. If the problem cannot be easily diagnosed, refer the error to your product support representative.
Reason:
A CANCEL, DISCONN or RECONN command has been successfully issued against the named userid and region combination.
System Action:
If the command is CANCEL then the users processing region(s) is/are processed for termination.
If the command is DISCONN then the users processing region(s) is/are processed for disconnection.
For the RECONN command the current terminal is connected to the target region. The current region is either terminated or disconnected.
User Action:
If a reconnection is processed successfully a panel will be displayed indicating this. Press the ENTER key to resume the disconnected processing.
Reason:
The CANCEL command requires an operand. No operands have been specified.
System Action:
The command is rejected.
User Action:
Correct the error and retry.
Reason:
A CANCEL or DISCONN command has been issued specifying an invalid userid on the U= operand.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
A CANCEL, DISCONN or RECONN command has been issued against the nominated userid. This userid is not processable by the command. Eg. Disconnection of a background userid.
System Action:
The command is rejected.
User Action:
None.
Reason:
A CANCEL or DISCONN command was issued but no regions were found to process.
System Action:
The command is rejected.
User Action:
If required issue SHOW USERS to verify the current users logged on.
Reason:
An unsupported operand (which is valid for another command) was specified on a CANCEL, DISCONN or RECONN command.
System Action:
The command is rejected.
User Action:
Correct the error and retry.
Reason:
A CANCEL WINDOW command was issued when no other window existed.
System Action:
The command is rejected.
User Action:
None.
Reason:
A CANCEL WINDOW command has successfully cancelled the users other window.
System Action:
Processing with a single window continues.
User Action:
None.
Reason:
A CANCEL command was issued specifying a user that had a numeric reconnection identifier nnnnn.
System Action:
The users reconnect region is processed for termination.
User Action:
None.
Reason:
A CANCEL, DISCONN or RECONN command has been issued for a region that is already processing a region level command.
System Action:
The command is rejected.
User Action:
Retry the command if the condition persists then report the problem to your installation help desk.
Reason:
Either RECONN or CANCEL command has specified a numeric reconnection identifier nnnnn but no matching region exists. The userid uuuuuuuu is specified for RECONN command only.
System Action:
The command is rejected.
User Action:
Verify the reconnection identifier by issuing SHOW USERS=uuuuuuuu (for RECONN comand) or SHOW USERS (for CANCEL command). If necessary retry the command.
Reason:
A RECONN command has failed due to lack of storage.
System Action:
The reconnection request is aborted.
User Action:
Retry the command if the condition persists notify your installation help desk.
Reason:
An attempt was made to CANCEL or DISCONN. The command operand authority level required exceeds that of the requestor.
System Action:
The command is rejected.
User Action:
None.
Reason:
A RECONN command has been issued from a terminal other than that specified in the message. The system is currently configured so that reconnection can only occur at the same terminal as disconnection.
System Action:
The request is rejected.
User Action:
If possible re-logon at the indicated terminal and retry the request.
Reason:
A CANCEL or DISCONN command specified a region that could not be processed. The region specified is not in a valid state for processing by the command.
System Action:
The command is rejected.
User Action:
If required issue SHOW USERS to verify the current users logged on.
Reason:
A CANCEL command with the FORCE operand can only be issued when a CANCEL command has already been issued without the FORCE operand.
System Action:
None.
User Action:
Issue the CANCEL command without the FORCE operand.
Reason:
A CANCEL command with the FORCE operand cannot be issued for a user that is in the process of signing off.
System Action:
None.
User Action:
None.
Reason:
A CANCEL command with the FORCE operand can only be issued for a terminal owning region such as an LU2 or LU1 type session.
System Action:
None.
User Action:
Issue the CANCEL command without the FORCE operand for this user.
Reason:
A VTAM SENDCMD macro was rejected with the specified error codes.
System Action:
The VTAM command is unable to be executed.
User Action:
Determine the meaning of the error codes from the appropriate VTAM Programming manual.
Reason:
A VTAM SENDCMD macro was rejected with the specified error codes.
System Action:
The VTAM command is unable to be executed.
User Action:
Determine the meaning of the error codes from the appropriate VTAM programming manual.
Reason:
This message confirms the successful completion of an LSRPOOL command.
System Action:
None.
User Action:
None.
Reason:
An LSRPOOL command has been issued to replace, update or reset the pending LSR pool definition. However there is an LSR pool currently active. You must code `FORCE' on your LSRPOOL command in this case.
System Action:
The command is rejected.
User Action:
Reissue the command with `FORCE' specified.
Reason:
An LSRPOOL command has been issued with a parameter size=num defining a set of buffers to be allocated to the VSAM shared resources pool. However the number ( num ) is invalid.
If MVS/XA or MVS/ESA, the count must be 0, or greater than 3, to a maximum of 65535.
If not MVS/XA or MVS/ESA, it must be 0, or 3 to 32767, and the product of (buffer size * count) must not exceed 16M.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
You have specified a buffer size that is only supported in MVS/XA or MVS/ESA.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
Hiperspace buffers must be a multiple of 4K to a maximum of 32K.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The count of hiperspace buffers must be from 0 to 16777215 (16M-1).
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
A buffer size specification on an LSR command has been duplicated within a specific section. For example:
DATA 4K=10 2K=5 4K=8 The second 4K is duplicated.
This does not include the case where a size is repeated in separate sections of the command for example:
DATA 4K=10 INDEX 4K=5
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The use of the INDEX keyword on the LSR command to request a separate index buffer pool is not supported on this operating system.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The use of the HIPERSPACE or HS keyword on the LSR command to request MVS/ESA hiperspace buffers is not supported on this operating system.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The POOL=n keyword of the LSR command has specified an invalid pool number. The number is less than 0, or greater than the maximum pool number supported by the LSR command. In MVS/XA and MVS/ESA, a maximum pool number of 15 is allowed. All other environments only support a pool number of 0.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
This message is the header line for a SHOW LSR display. It indicates which definition (active, pending, or default) is being displayed.
System Action:
None.
User Action:
None.
Reason:
This is one line of the SHOW LSR display. This line displays the maximum allowable key length for the pool, maximum number of strings available, whether I/O control blocks are fixed in storage (YES or NO), and whether I/O buffers are fixed in storage (YES or NO).
System Action:
None.
User Action:
None.
Reason:
This is one line of the SHOW LSR display. This line is a header for the subsequent lines of the display (see N15A23).
NOTE: The INDEX, H-SPACE, and X-H-SPACE headings will only be displayed if separate index pools and/or hiperspace buffers are supported by the current operating system.
System Action:
None.
User Action:
None.
Reason:
This is one line of the SHOW LSR display. This line describes one set of buffers contained in the pool:
size is the size of the buffers,
count is the number of buffers of this size allocated.
index is the count of index buffers if a separate index pool exists.
h-space and x-h- space are the data and index pool hiperspace buffer counts.
NOTE: The count can be zero if one of the other counts are non-zero.
System Action:
None.
User Action:
None.
Reason:
This is the header line for a multi-line display of statistics about a currently active LSR pool. The pool number is shown in the message.
System Action:
None.
User Action:
None.
Reason:
This is one line of a SHOW LSR=STATISTICS display. This line describes the attributes of the active LSR pool. It gives the maximum allowable key length for the pool, maximum number of strings available, whether I/O control blocks are fixed in storage (YES or NO), whether I/O buffers are fixed in storage (YES or NO), the maximum number of concurrent strings used, and the current number of open datasets using the pool
System Action:
None.
User Action:
None.
Reason:
This is one line of a SHOW LSR=STATISTICS display. This is a header for the following lines describing the buffers in the pool (see N15A33).
System Action:
None.
User Action:
None.
Reason:
This is one line of a SHOW LSR=STATISTICS display. This line describes one set of buffers within the pool. Statistics are:
size The size of each buffer
count The number of buffers of this size in the pool.
p.reads Number of physical reads into this set of buffers.
buf found The number of read requests satisfied from the LSR pool.
uiw The number of user-initiated writes from the LSR pool.
nuiw The number of non-user-initiated writes from the LSR pool.
% found The percentage of reads satisfied from the LSR pool.
hs-count If hiperspace buffers are defined for this buffer size, the the number of hiperspace buffers.
System Action:
None.
User Action:
None.
Reason:
This is one line of a SHOW LSR=STATISTICS display. This line indicates that the pool currently being displayed has a separate data and index buffer set defined, and that the following N15A33 messages relate to the DATA pool.
System Action:
None.
User Action:
None.
Reason:
This is one line of a SHOW LSR=STATISTICS display. This line indicates that the pool currently being displayed has a separate data and index buffer set defined, and that the following N15A33 messages relate to the INDEX pool.
System Action:
None.
User Action:
None.
Reason:
A request for a display of LSR statistics has been unsuccessful for the reason given.
System Action:
None.
User Action:
None.
Reason:
A SHOW LSR=xxxx command was entered, but the value of xxxx was not one of: STATISTICS, CURRENT, PENDING or DEFAULT
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
A SHOW LSR command was issued with invalid parameters.
System Action:
The command is rejected.
User Action:
Correct the command and retry.
Reason:
The entered SUBSYS command has completed successfully.
System Action:
none.
User Action:
none.
Reason:
The entered SUBSYS DEFINE command failed. There is already a defined subsystem of that name.
System Action:
THe command is not processed.
User Action:
Correct the subsystem name if required.
Reason:
The entered SUBSYS command failed. There is no subsystem of that name defined.
System Action:
THe command is not processed.
User Action:
Correct the subsystem name if required.
Reason:
The entered SUBSYS command failed. The subsystem is pending deletion.
System Action:
THe command is not processed.
User Action:
Wait until the subsystem finishes processing the deletion request.
Reason:
The entered SUBSYS FORCE command failed. The subsystem cannot be forced at this time.
System Action:
THe command is not processed.
User Action:
A subsystem can only be forced when the subsystem subtask is processing user code. THis is indicated by the FORCE column on SHOW SUBSYS, CHeck the output of a SHOW SUBSYS and retry if necessary.
Reason:
The listed subsystem has had the named program successfully loaded, ready for activation.
System Action:
none
User Action:
none
Reason:
The listed subsystem program could not be loaded, The failure reason is shown.
System Action:
The subsystem remains inactive.
User Action:
Investigate the reason and correct it.
Reason:
The listed subsystem is now running, and ready to process requests.
System Action:
The subsystem becomes active.
User Action:
none.
Reason:
The listed subsystem subtask could not be attached. There is an additional message on the activity log.
System Action:
The subsystem stays inactive.
User Action:
INvestigate the problem.
Reason:
The listed subsystem subtask abended before initializing.
System Action:
The subsystem stays inactive.
User Action:
Check the System log and SOLVE job log for ABEND information (such as an indicative dump). Use the ABEND information to determine why the SUBSYS ABENDed.
Reason:
The listed subsystem has stopped.
System Action:
none.
User Action:
none.
Reason:
The listed subsystem has been deleted.
System Action:
none.
User Action:
none.
Reason:
The listed subsystem could not be started, as there was a shortage of storage.
System Action:
The subsystem stays inactive.
User Action:
INvestigate the reason for storage shortage, and then retry.
Reason:
The listed subsystem could not be started, as it is already started.
System Action:
The subsystem is already started.
User Action:
None.
Reason:
The listed subsystem could not be started, as the subsystem program failed to load.
System Action:
The subsystem remains inactive.
User Action:
Determine the reason for the load failure, correct it, and restart the subsystem.
Reason:
The listed subsystem could not be stopped as it is not started.
System Action:
The subsystem remains inactive.
User Action:
none.
Reason:
THe SUBSYS RELOAD command is not allowed when the target subsystem is started. It must be stopped first.
System Action:
The command is not processed.
User Action:
Stop the subsystem and reissue the command.
Reason:
THe SUBSYS DELETE command is not allowed when the target subsystem is started. It must be stopped first.
System Action:
The command is not processed.
User Action:
Stop the subsystem and reissue the command.
Reason:
THe SUBSYS STOP command could not be processed as there was s storage shortage that prevented us from obtaining storage to process the stop request.
System Action:
The command is not processed.
User Action:
Investigate the storage shortage and retry,
Reason:
THe indicated Subsystem has abended. The ABEND code is shown
System Action:
The subsystem stops.
User Action:
Investigate the abend reason.
Reason:
The indicated Subsystem had a SUBSYS FORCE command successfully processed.
System Action:
The subsystem stops.
User Action:
None.
Reason:
This message will be issued by SHOW SUBSYS when no subsystems are defined, or if a SHOW SUBSYS=name command is issued and no subsystems match the supplied name or prefix.
System Action:
None.
User Action:
None.
Reason:
This message will be issued by SHOW SUBSYS to head up the subsystem list.
The columns are:
SUBSYS The subsystem name
PROGRAM The program name
STATUS The subsystem status
QREQ The current number of queued requests
FRC Whether the subsystem can be forced
PLF The parameter list format
AUT The Automatic call replace option
STOP-REASON The reason that the subsystem was stopped
System Action:
None.
User Action:
None.
Reason:
This message will be issued by SHOW SUBSYS for each listed subsystem. refer to message N15F02 for the meanings of the columns.
System Action:
none.
User Action:
None.
Reason:
The SHOW SUBSYS command had invalid or unrecognized parameters.
System Action:
The command is not processed.
User Action:
Correct the parameters.
Reason:
The SHOW SUBSYS command had invalid or unrecognized data after the SUBSYS= operand.
System Action:
The command is not processed.
User Action:
Correct the parameters.
Reason:
SOLVE was unable to attach an operating system subtask to perform a function
System Action:
The attach fails.
User Action:
Contact your systems administrator to determine the reason for the attach failing. Other messages will follow this describing any associated processing that is impacted.
Reason:
A subtask attached by SOLVE has abended. The message indicates the abend code and PSW. (if no SDWA was available, the PSW is not provided and a message indicates that no SDWA was available).
N15Z21 messages follow with register information.
System Action:
Depends on the subtask purpose.
User Action:
If the subtask is a user program (eg &CALL program), examine the abend and correct the code. SOLVE subtask abends should be notified to Technical Support.
Reason:
This message follows the N15Z20 message and provides register information. 4 messages will contain all 16 registers.
Refer to message N15Z20 for details.
System Action:
See messages N15Z20
User Action:
See message N15Z20
Reason:
No LOG DD cards have been included in the product execution JCL.
System Action:
The system continues processing but no hardcopy logging can be performed. LOGPROC still receives each log record.
User Action:
If required, include DD cards for the log files. This can be done dynamically using the ALLOC command and logging can then be started using the LOGSWAP command.
Reason:
Storage shortage prevents use of the activity log.
System Action:
Processing continues.
User Action:
Increase job region/partition size and investigate cause of storage shortage.
Reason:
An I/O error has occurred on the log dataset defined by the specified DD card, caused by the specified abend code.
System Action:
Swaps to the next available log dataset. If no more logs are available logging is halted.
User Action:
If logging is halted but is still required, a new log dataset may be dynamically allocated (using ALLOC) and then swapped to (using LOGSWAP).
Reason:
A LOGSWAP command has been entered before a previous LOGSWAP command has completed.
System Action:
The command is rejected.
User Action:
Await completion of the previous LOGSWAP operation, and try again if necessary.
Reason:
A LOGSWAP command has been entered to cause use the next available hardcopy log but no more are available.
System Action:
The command is rejected. Processing continues with the last available log.
User Action:
If additional logs are required, they may be dynamically allocated using the ALLOC command.
Reason:
Confirms successful completion of a LOGSWAP command and shows the DD name of the new log dataset.
System Action:
None.
User Action:
None.
Reason:
During LOGSWAP processing the next activity log file could not be opened so activity logging has been halted.
System Action:
Activity logging stops.
User Action:
Refer to message N16103 for required action.
Reason:
During LOGSWAP processing the log dataset with DDname xxxxxxxx could not be OPENed.
System Action:
The system tries the next available log dataset.
User Action:
None.
Reason:
Confirms completion of LOGSWAP processing. This message provides a record of the previous log dataset and the user who requested the LOGSWAP.
System Action:
None.
User Action:
None.
Reason:
Confirms completion of LOGSWAP processing to the log identified by the xxxxxxxx DD statement.
System Action:
None.
User Action:
None.
Reason:
An I/O error occurred on the current log and the system has generated an internal LOGSWAP operation.
System Action:
Logging will continue with the next available log if one exists. If no additional log remains a warning message will be issued to advise that logging has been halted. In this case the SYSPARMS command SYSLOG operand can be used to request logging to the system log until a restart can be performed.
User Action:
Determine the reason for the I/O error and rectify it.
Reason:
In a VM/GCS system, the LOG1 FILEDEF statement identifies a spooled printer but the (only) printer is in use by the identified DD.
System Action:
Activity logging is halted.
User Action:
Amend the SOLVE startup procedure to avoid the conflicting use of the spooled printer. Consider activity logging to CMS disk datasets.
Reason:
Indicates successful processing of an OCSID command.
System Action:
This is the value that will subsequently be returned in the NCL system variable OCSID if requested from this window. The OCSID is displayed in the right hand side of the OCS window.
User Action:
None.
Reason:
The OCSID command allows an ID of up to 8 characters. A longer ID was specified and has been truncated.
System Action:
None.
User Action:
None.
Reason:
Indicates successful processing of an OCSID command that specified a null ID to delete the current OCSID.
System Action:
Any existing OCSID is deleted. At this time the OCSID NCL system variable will return a null value.
User Action:
None.
Reason:
An OCSID greater than 8 characters was specified, but the ID could not be truncated because it contains DBCS shift-in or shift-out characters.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
An attempt was made to set the OCS window Id with the OCSID command but the current environment does not have an OCS window.
System Action:
The command is rejected.
User Action:
None.
Reason:
The specified operand, entered in conjunction with a PROFILE, SHOW or SYSPARMS command, is not a valid operand for the command.
System Action:
The command is rejected.
User Action:
Correct and retry. The operand may be genuinely invalid or may be valid only for a feature which is not licensed.
Reason:
The specified operand, entered in conjunction with a PROFILE, SHOW or SYSPARMS command, is a valid operand for the command but its value is invalid.
System Action:
The command is rejected.
User Action:
Correct and retry.
Reason:
The specified operand, entered in conjunction with a PROFILE, SHOW or SYSPARMS command was valid in a previous release of SOLVE but is no longer supported.
System Action:
The command is ignored.
User Action:
Check the Release Summary for obsolete command operands.
Reason:
An APPLSTAT command could not be processed because of storage shortage.
System Action:
The command is rejected.
User Action:
Retry at a later time when the storage shortage is relieved. If necessary, increase the region size.
Reason:
A SYSPARMS NONSWAP command has been entered but it is not valid for use in this operational environment.
System Action:
The command is rejected.
User Action:
None.
Reason:
A SYSPARMS NONSWAP command has been rejected because the system is not APF authorized.
System Action:
The command is rejected.
User Action:
Contact your systems administrator to determine why the system is not APF authorized. Other processing may be limited without APF authorization.
Reason:
A SYSPARMS NONSWAP=NO command has been rejected because the system is already running swappable.
System Action:
The command is ignored.
User Action:
None.
Reason:
A SYSPARMS NONSWAP=YES command has been rejected because the system is running non-swappable.
System Action:
The command is ignored.
User Action:
None.
Reason:
A SYSPARMS MODLOAD=modname command failed. bbbb and cccc show the return codes from the LOAD macro.
System Action:
The module specified is not loaded.
User Action:
Determine the cause of the error and retry.
Reason:
A SYSPARMS MODDEL=modname command failed.
System Action:
The specified module is not deleted.
User Action:
Retry specifying the correct module name.
Reason:
A SYSPARMS NONSWAP=NO command has been issued (under MVS) to make SOLVE run swappable. The attempt has failed, since AOM is running in cross-memory mode, and requires SOLVE to run non-swappable.
System Action:
The command is rejected. SOLVE will keep running non-swappable.
User Action:
None.
Reason:
A SYSPARMS CMDREPL=aaaaaaaa command has been issued, however aaaaaaaa is not the exact name of a known command. To replace a command with an NCL procedure, the procedure name must be an exact match for the command is it replacing.
System Action:
The command is rejected.
User Action:
Check the spelling of the command and reissue.
Reason:
A SYSPARMS CMDREPL=aaaaaaaa command has been issued, but it is not valid for command aaaaaaaa to be replaced by an NCL procedure.
System Action:
The command is rejected.
User Action:
None. The command cannot be replaced.
Reason:
A SYSPARMS CMDREPL=aaaaaaaa has been issued, but command aaaaaaaa is already overridden by a global equate, or has been replaced by an OML procedure.
System Action:
The command is rejected.
User Action:
None.
Reason:
A SYSPARMS UNLOAD= command has been issued specifying a generic NCL procedure or DDname. This message shows how many NCL procedures were unloaded as a result of the command.
System Action:
nnn NCL procedures have been unloaded.
User Action:
None.
Reason:
A request has been received by Dataset Services for an action to be performed on a specified DD. The request has failed because the DD does not exist.
System Action:
The request fails.
User Action:
Allocate the specified DD then retry the request.
Reason:
A request has been received by Dataset Services for an action to be performed on a specified dataset referenced by dataset name aaaaaaaa. The request has failed because the dataset does not exist.
System Action:
The request fails.
User Action:
Allocate the specified dataset then retry the request.
Reason:
A request has been received by Dataset Services for an action to be performed on a specified member of a Partitioned DataSet (PDS). The request has failed because the member aaaaaaaa does not exist.
System Action:
The request fails.
User Action:
Check that the member is correct.
Reason:
A request has been received by Dataset Services for an action to be performed on a specified dataset. The request has failed because the dataset is not allocated to SOLVE.
System Action:
The request fails.
User Action:
Allocate the dataset to SOLVE and retry the request.
Reason:
The DYNALLOC macro has failed performing a Dataset Services action. The following information is returned:
aa is the verb code specified in the request block.
bb is the return code in Register 15.
cccc is the SVC99 error reason code.
dddd is the SVC99 information reason code.
System Action:
The request fails.
User Action:
Dynamic allocation return code information is found in the following IBM manual, chapter, and section:
z/OS MVS Programming: Authorized Assembler Services Guide (Document Number SA22-7608)
Requesting Dynamic Allocation Functions
SVC 99 Parameter List Verb Codes and Text Units, By Function
The verb index (VB) is one of the following:
Return code (RC) and feedback codes (E= and I=) are documented in the following section of the same chapter: Interpreting DYNALLOC Return Codes.
Investigate the reason for the failure using the supplied information. Check the SOLVE activity log for system messages that were returned by DYNALLOC processing.
Reason:
A request has been received by Dataset Services for an action to be performed on a specified dataset. The request has failed because it requires exclusive access to the dataset, but another task in the system has the dataset allocated.
System Action:
The request fails.
User Action:
Obtain exclusive access to the dataset and retry the request.
Reason:
A request has been received by Dataset Services to add an ALIAS for a member in a Partitioned DataSet (PDS). The ALIAS name matched the name of a member which already existed in the PDS, so this member has been replaced by the ALIAS entry.
System Action:
None.
User Action:
None.
Reason:
A request has been received by Dataset Services to read a Directory entry from a Partitioned DataSet (PDS). The read has encountered the end of the current directory and has begun to read the directory of the next dataset in the DD concatenation.
System Action:
None.
User Action:
None.
Reason:
A request has been received by Dataset Services to read one or more records from a sequential file or member of a Partitioned DataSet (PDS). During read processing, the end of the file or PDS member was found.
System Action:
None.
User Action:
None.
Reason:
A request has been received by Dataset Services to CLOSE a file to which records were being written. The file supports blocked records and some records in the last block of records had not been written to the file, so before the CLOSE is performed the remaining records are written to the file. During the write of the final block, an error occurred.
System Action:
The file is closed.
User Action:
To obtain more specified error information, a FLUSH request should be performed before the CLOSE. The FLUSH request writes the remaining block of records to the file and returns more specific information about any errors which may occur.
Reason:
A request has been received by Dataset Services to CLOSE a member of a Partitioned DataSet (PDS) which was being accessed. The STOW macro which is issued to end access to the PDS member has failed. The STOW macro is an IBM MVS macro.
System Action:
The member is not closed.
User Action:
Investigate the reason for the STOW failure using the return code shown in the appropriate IBM manual.
Reason:
A request has been received by Dataset Services to close a file and the close of the file has failed. The error is not expected and the exact failure reason cannot be determined.
System Action:
The file is not closed.
User Action:
Investigate the system log for related error messages.
Reason:
A request has been received by Dataset Services to close a file and the CLOSE has resulted in an abend. The abend code is shown.
System Action:
The file is not closed.
User Action:
Investigate the reason for the abend using the abend code shown.
Reason:
A request has been received by Dataset Services to DELETE a dataset and the DELETE request has failed because the dataset has an expiry date and this date has not been reached yet.
System Action:
The dataset is not deleted.
User Action:
None.
Reason:
A request has been received by Dataset Services to DELETE a dataset and the DELETE request has failed. The Operating System SCRATCH routine has indicated that an error has occurred.
System Action:
The dataset is not deleted.
User Action:
Check the system log and job log for related error messages.
Reason:
A request has been received by Dataset Services to RENAME a dataset and the RENAME request has failed. The request invoked an operating system function using macro aaaaaaaa, which returned Return Code bb and Feedback Code cccc.
System Action:
The dataset is not renamed.
User Action:
Investigate the reason for the failure using the supplied information.
Reason:
A request has been received by Dataset Services to RENAME a dataset and the RENAME request has been rejected because the dataset is distributed over more than one volume. Multi-volume datasets are not supported by Dataset Services.
System Action:
The dataset is not renamed.
User Action:
None.
Reason:
A request has been received by Dataset Services to RENAME a dataset and the RENAME request has been rejected because the dataset is not resident on a Direct Access Storage Device (DASD). Dataset Services does not support rename of tape or cartridge datasets.
System Action:
The dataset is not renamed.
User Action:
None.
Reason:
A request has been received by Dataset Services to perform an action on a dataset but the dataset has been migrated (for example, by DFHSM) and MIGRATE=YES was not specified on the request.
System Action:
The action is not performed.
User Action:
Specify MIGRATE=YES on the request or recall the dataset and retry the request.
Reason:
A request has been received by Dataset Services to perform an action on a dataset but the volume on which the dataset resides is not mounted and MOUNT=YES was not specified on the request.
System Action:
The action is not performed.
User Action:
Specify MOUNT=YES on the request or mount the volume and retry the request.
Reason:
A request has been received by Dataset Services to ENQ a dataset or to OPEN a dataset for output, but the ENQ has failed.
System Action:
None.
User Action:
This usually indicates that another user is accessing the dataset. The other user may hold an ENQ for a very short time whilst accessing the dataset, in which case if the request is retried it may work.
Reason:
A request has been received by Dataset Services to perform an action on a dataset, but the request cannot be performed because the dataset is currently OPEN.
System Action:
The request fails.
User Action:
CLOSE the dataset and retry the request.
Reason:
A request has been received by Dataset Services to perform an action on a dataset, but the request cannot be performed because the dataset is a VSAM dataset. Some Dataset Services functions do not support VSAM files.
System Action:
The request fails.
User Action:
None.
Reason:
A request has been received by Dataset Services for an action to be performed on a specified logstream referenced by logstream name aaaaaaaa. The request has failed because the logstream does not exist.
System Action:
The request fails.
User Action:
Check and correct or create the specified logstream then retry the request.
Reason:
A system logger request has encountered an error. The system return code (aaa, decimal) and reason code (bbbbbbbb, hex) are displayed.
System Action:
The request fails.
User Action:
The return and reason codes can be looked up in the IBM Assembler Programming Reference in the sections on the System Logger macros, IXG.... Take action as required.
Reason:
A request has been received by Dataset Services for an action to be performed on a specified HFS path referenced by path name aaaaaa. The request has failed because the path does not exist.
System Action:
The request fails.
User Action:
Create the specified path then retry the request.
Reason:
A request has been received by Dataset Services to OPEN a dataset and the OPEN of the dataset has failed.aaaaaaaa is the DDname used in the failed open request.
System Action:
The request fails.
User Action:
Check for relevant system messages on the system log and job log.
Reason:
A request has been received by Dataset Services to perform an action on a dataset and the action has resulted in an I/O error. The DDname used in the request was 'aaaaaaaa'.
System Action:
The request fails.
User Action:
Refer to the SOLVE activity log for messages which supply more specific information about the error.
Reason:
Dataset Services received a request to perform an action on a data set, and the action resulted in an abend. abbbb is the abend code returned from the failed action.
System Action:
The request fails.
User Action:
If the abend code indicates system level error, correct the error and retry the request. If you cannot determine the cause of the abend, contact Technical Support.
Reason:
A request has been received by Dataset Services to write a record to a file but the record is too long for the dataset.
System Action:
The request fails.
User Action:
Either truncate the record to a valid length or redefine the file with a larger maximum record length.
Reason:
A request has been received by Dataset Services to read the next entry in a Partitioned DataSet (PDS) directory, and the length of the directory block returned by the system is invalid.
System Action:
The request fails.
User Action:
This indicates that the directory of the PDS is corrupted. Investigate the cause of the corruption.
Reason:
A request has been received by Dataset Services to OPEN a dataset and the OPEN MODE is invalid.
System Action:
The request fails.
User Action:
Correct the MODE option and retry. Valid modes are INPUT, OUTPUT, and EXTEND.
Reason:
A request has been received by Dataset Services to update a PDS directory entry (eg. due to CLOSE of a member or ADD ALIAS request) and the length of the userdata supplied is not valid.
System Action:
The request fails.
User Action:
Correct the userdata value and retry.
Reason:
A request has been received by Dataset Services to update a PDS directory entry (eg. due to CLOSE of a member or ADD ALIAS request) and the userdata contains an invalid number of TTRs. The number of TTRs must be from 0 to 3, and the length of the userdata must match the length expected for the number of TTRs specified.
System Action:
The request fails.
User Action:
Correct the userdata value and retry.
Reason:
A request has been received by Dataset Services to OPEN a file with MODE=EXTEND or to OPEN a file which is allocated with DISP=MOD but the request has been rejected because the file is a Partitioned DataSet (PDS) or a member of a PDS.
System Action:
The request fails.
User Action:
Alter the ALLOCation and OPEN requests to specify DISP=SHR/OLD and MODE=OUTPUT respectively. It is invalid to open a PDS or PDS member for EXTEND.
Reason:
A request has been received by Dataset Services to OPEN a dataset, however the dataset blksize is zero or invalid.
System Action:
The request fails.
User Action:
Determine why the dataset blksize is not valid. Reallocate the dataset and try again.
Reason:
A request has been received by Dataset Services which specifies the DD name of a file to be actioned, but the DD name supplied is not a valid name.
System Action:
The request fails.
User Action:
Correct the DD name and retry the request.
Reason:
A request has been received by Dataset Services which specifies the name of a Partitioned DataSet (PDS) to be actioned but the member name is not a valid name.
System Action:
The request fails.
User Action:
Correct the member name and retry the request.
Reason:
A request has been received by Dataset Services which specifies the name of a Partitioned DataSet (PDS) to be actioned but the member name is not a valid name.
System Action:
The request fails.
User Action:
Correct the member name and retry the request.
Reason:
A request has been received by Dataset Services which specifies the name of a dataset to be actioned but the dataset name is not a valid name.
System Action:
The request fails.
User Action:
Correct the dataset name and retry the request.
Reason:
A request has been received by Dataset Services which specifies the name of a dataset to be actioned but the dataset name is not a valid name.
System Action:
The request fails.
User Action:
Correct the dataset name and retry the request.
Reason:
A request has been received by Dataset Services which specifies a parameter which is not valid.
System Action:
The request fails.
User Action:
Locate the incorrect parameter, correct it and retry the request.
Reason:
A request has been received by Dataset Services which specifies a list of DD names to be actioned, but the format of the list is not valid.
System Action:
The request fails.
User Action:
Correct the format of the list and retry the request. The list must be one or more valid DD names separated by commas and may be enclosed in parentheses.
Reason:
A request has been received by Dataset Services which specifies a list of DD names to be actioned, but the list does not have at least 2 names.
System Action:
The request fails.
User Action:
Add more DD names to the list and retry the request.
Reason:
A request has been received by Dataset Services which specifies a list of DD names to be actioned, but the list contains a DD name which appears more than once in the list.
System Action:
The request fails.
User Action:
Ensure that each DD name in the list only appears once and retry the request.
Reason:
A request has been received by Dataset Services which specifies the name of a logstream to be actioned but the name is not a valid logstream name.
System Action:
The request fails.
User Action:
Correct the logstream name and retry the request.
Reason:
A request has been received by Dataset Services which requires that the dataset to be actioned must have a specific dataset organisation. The dataset is not of the required organisation.
System Action:
The request fails.
User Action:
Redefine the dataset to have the specified dataset organisation.
Reason:
A request has been received by Dataset Services which specifies an action to be performed on a member of a Partitioned DataSet (PDS), but the member name has not been supplied.
System Action:
The request fails.
User Action:
Specify the member name and retry the request.
Reason:
A request has been received by Dataset Services which specifies an action to be performed on a Partitioned DataSet (PDS), but a member name has been supplied and no member name is allowed for the request.
System Action:
The request fails.
User Action:
Remove the member name and retry the request.
Reason:
A request has been received by Dataset Services which involves a dataset which contains spanned records. Spanned record datasets are not supported by Dataset Services.
System Action:
The request fails.
User Action:
None.
Reason:
A request has been received by Dataset Services to RENAME a member of a Partitioned DataSet (PDS), but a member with the NEW name already exists in the PDS.
System Action:
The request fails.
User Action:
Delete the target member or choose a different new member name.
Reason:
A request has been received by Dataset Services to add a new member to a Partitioned DataSet (PDS), but there is no free space in the PDS directory.
System Action:
The request fails.
User Action:
Delete unwanted members from the PDS, or redefine the PDS with a larger directory.
Reason:
A request has been received by Dataset Services to obtain an ENQ for a file, but the specified ENQ is already held by the requestor. This usually denotes a logic error in the code being executed for not recognizing that the ENQ was already held.
System Action:
None.
User Action:
Notify the organization responsible for the code being executed of the ENQ problem.
Reason:
A request has been received by Dataset Services to release an ENQ for a file, but the specified ENQ is not held by the requestor.
System Action:
None.
User Action:
None.
Reason:
A request has been received by Dataset Services which specifies the name of an HFS path to be actioned but the path name is not a valid name.
System Action:
The request fails.
User Action:
Correct the path name and retry the request.
Reason:
A request received by Dataset Services specifies the name of a data set that is not qualified (that is, an attempt to allocate a high-level qualifier).
System Action:
The request fails.
User Action:
Specify a qualified data set name, and retry the request.
Reason:
A request has been received by Dataset Services to ALLOCate a new or existing file, but some required parameters have been omitted. Dataset Services is unable to determine if the ALLOC request is for a new dataset, an existing dataset or a SYSOUT dataset.
System Action:
The ALLOC request is rejected.
User Action:
Specify either the STATUS operand or CLASS operand.
Reason:
A request has been received by Dataset Services to ALLOCate a new or existing file, but a required parameter has been omitted. aaaa shows the MDO key of the field which has been omitted. The MDO is mapped by by the map $DSCBD3Z. The MDO keys are in << >> structures in the map source which can be viewed from Mapping Services.
System Action:
The ALLOC request is rejected.
User Action:
Use the ASN.1 map for the request and key aaaa to determine which operand has been omitted, then retry the request with the operand supplied.
Reason:
A request has been received by Dataset Services to ALLOCate a new or existing file, but a parameter has been specified which is not allowed for this request. aaaa shows the MDO key for the operand which is in error. The MDO is mapped by map $DSCBD3Z. The keys are in the << >>structures in the maps source which can be viewed from Mapping Services.
System Action:
The ALLOC request is rejected.
User Action:
Use the ASN.1 map for the request and key aaaa to determine which operand is invalid, then retry the request without the operand supplied.
Reason:
A request has been received by Dataset Services to ALLOCate a new or existing file, but a parameter has been specified which is invalid. aaaa shows the MDO key for the operand which is invalid. The MDO is mapped by the map $DSCBD3Z. The keys are in the << >> structures in the map source which can be viewed from Mapping Services.
System Action:
The ALLOC request is rejected.
User Action:
Use the ASN.1 map for the request and key aaaa to determine which operand is invalid, then retry the request after correcting the operand value.
Reason:
A request has been received by Dataset Services to allocate a new or existing file, but the request has failed due to a Systems Managed Storage error. The following fields are shown:
aa - The DYNALLOC verb code for the request.
bb - The return code in Register 15 on completion.
cccccccc - The SMS reason code for the failure.
System Action:
The ALLOC request is rejected.
User Action:
Investigate the reason for refusal by SMS, using the DYNALLOC verb code and SMS reason code. Refer to the activity log for any system messages related to the failure.
Reason:
A request has been received by Dataset Services to retrieve information about a DD using the Relative Request Number for the DD, and the operating system has indicated that the specified Relative Request Number is the highest for any dataset allocated to SOLVE.
System Action:
This message is for information only and informs the requestor that any request for information for a Relative Request Number higher than the one requested will fail.
User Action:
None.
Reason:
A request has been received by Dataset Services to retrieve information about a DD using the Relative Request Number for the DD, but no DD exists with the specified Relative Request Number.
System Action:
The request fails.
User Action:
Correct the Relative Request number and retry the request. When obtaining information by Relative Request Number, always check for return of message N16C65 which indicates that the highest Relative Request Number has been reached.
Reason:
A request has been received by Dataset Services to allocate a NEW dataset but a dataset with the specified name already exists.
System Action:
The request fails.
User Action:
Delete the existing dataset or choose a different dataset name for the new dataset name.
Reason:
A request has been received by Dataset Services to allocate a dataset but the DD name specified is already in use.
System Action:
The request fails.
User Action:
Choose a different DD name or unallocate the existing DD and retry the request.
Reason:
A request has been received by Dataset Services which returns information in an MDO. An error was encountered whilst the MDO was being updated with the returned information.
System Action:
The request has been performed as requested but no information is returned.
User Action:
Investigate the reason for MDO update failure using the shown return code and feedback values. These are documented in the NCL Reference.
Reason:
A request has been received by Dataset Services which involves a call to a system Utility Module. The Utility Module is ATTACHed as a subtask of SOLVE. The ATTACH has failed.The system Utility Module is 'aaaaaaaa'.
System Action:
The request fails.
User Action:
Investigate the reason for the ATTACH failure using the shown return code.
Reason:
A request has been received by Dataset Services which has failed due to errors during retrieval of dataset information. The following information is shown:
aa : A number indicating which function failed.
04 = DDname not found (DEVTYPE failed)
08 = Allocation Query failed (DYNALLOC failed)
12 = RDJFCB failed
16 = OBTAIN failed
20 = Abend occurred
bb : The return code from the requested function if applicable.
System Action:
The request fails.
User Action:
Investigate the cause of the problem by checking the meaning of the return code for the particular function.
Reason:
A request has been received by Dataset Services which required a RDJFCB macro to be issued. The macro call failed with the return code as shown.
System Action:
The request fails.
User Action:
Investigate the reason for the RDJFCB failure using the shown return code.
Reason:
A request has been received by Dataset Services which required a OBTAIN macro to be issued. The macro call failed with the return code as shown.
System Action:
The request fails.
User Action:
Investigate the reason for the OBTAIN failure using the shown return code.
Reason:
A request has been received by Dataset Services which resulted in an ENQ or DEQ being issued. The ENQ or DEQ failed with the return code as shown.
System Action:
The request fails.
User Action:
Investigate the reason for the ENQ or DEQ failure using the shown return code.
Reason:
A request has been received by Dataset Services which caused data to be written to or read from a dataset. A NOTE Macro is issued to note the position in the dataset after the read or write is performed. The NOTE macro has failed.
System Action:
The request fails.
User Action:
Investigate the reason for the NOTE failure using the shown return code. Refer to the system log and job log for related error messages.
Reason:
A request has been received by Dataset Services which requested an operating system function, and the operating system function has failed.
System Action:
The request fails.
User Action:
Investigate the reason for the failure using the shown return code and function name. Refer to the system log and job log for related error messages.
Reason:
A request has been received by Dataset Services which requested an operating system function, and the operating system function has abended.
System Action:
The request fails.
User Action:
Investigate the reason for the failure using the shown return code and function name. Refer to the system log and job log for related error messages.
Reason:
A request has been received by Dataset Services which specifies a path name which is invalid.
System Action:
The request fails.
User Action:
Correct the path name and retry the request.
Reason:
A request has been received by Dataset Services which opens a new path to a dataset, but a path with the specified name already exists.
System Action:
The request fails.
User Action:
Close the existing path name or change the path name and retry the request.
Reason:
A request has been received by Dataset Services which access an existing path to a dataset, but no path exists with the specified name.
System Action:
The request fails.
User Action:
Correct the path name or open a path with the required name and retry the request.
Reason:
A request has been received by Dataset Services which access an existing path to a dataset, but the requested function is not available on the existing path. For example, a path has been opened to a Sequential File and a request to read a PDS directory has been encountered.
System Action:
The request fails.
User Action:
Correct the request type or open a path of the desired class and retry the request.
Reason:
A request has been received by Dataset Services which access an existing path to a dataset, but the requested function is not available on the existing path. For example, the path is to a sequential file and is open for output, and a READ operation was requested.
System Action:
The request fails.
User Action:
Correct the request type or open a path of the desired type and retry the request.
Reason:
A request has been received by Dataset Services which access an existing path to a dataset, but the requested function cannot be performed due to a previous error on the path. For example, a WRITE operation was requested but an I/O error had occurred previously.
System Action:
The request fails.
User Action:
Close the path.
Reason:
A request has been received by Dataset Services which access an existing path to a dataset, but the requested function cannot be performed due to an abend in the I/O subtask during a previous request.
System Action:
The request fails.
User Action:
Close the path.
Reason:
A request has been received by Dataset Services that requires authorization from the NMDSSCHK exit. The call to the NMDSSCHK exit has failed. This could indicate the LOAD of the NMDSSCHK module failed, or the initialization of the exit failed, or the exit abended during processing.
System Action:
The request fails.
User Action:
See the SOLVE activity log for further messages about the failure. Message N16D16 should be present, containing a description of the error. If an abend occurred, the subtask that calls the exit should have taken a subtask dump - investigate the dump and determine why the exit failed.
Reason:
A request has been received by Dataset Services which requires authorisation from the NMDSSCHK exit. The call to the NMDSSCHK exit has resulted in a return code from the exit indicating that the request is not allowed.
System Action:
The request fails.
User Action:
Refer to the SOLVE activity log for further messages about the failure. If the exit returns a message indicating the reason for the failure, it will be logged as part of message N16D16.
Reason:
A request has been received by Dataset Services which requires authorization from the security system (for example, RACF). The security system has disallowed the request.
System Action:
The request fails.
User Action:
Check with your security administrator. There may be additional messages on the system log or system console that explain the failure.
Reason:
A request has been received by Dataset Services which is either not supported by the operating system on which SOLVE is executing (for example, Partitioned DataSet functions on VM operating system) or is not available in the environment in which SOLVE is executing (Systems Managed Storage not available in old versions of MVS).
System Action:
The request fails.
User Action:
None.
Reason:
A request has been received by Dataset Services which has resulted in an unexpected abend during processing of the request.
System Action:
The request fails.
User Action:
Contact your SOLVE support center.
Reason:
A request has been received by Dataset Services which has been cancelled due to termination of the requestor.
System Action:
The request is cancelled.
User Action:
None. This is normal for requests which were issued from NCL procedures. The request is cancelled if the procedure is flushed.
Reason:
A request has been received by Dataset Services which has failed due to a storage shortage.
System Action:
The request fails.
User Action:
Retry the request.
Reason:
A request has been received by Dataset Services which has been rejected because SOLVE is in shutdown. Dataset Services does not accept new requests during shutdown to enable active file processing to quiesce before shutdown completes.
System Action:
The request fails.
User Action:
None.
Reason:
This message indicates an unexpected abend has occurred in a Dataset Services request. It shows the Abend Code for the abend (aaaaaaaa), the Dataset Services Request Class (bbbbbbbb) for the request, and the Request Code (cc) which identifies the request being performed.
System Action:
This message and others relating to the abend are written to the activity log.
User Action:
Refer to the activity log for further information about the abend. Investigate the cause of the abend and, if the cause cannot be determined, contact Technical Support.
Reason:
This message indicates an unexpected abend has occurred in a Dataset Services request. It shows the Program Status Word (PSW) at the time of Abend, the Interrupt Code (IC) and the Instruction Length Code (ILC) at the time of abend.
System Action:
This message and others relating to the Abend are written to the SOLVE activity log.
User Action:
Refer to the SOLVE activity log for further information about the Abend. Investigate the cause of the Abend and if the cause cannot be determined contact your SOLVE support center.
Reason:
This message indicates an unexpected abend has occurred in a Dataset Services request. It shows the contents of some General Purpose Registers at the time of abend.
System Action:
This message and others relating to the Abend are written to the SOLVE activity log.
User Action:
Refer to the SOLVE activity log for further information about the Abend. Investigate the cause of the Abend and if the cause cannot be determined contact your SOLVE support center.
Reason:
This message indicates an unexpected abend has occurred in a Dataset Services request. It shows the addresses of various Dataset Services procesing modules at the time of abend. Each module and its address are shown in the format module name: address.
System Action:
This message and others relating to the Abend are written to the SOLVE activity log.
User Action:
Refer to the SOLVE activity log for further information about the Abend. Investigate the cause of the Abend and if the cause cannot be determined contact your SOLVE support center.
Reason:
This message indicates an unexpected abend has occurred in a Dataset Services request. It is the last message in a group which are written to the SOLVE actvity log when an abend has occurred in Dataset Services.
System Action:
This message and others relating to the Abend are written to the SOLVE activity log.
User Action:
Refer to the SOLVE activity log for further information about the Abend. Investigate the cause of the Abend and if the cause cannot be determined contact your SOLVE support center.
Reason:
This message indicates an I/O error has occurred in a Dataset Services request. It shows the text of a messages returned by the operating system to describe the I/O error.
System Action:
This message is written to the SOLVE activity log.
User Action:
Investigate the cause of the I/O error using the information supplied in the message which was returned from the operating system. Refer to the system log and job log for further messages related to the error.
Reason:
A request has been received by Dataset Services which requires authorisation from the NMDSSCHK exit. The call to the NMDSSCHK exit has failed or has returned a return code indicating that the request is not allowed. This message is logged along with any message returned by the exit to explain the failure.
System Action:
The request fails.
User Action:
Investigate the reason for the failure using the error text shown. If the text consists of a SOLVE error message, the help for the message will explain what the problem was.
Reason:
A request has been received by Dataset Services which requires authorisation from the NMDSSCHK exit. The LOAD of the exit module has failed with the return code aaaaaaaa.
System Action:
The request fails.
User Action:
Refer to the SOLVE job log for further messages about the failure. Check the SOLVE load library to ensure that the NMDSSCHK load module exists.
Reason:
A request has been received by Dataset Services which requires authorization from the NMDSSCHK exit. The initialization call made to the exit has received return code 8 (initialization failed) but no error message was returned from the exit.
System Action:
The request fails.
User Action:
Check the exit logic to find out why initialization failed. Check the SOLVE job log for any related error messages.
Reason:
A request has been received by Dataset Services which requires authorisation from the NMDSSCHK exit. The authorisation call made to the exit has received return code 4 (access denied) but no error message was returned from the exit.
System Action:
The request fails.
User Action:
Contact your system administrator to find out why you are not allowed to perform the function you requested.
Reason:
A request has been received by Dataset Services which requires authorisation from the NMDSSCHK exit. The call made to the exit has received a return code aaaaaaaa in R15 which is not valid for the request type.
System Action:
The request fails.
User Action:
Check the logic of the NMDSSCHK exit to find out why the invalid return code was returned.
Reason:
A request has been received by Dataset Services which requires authorisation from the NMDSSCHK exit. The call made to the exit has resulted in an ABEND. aaaaaaaa shows the abend code.
System Action:
The request fails.
User Action:
The abend should result in a subtask dump for the task which called NMDSSCHK. Investigate the dump to find the cause of the abend.
Reason:
A request has been received by Dataset Services which requires authorisation from the NMDSSCHK exit. The GETMAIN of storage used for the parameter list for the NMDSSCHK call has failed.
System Action:
The request fails.
User Action:
Investigate the reason for the storage shortage condition.
Reason:
Program 1 at line number 2 , column 4 , called Dataset Services with an MDO mapped by $DSCBD3Z, which is obsolete. The calling program should use $DSCBD3M instead. 3 is either ABS or REL, indicating that the line number is abolute or relative.
System Action:
The operation continues.
User Action:
Contact Technical Support, quoting the full text of the message.
Reason:
ROF signon to a remote SOLVE system failed because the user's USERID is not defined to the remote system.
System Action:
The remote signon is rejected.
User Action:
Contact your systems administrator, and, if required, define the USERID to the remote system.
Reason:
Issued to monitor status operators when successful ROF signon is completed by a user from another SOLVE system. The USERID (userid) origin (linkname) link name and user's name (username) are included in the message.
System Action:
None.
User Action:
None.
Reason:
Signifies successful completion of ROF signon to a remote system.
System Action:
None.
User Action:
None.
Reason:
Notifies monitor status operators that a ROF user has logged off.
System Action:
None.
User Action:
None.
Reason:
Notifies monitor status operators that user userid's ROF session has been terminated because the link to linkname has been lost.
System Action:
None.
User Action:
Attempt to re-establish the link to linkname if required.
Reason:
A user has attempted to establish a ROF session but the USERID defined at the remote system does not have operator authority, and therefore the ROF connection is not allowed.
System Action:
None.
User Action:
None.
Reason:
Notifies a user that re-establishment of a ROF connection that was disrupted earlier by a link failure will be attempted.
System Action:
Signon processing is scheduled at the remote SOLVE system.
User Action:
None.
Reason:
During establishment of a ROF connection, errors were detected when processing the NPF members associated with the USERID.
System Action:
None.
User Action:
Use the SHOW NPF and SHOW NPTAB commands (at the remote SOLVE system) to display the NPF tables in error. Have the tables corrected and sign on again to build the correct environment.
Reason:
Notifies a user that the ROF connection to remote SOLVE system linkname has been broken because the link to the remote system has been lost.
System Action:
The ROF connection is scheduled for re-establishment when the link becomes active again.
User Action:
None.
Reason:
ROF messages flowing from the nominated remote system were discarded before transmission from that system because the system NMIQLIM
System Action:
User Action:
Investigate why so many messages were issued. The default threshold is
Reason:
This message is issued during link activation and de-activation. It shows that the system is prepared to support ROF sessions (link active), or has ceased supporting ROF sessions (link inactive).
System Action:
None.
User Action:
None.
Reason:
A user waiting for recovery of a ROF connection to remote SOLVE system linkname, lost because the link to the remote system has been broken, is notified that the ROF connection will not be restarted because the link definition to the remote system has been reset.
System Action:
None.
User Action:
If the link to the remote system is re-defined, the user will have to sign on again if a new ROF connection is required.
Reason:
A user who had queued a signon request to a remote SOLVE system, pending activation of the link to that system is notified that the request has been cancelled because the link definition to the remote system has been reset.
System Action:
None.
User Action:
The signon must be attempted again once the link is re-defined.
Reason:
A SHOW command failed because the nominated module aaaa could not be loaded for execution. The reason may be determined from the reason code bbbb
System Action:
The command fails.
User Action:
Determine the reason for the failure to load. Ensure the module is in a library accessible to SOLVE.
Reason:
Issued in response to a SHOW BUFF command following message N17A35. Some SOLVE commands are processed by non-resident load modules which are loaded as required and retained in storage until the total amount of storage (of all retained load modules) exceeds the maximum (bbbbbK). When this occurs the oldest modules are deleted. The current storage total of retained modules is shown (aaaaaK).
System Action:
None.
User Action:
None, information only.
Reason:
Part of the SHOW BUFF display. The size of the SOLVE base module NM001 which is loaded by the operating system is given in K-bytes. The storage total of all other modules subsequently loaded by the base module is given in K-bytes. For OS and VM systems storage allocation is controlled by the operating system. In DOS and NIDOS systems the storage for each loaded module is obtained from within the SOLVE reserves which are within GETVIS.
System Action:
None, for information only.
User Action:
None, for information only.
Reason:
Part of the SHOW BUFF display. Displays the total number of kilobytes used for program modules below the 16M line.
System Action:
None.
User Action:
Load module storage use below the line may be reduced by specifying the INC or EXC startup parameters to select a subset of licensed components.
Reason:
Part of the SHOW BUFF display. Displays the total number of kilobytes used for program modules above the 16M line.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW NRD command. There are currently no messages held in the NRD retention list to display.
System Action:
None.
User Action:
None.
Reason:
This message is part of a SHOW NRD display. It gives the number of messages currently held on the NRD retention queue, and the maximum allowed at one time (set by SYSPARM NRDLIM).
System Action:
None.
User Action:
None.
Reason:
This message is part of a SHOW NRD display. It is a header for the subsequent display lines for individual held messages (see N17B04).
System Action:
None.
User Action:
None.
Reason:
This message is part of a SHOW NRD display. This line contains information and text of an individual held message. bd is the message id. date is the date the message was added to the NRD queue. time is the time the message was added to the NRD queue. nclid is the NCLID of the NCL procedure which added this message. mfav where the message is to be displayed: M=monitor screens, F=FTS screens, A=AOM screens, V=all OCS screens. text is the text of the message.
System Action:
None.
User Action:
None.
Reason:
No Mapped Data Services maps are currently loaded into memory.
System Action:
none.
User Action:
Enter Sysparms Mapload=mapname command to load a particular map into memory.
Reason:
Title message for SHOW MAPS command. For each map selected N17B07 will display the map name, status, time it was last loaded, and the current number of active connections for the map.
System Action:
None.
User Action:
None.
Reason:
Display for SHOW MAPS command. aaaaa = map name. ccccc = map status eeeee = map load time ggggg = map active connection count
System Action:
None.
User Action:
None.
Reason:
End message for a SHOW MAPS command. aaaa is the number of maps selected for display, and bbbbbb is the total storage used by the selected maps.
System Action:
None.
User Action:
None.
Reason:
An invalid value was specified for an operand of the SHOW MAP command.
System Action:
Command is rejected.
User Action:
Correct and retry.
Reason:
A SHOW command is incomplete because no other operands were specified.
System Action:
The command fails.
User Action:
Reenter the command with the appropriate operand(s).
Reason:
A SHOW command failed because the nominated module aaaaaaaa could not be loaded for execution. The reason may be determined from the reason code
bbbbbbbbbbbbbbbb
System Action:
The command fails.
User Action:
Determine the reason for the failure to load. Ensure the module is in a library accessible to SOLVE.
Reason:
A SHOW command failed because there was insufficient storage to load the processor module.
System Action:
The SHOW command is rejected.
User Action:
Contact your systems administrator who can determine if the storage shortage is temporary. Other messages may indicate that there is a storage shortage.
Reason:
The operand entered on the SHOW command is not valid under this operating system.
System Action:
The SHOW command is rejected.
User Action:
None.
Reason:
This message is the title line of a SHOW MSGQ display.
TYPE - The type of queues being reported, from the SHOW MSGQ operands:
- OCS
- OCS environments
- NCL
- NCL INTCMD environments
- BG - background processing environments
- SYS - various system queues
ENV - The specific environment.
- For a type of OCS, can be
OCS - an actual full-screen OCS environment
ROF - A remote operator
OPER - A signed on operating system console
LU1 - An LU1 OCS session
- For a type of NCL will only be NCL
- For a type of BG will be the background environment id, for example BSYS or LOGP.
- for a type of SYS, can be
LOG - the LOG/LOGPROC message queue
NRD - the NRD message rentention queue
AOM - the AOMPROC message queue(s) and DOM Queue.
CNM - the CNMPROC message queue
PPO - the PPOPROC message queue
UID/NAME - the userid or a region or name of a system queue.
LUNAME - the terminal (or '-' if not relevant) W - the window number (or '-')
NCLID - for NCL types, or secondary AOMPROCs, the NCLID, or '-'.
MSGS - the number of queued response or OCS messages
MEM/REQ - the number of OCS screen memory or NCL REQ msgs
QMPROC - the number of msgs queued to MSGPROC
LOST - flags if msgs have been lost at this time. (ie the queue is presently full and messages have been discarded. This indication gets reset when messages are read from the queue)
System Action:
None.
User Action:
None.
Reason:
This message is a detail line of a SHOW MSGQ display. Refer to message N17G01 for details.
System Action:
None.
User Action:
None.
Reason:
This message is the starting message of a SHOW COMMANDS display. It indicates the following output contains only commands that may be available to the indicated user.
System Action:
None.
User Action:
None.
Reason:
This message is the title line of a SHOW COMMANDS display.
COMMAND - The command name
AUTH - the command authority
OP-AUTH - the command operand authority, if it has one
NOTE - a note indicating equate or cmdrepl status
EQUATE TEXT - the equate text, if relevant.
System Action:
None.
User Action:
None.
Reason:
This message is a detail line of a SHOW COMMANDS display. Refer to message N17G11 for details.
System Action:
None.
User Action:
None.
Reason:
This is the title line of a SHOW SYSCONS display.
con-name the console logical or terminal name (shown as LUNAME in SHOW USERS display).
key-uid the userid used as the logical key when incoming commands are processed. Used to detect when an operating system console has had a new RACF signon.
act-uid the actual userid that the console has been signed on to SOLVE under.
con-id the console id. Either a 2-digit decimal number (00 to 99) or 8 hexadecimal digits (being the extended 4-byte console id).
uid-1, the userids used during signon processing to establish the
uid-2, actual signed on userid.
uid-3
System Action:
None.
User Action:
None.
Reason:
This message supplies the details for each operating system console. Refer to N17J01 for a description of the contents of the fields in this message.
System Action:
None.
User Action:
None.
Reason:
This is the first message produced as a response to the SHOW TIMEZONE command. It shows the system time zone offset (As set by the TZ JCL parameter, or as derived from the hardware clock and local time)
If the JCL parm TZ=GMT is in effect, this is indicated by TZ=GMT.
System Action:
None.
User Action:
None.
Reason:
This is the second message produced as a response to the SHOW TIMEZONE command. It provides column headings for the N178K03 messages that follow. The columns are time zone name, GMT or UTC offset, and the description provided on the TIMEZONE ADD command.
System Action:
None.
User Action:
None.
Reason:
This is the third message produced as a response to the SHOW TIMEZONE command. It displays the time zone names and offsets as set by the TIMEZONE command. Refer to message N17K02 for column descriptions.
System Action:
None.
User Action:
None.
Reason:
Response messages from the SHOW ASINFO command follow.
System Action:
None.
User Action:
None.
Reason:
This message displays the first header line for the SHOW ASINFO command. The column headings relate to the N17L15 message.
Is the address space ID (in hexadecimal).
Is the job name.
Is the step name.
Is the procedure step name.
Is the job type:
Indicates a JES2 job.
Indicates an OpenMVS transaction.
Indicates a start task.
Indicates a TSO user.
Is the job step program name.
Is the JES job ID.
Is the owning subsystem name (such as JES2).
System Action:
None.
User Action:
None.
Reason:
This is the second header message from the SHOW ASINFO message.
The column headings relate to the N17L16 message.
The column headings are:
A ddname used in the job step
A dsname associated with this ddname
a member name associated with the ddname
for concatenated datasets, the concatenation number.
System Action:
None.
User Action:
None.
Reason:
This is the third header message from the SHOW ASINFO message.
The column headings relate to the N17L17 message.
The column headings are:
The parm for the jobstep program
System Action:
None.
User Action:
None.
Reason:
This is the first informational message from SHOW ASINFO message.
For column information, refer to the N17L10 message.
System Action:
None.
User Action:
None.
Reason:
This is the second informational message from SHOW ASINFO message.
For column information, refer to the N17L16 message.
System Action:
None.
User Action:
None.
Reason:
This is the third informational message from SHOW ASINFO message.
For column information, refer to the N17L12 message.
System Action:
None.
User Action:
None.
Reason:
This message is produced in response to the SHOW ASINFO command, if the command is not supported on the current operating system.
System Action:
The command is terminated.
User Action:
None.
Reason:
This message is produced in response to the SHOW ASINFO command, if the command is issued on a region that is not APF authorized.
System Action:
The command is terminated.
User Action:
None.
Reason:
This message is produced in response to the SHOW ASINFO command, if the command could not be processed due to a storage shortage.
System Action:
The command is terminated.
User Action:
None.
Reason:
This message is produced in response to the SHOW ASINFO command, if an ABEND was encountered during processing.
Abend information is displayed.
System Action:
The command is terminated.
User Action:
Contact your support representative.
Reason:
Statistics for the System procedure loader follow. This is output of the SHOW SYSLOAD command.
System Action:
none.
User Action:
none.
Reason:
Statistics for the system procedure loader follow. This is a heading line.
System Action:
none.
User Action:
none.
Reason:
This is a system loader stats line. The name is self-explanatory.
System Action:
none.
User Action:
none.
Reason:
During system initialization the VTAM message module, which is used to initialize the DEFMSG summary table, was found to have invalid non numeric entries. This module is required to be correct for NPF initialization.
System Action:
NPF message delivery is disabled. This message will be followed by N18003.
User Action:
This could signify a VTAM internal problem.
Reason:
During system initialization the VTAM message module modname (ISTCFCMM or its equivalent) could not be loaded. This module is required for NPF initialization. If n is 0 then the failure occurred on a BLDL macro.
aaaa shows the return code and bbbb is the reason code. If n is 1 then the failure occurred on a LOAD or LINK macro. aaaa shows the reason code and bbbb is the abend code.
System Action:
NPF for message delivery is disabled. This means that any users logging on to the system who is authorized to receive unsolicited (PPO) messages will receive ALL such messages whether or not their USERIDS specify NPF message control.
User Action:
Determine the cause of load failure and restart the NetMaster region.
Reason:
An error has occurred during initialization processing for the Network Partitioning Facility. An accompanying message on the activity log will indicate the reason for the failure.
System Action:
NPF for message delivery is disabled. This means that any users logging on to the system who is authorized to receive unsolicited (PPO) messages will receive ALL such messages whether or not their USERIDS specify NPF message control.
User Action:
Determine the cause of the failure and restart the NetMaster region.
Reason:
During a user's LOGON processing the NPF RESOURCE control member xxxx defined in the user's UAMS record could not be located on the NPF dataset.
System Action:
The logon is allowed but the user will have no NPF resource access.
User Action:
Refer to the systems administrator for correction of the problem.
Reason:
During a user's logon processing an I/O error occurred while reading the NPF member mbrname. NPF processing continues but the user's access to network resources may be restricted, partially or completely.
System Action:
None.
User Action:
Refer the error to your systems administrator.
Reason:
During a user's logon processing a syntax error was detected while processing control member aaaaaaaa. The sequence number of the record in error is bbbbbbbb, extracted from bytes 73-80 of the record.
System Action:
Processing continues.
User Action:
Correct the syntax error and logon again.
Reason:
Processing of a user's NPF authorisation terminated because the system NPF dataset referenced by the NPTABLES DD statement could not be opened.
System Action:
None.
User Action:
Refer the error to your systems administrator. Access to network resources will be prohibited.
Reason:
During a user's logon processing the NPF RESOURCE table member mbrname, referred to by the user's NPF RESOURCE control member, could not be found.
System Action:
Processing continues. Access to network resources may be restricted.
User Action:
Refer to your systems administrator.
Reason:
During a user's logon processing an I/O error occurred attempting to read the NPF resource table member mbrname.
System Action:
Processing continues. Access to network resources may be restricted.
User Action:
Refer to your systems administrator.
Reason:
During a user's logon processing a syntax error was detected in record sequence number bbbbbbbbb of NPF resource table member mbrname.
System Action:
Processing continues at the next record. Access to network resources may be restricted.
User Action:
Refer to your systems administrator for correction of the problem.
Reason:
A SHOW LOCKS or SHOW NCLLOCKS command was issued but no locks are held.
System Action:
None
User Action:
None
Reason:
A SHOW LOCKS or SHOW NCLLOCKS command has an invalid operand ( P1 ).
System Action:
The command fails.
User Action:
Correct and retry.
Reason:
The title line for the SHOW LOCKS or SHOW NCLLOCKS display; shows the class of locks ( P1 ). Lock classes are:
NCL - NCL programs
SYS - Internal system resources
EDIT - Panel Services (panel edit)
System Action:
None
User Action:
None; for more information on lock classes refer to the SHOW LOCKS or SHOW NCLLOCKS command description.
Reason:
The information line of the SHOW LOCKS or SHOW NCLLOCKS display; indicates the lock level ( P1 , PRIMARY, or MINOR) and the lock name ( P2 ).
System Action:
None
User Action:
None
Reason:
This message is the title line of the lock detail section of the SHOW LOCKS or SHOW NCLLOCKS display.
System Action:
None
User Action:
None
Reason:
The lock detail display for a specific primary or minor lock. It shows:
P1 is the unique lock number
P2 indicates how the lock is held (shared or exclusive)
P3 is the text associated with the lock
P4 is the minor lock name (if any)
System Action:
None
User Action:
None
Reason:
A SHOW LOCKS or SHOW NCLLOCKS command contains a wrong or duplicated operand ( P1 ).
System Action:
The command fails.
User Action:
Correct and retry.
Reason:
The title line of the LIST=WAIT display for SHOW LOCKS or SHOW NCLLOCKS; shows the minor lock name ( P1 ) if any.
System Action:
None
User Action:
None
Reason:
This message is the heading line for part of the SHOW LOCKS or SHOW NCLLOCKS display. It is followed by a list of lock requests which have SHR access to a resource and have requested that the lock ownership be changed to EXCL.
System Action:
None
User Action:
None
Reason:
This message is a heading line for the SHOW NCLLOCKS display. It provides column headings for message N18713.
System Action:
None
User Action:
None
Reason:
This message is a heading line for the SHOW NCLLOCKS display. It provides column headings for message N18714.
System Action:
None
User Action:
None
Reason:
This message is a detail line for the SHOW NCLLOCKS display. The fields displayed are:
P1 is the NCLID of the process that holds the lock.
P2 is the name of the NCL procedure that took out the lock. Note that this need not be the active NCL procedure.
P3 is the user ID associated with the process.
P4 is the lock request type, shared (SHR) or exclusive (EXCL).
P5 is text associated with the lock.
P6 is the minor lock name if any.
System Action:
None
User Action:
None
Reason:
This message is a detail line for the SHOW NCLLOCKS display. The fields displayed are:
P1 is the unique lock number.
P2 is the lock level, PRIMARY or MINOR.
P3 is the lock resource name.
System Action:
None
User Action:
None
Reason:
The title line of the SHOW DOMAINS display. This message provides column headings for message N18722.
System Action:
None
User Action:
None
Reason:
The detail line of a SHOW DOMAINS display. The fields displayed are:
P1 represents the remote system domain ID (as specified by the NMDID initialization parameter for the remote system).
P2 is the linkname of the INMC link to the remote system.
P3 is the system identifier of the remote system.
P4 is the network name of the remote system.
P5 is the VTAM version and release level in the remote system, or, if the remote system is a Tandem system, the system node name.
P6 is the version and release level of the Management Services component of the remote NetMaster system.
P7 is the remote system operating system type.
P8 is the status of this NetMaster system's knowledge of the remote system domain information, as follows: Complete indicates that the information displayed is current. Incomplete indicates that the information displayed is the latest known.
System Action:
None
User Action:
None
Reason:
The second title line of the SHOW DOMAINS display. This message provides column headings for message N18724.
System Action:
None
User Action:
None
Reason:
The second detail line of a SHOW DOMAINS display; the fields displayed are:
P1 represents the remote system Management Services level.
P2 is the jobname of the remote system.
P3 is the operating system version of the remote system.
P4 is the operating system system name of the remote system.
P5 is the VTAM generic resource name of the remote system, if used.
System Action:
None
User Action:
None
Reason:
The title line of the SHOW DOMAINS TYPE=DEFINED display. This is followed by messages N18726 and N18727 which contain details about each domain.
System Action:
None.
User Action:
None.
Reason:
This is the detail line of the SHOW DOMAINS TYPE=DEFINED display. The fields displayed match the heading message N18725. The information is as follows:
Is the domain name
Indicates how the domain is defined:
Indicate if the domain may be accessed using the access method for that column, that is, VTAM, IP, EPS, and XNF. The columns display the following values:
If the IP access method is YES, there will be an additional message, N18727, which contains TCP/IP addressing information.
Indicates whether the domain can be contacted with the INMC access method. This access method is relevant to APPC links only. It uses an INMC link (with some other access method) as a transport method for APPC sessions.
System Action:
None.
User Action:
None.
Reason:
This is a detail line of the SHOW DOMAINS TYPE=DEFINED display. It is issued if the preceeding N18726 message indicated that the TCPIP access method is supported for connections to this domain. In this message:
P1 is domain name
P2 is the Port number that the (remote) system will use to receive inbound connections
P3 and P4 show the connection details specified when the domain was defined and will be either: NAME and an internet host name, or, ADDR and an IP Address
System Action:
None.
User Action:
None.
Reason:
A SHOW DOMAINS TYPE=DEFINED display was requested but there are no domains defined which match the specified criteria.
System Action:
None.
User Action:
None.
Reason:
This is a detail line of the SHOW DOMAINS TYPE=DEFINED display. It is issued if the preceding N18726 message indicates that the TCP/IP access method is supported for connections to this domain. In this message:
P1 is domain name.
P2 is the port number that the (remote) system uses to receive inbound connections.
P3 and P4 show the connection details of the proxy server and can be one of the following:
System Action:
None.
User Action:
None.
Reason:
A request for dynamic allocation that required a volume to be mounted was cancelled by the system operator.
System Action:
The allocation attempt is abandoned.
User Action:
Determine why the operator cancelled the request.
Reason:
An ALLOCATE command has been successfully issued. The ddname is dddddddd.
System Action:
None.
User Action:
None.
Reason:
A syntactically correct ALLOCATE command failed for the above reason. The SMS REASON CODE is only displayed if the error was related to a Systems Managed Storage error.
System Action:
None.
User Action:
You may use the $DAIR NCL procedure supplied with the system to determine the reason for the dynamic allocation interface return code. If an SMS error occurred, look up the reason code in the appropriate SMS documentation.
Reason:
Requests for dynamic allocation are performed by a subtask. This subtask has failed.
System Action:
The request is rejected.
User Action:
Refer this problem to your systems administrator for correction.
Reason:
An ALLOCATE command was issued specifying the CONCAT operand. The allocation was successful, but concatenation to the specified ddname
ddname2 has failed.
System Action:
The dataset is allocated to ddname1, but not concatenated to ddname2.
User Action:
Use the $DAIR NCL procedure to determine the reason for the failure using the dair code cccc.
Reason:
The installation defined dataset authorisation exit could not be loaded.
System Action:
No allocation is performed.
User Action:
Determine the cause of the failure and retry.
Reason:
The requested UNALLOC command has been successfully processed.
System Action:
None.
User Action:
None.
Reason:
A syntactically correct UNALLOC command failed for the above reason.
System Action:
None.
User Action:
Use the $DAIR NCL procedure to determine the reason for the failure.
Reason:
Requests for unallocation are performed by a subtask. This subtask has failed.
System Action:
The request fails.
User Action:
Refer this problem to your systems administrator for correction.
Reason:
An OPNDST was rejected because of a storage shortage.
System Action:
The command is rejected.
User Action:
Retry the command. Increase job region or partition size if the problem persists.
Reason:
An OPNDST was issued for a terminal already connected.
System Action:
The command is rejected.
User Action:
None.
Reason:
An OPNDST is already in progress for the specified LU.
System Action:
The command is rejected.
User Action:
None.
Reason:
An OPNDST command specified an LU name not defined to VTAM, or one that VTAM cannot establish contact with. If the resource is in another domain there may not be a cross domain resource definition available or active.
System Action:
The command is rejected.
User Action:
Correct and re-enter.
Reason:
An OPNDST command failed.
System Action:
The command is rejected.
User Action:
Refer the error to your systems administrator. The error codes included in the message are explained in the appropriate VTAM Programming manual.
Reason:
An OPNDST command was issued to connect terminal luname, but this device is already in session with a different application.
System Action:
The command is rejected.
User Action:
Retry the command later if required.
Reason:
An OPNDST command has specified an invalid logmode in the LOGMODE=logmode operand.
System Action:
The command is rejected.
User Action:
Correct the logmode name and retry.
Reason:
An OPNDST command was entered to acquire an LU. SOLVE currently has a queued logon request for the LU due to a prior OPNDST command, and the LU has still not been connected. The CLSDST command has been used to cancel the pending logon request. SOLVE cannot issue another request to VTAM to acquire the terminal until the previous request completes.
System Action:
The OPNDST command is rejected.
User Action:
Investigate why the LU has not been connected to SOLVE. It is most likely to be in use by another application program.
Reason:
An &MSGREAD, &MSGDEL, &MSGCONT or &MSGREPL verb can only be issued by a procedure operating as a MSGPROC for an OCS window.
System Action:
The NCL procedure is flushed.
User Action:
Correct the NCL procedure.
Reason:
An MDS error occurred while trying to assign replacement message text during an INTREPL operation. xx and yy indicate the MDS return code and feedback information.
System Action:
The procedure is terminated.
User Action:
Return code and feedback values for MDS are explained in the NCL REFERENCE for the &ZMDSRC and &ZMDSFDBK system variables. Use this information to determine why MDS assignment failed for $MSG.TEXT.
Reason:
This message is logged when an invalid function code is passed to the system logger interface record reformatter.
System Action:
The request is rejected.
User Action:
Contact your local SOLVE support office.
Reason:
This message is logged when an invalid format code is passed to the system logger interface record reformatter.
System Action:
The request is rejected.
User Action:
Contact your local SOLVE support office.
Reason:
This message is logged when a reformatted record overflows the output area during processing by the system logger interface record reformatter.
System Action:
The request is rejected.
User Action:
Contact your local SOLVE support office.
Reason:
This message is logged when the system logger interface record refirnatter encounters an invalid OPERLOG record. In this case, the MDB header is invalid.
The record is dumped to the SOLVE log (see message N19T90).
System Action:
The request is rejected.
User Action:
Contact your local SOLVE support office.
Reason:
This message is logged when the system logger interface record refirnatter encounters an invalid OPERLOG record. In this case, an invalid or unrecognised MDB segment was found. The offset is displayed.
The record is dumped to the SOLVE log (see message N19T90).
System Action:
The request is rejected.
User Action:
Contact your local SOLVE support office.
Reason:
This message is logged when the system logger interface record refirnatter encounters an invalid OPERLOG record. In this case, the MDB total length does not match the sum of the segment lengths.
The record is dumped to the SOLVE log (see message N19T90).
System Action:
The request is rejected.
User Action:
Contact your local SOLVE support office.
Reason:
This message is logged when the system logger interface record reformatter encounters an invalid OPERLOG record. In this case, the MDB segments are not in the correct sequence.
The record is dumped to the SOLVE log (see message N19T90).
System Action:
The request is rejected.
User Action:
Contact your local SOLVE support office.
Reason:
This message is logged when the system logger interface record reformatter encounters an invalid record. It provides a hex dump of the record in error.
System Action:
None
User Action:
Refer to the previous N19Txx message for details of the error.
Reason:
This message is returned (in the &SYSMSG variable) when a record reformat error occurs on a DSS_LOGGER READ OML verb.
Preceding records on the SOLVE log describe the error.
System Action:
The request is rejected. The return code is set to 32, the feedback code to 0.
User Action:
Contact your local SOLVE support office.
Reason:
An attempt to reference a non-existent HFS file was made. The pathname was path.
System Action:
The request fails.
User Action:
Reissue the request with a valid path.
Reason:
An attempt was made to perform an HFS directory operation on pathname
path. However, path is not a directory.
System Action:
The request fails.
User Action:
Reissue the request with a path that represents an HFS directory.
Reason:
An attempt was made to seek to a position before the start of an HFS file.
System Action:
The request fails.
User Action:
This is an internal error. Call your support representative.
Reason:
When processing a call to convert an MDO to a DSECT, a field was encountered that required classification. This was not possible because more than one class specification was encountered in the MDO.
System Action:
The request fails.
User Action:
This is an internal error. Call your support representative.
Reason:
A required operand was omitted on a call to convert an MDO to a DSECT or vice versa. The MDO key being processed was key.
System Action:
The request fails.
User Action:
This is an internal error. Call your support representative.
Reason:
An operand that was not allowed was supplied on a call to convert an MDO to a DSECT or vice versa. The MDO key being processed was key.
System Action:
The request fails.
User Action:
This is an internal error. Call your support representative.
Reason:
An invalid operand was supplied on a call to convert an MDO to a DSECT or vice versa. The MDO key being processed was key.
System Action:
The request fails.
User Action:
This is an internal error. Call your support representative.
Reason:
A Unix System Services call issued by Dataset Services failed with a return code of rrrr and reason code of cccc-cccc when trying to initialize the environment for an HFS call.
System Action:
The request fails.
User Action:
Refer to "Unix System Services Messages and Codes" for the relevant return code and reason code.
Reason:
A Unix System Services call issued by NetMaster Dataset Services to process an HFS file failed with a return code of rrrr and reason code of cccc-cccc.
System Action:
The request fails.
User Action:
HFS file errors may have a variety of environmental causes. A common one is when the HFS file system is not mounted. Other possibilities include:
File permission error.
The NetMaster started task UID does not have the required authority to access the file
File does not exist.
The path name may be wrong, or the file may have been deleted
No such device exists.
Not enough space is available.
No space is left on the device, or no space is available to create the IPC member ID.
Not a directory.
HFS encountered a system error.
Ensure that the HFS file system has been defined with sufficient space and is correctly and permanently mounted. Ensure that NetMaster features such as ReportCenter have been installed with the name of a correct and available file system.
File permissions are a frequent cause of HFS file errors.
Verify that the OMVS UID attempting the file operation has sufficient authority to do so. In general, all distributed HFS product files should allow at least read access to all users. Refer to the specific product installation and user manuals for additional file permission requirements for their specific working data.
A complete list of HFS reason codes is available in the IBM publication z/OS UNIX System Services Messages and Codes for your operating system level.
Additional information about z/OS HFS implementation is available from the IBM Redbook publication Hierarchical File System Usage Guide.
Reason:
Process extension storage is required to perform a CCI INIT request and is not obtainable because the region is low on storage.
System Action:
The CCI interface is not usable.
User Action:
Contact your Systems Programmer for assistance. If no problems are detected, contact Technical Support.
Reason:
An attempt was made to perform a CCI function before CCI INIT initializes the CCI interface.
System Action:
The CCI request fails.
User Action:
Correct the procedure logic so that CCI INIT is performed before other functions are requested.
Reason:
The SOAP subtask has abended. This will be preceeded by messages N15Z20 and N15Z21 detailing the abend details.
System Action:
If the subtask was currently processing a SOAP verb work request, that request will be terminated with &SYS.RETCODE=8 and &SYS.FDBK=8. This message will be followed by either N1S402 or N1S404.
User Action:
Report the abend to Technical Support. Refer to the following N1S402 or N1S404 messages.
Reason:
The SOAP subtask has just abended as noted by the preceeding message N1S401. The SOAP subtask has been reactivated.
System Action:
Subsequent work requests will be processed as normal. To prevent a potential subtask abend loop, only 2 subtask reactivations are allowed. A third abend will cause message N1S404 to be issued instead of N1S402.
User Action:
No action required.
Reason:
An attempt to shutdown the SOAP subtask was unsuccessful. The SOAP subtask did not terminate gracefully within 5 seconds. The system has forcibly detached the subtask. This can occur if the subtask is still busy processing a SOAP service call.
System Action:
After forcibly detaching the subtask, the SOAP interface is disabled.
User Action:
A forced detach should only occur at region shutdown. From a NetMaster point of view, this message is informational use only. The SOAP interface may report errors due to the fact that the subtask is being removed whilst a SOAP call is in progress.
Reason:
The SOAP subtask has just abended as noted by the preceeding message N1S401. The number of abends allowed for the SOAP subtask has been exceeded. This number is set to 2 - the third abend during the region lifetime or since the last SOAP USD FUNCTION=RESET call will cause this message. The SOAP interface is now disabled.
System Action:
Any subsequent SOAP verb call requests will be terminated with &SYS.RETCODE=8 and &SYS.FDBK=12. This will also apply to any SOAP requests already received but still queued for SOAP service processing.
User Action:
To reestablish the SOAP subtask interface, either recycle NetMaster or execute the OML verb 'SOAP USD FUNCTION="RESET"'.
Reason:
The SOAP subtask has just been activated and is now fully active. The SOAP subtask is activated by one of the following reasons:
1. After the receipt of the very first SOAP verb call for this region. 2. After an abend and subtask reactivation i.e. after N1S401 and N1S402. 3. After an unrecoverable abend (message N1S404) and RESET call issued.
System Action:
The SOAP subtask processes SOAP verb calls as normal.
User Action:
None.
Reason:
The SOLVE UNIX interface is not available until the initial call to UNIX System Services is completed. This message is issued every 30 seconds until completion.
System Action:
SOLVE UNIX support is unavailable until the initial call is completed. SOLVE initialization continues.
User Action:
None.
Reason:
The subtask to initialize communications with UNIX System Services has ABENDed.
System Action:
SOLVE UNIX support is reset. SOLVE initialization continues.
User Action:
Contact Technical Support.
Reason:
The subtask that issued the initial call to UNIX System Services was FORCE DETACHed.
System Action:
UNIX support is reset. Region initialization continues.
User Action:
Contact Technical Support.
Reason:
The release of OS/390 that you are running supports UNIX System Services but the first call made by the SOLVE system failed.
System Action:
SOLVE UNIX support is reset. SOLVE initialization continues.
User Action:
UNIX Systems Services may not be configured correctly in OS/390. Consult your systems programmer. For details of the reason code, see the UNIX System Services Messages and Codes manual.
Reason:
The SOLVE UNIX SHELL interface was unable to initialize and is not available for use. The reason for this was given in an earlier N1UYnn message.
System Action:
SOLVE UNIX support is reset. SOLVE initialization continues.
User Action:
See the N1UYnn message issued earlier.
| Copyright © 2012 CA. All rights reserved. |
|