|
|
|
Reason:
This message is issued in response to the TCPIP START command if an attempt to use the IUCV interface is made in an environment that does not support it.
System Action:
The TCPIP START command fails.
User Action:
Determine the correct interface type for the current operating system and environment. Issue another TCPIP START command using the TYPE=tttt operand with the correct type specified.
Reason:
This message is issued in response to a TCPIP START command when the IUCV interface to TCP/IP is unable to initialize. A reason number and description are provided. The reasons are listed below:
1 - NO STORAGE FOR GLOBAL CONTROL BLOCKS
The interface was unable to obtain required storage.
2 - NO STORAGE FOR LOCAL CONTROL BLOCKS
The interface was unable to obtain required storage.
3 - LOAD FAILED FOR INTERFACE MODULE nnnnnnn
The interface was unable to load a required module. If the module name is EZASOK03, it probably indicates that IBM TCP/IP V3.1 is not installed on this system. Other names generally indicate that the required IBM C runtime libraries are not installed.
4 - UNABLE TO OBTAIN IUCV PC NUMBERS
The interface was unable to locate required control blocks etcetera to obtain required information.
5 - UNRECOGNISED OPTION: ooooooooo
The TCPIP START commands OPTIONS operand had keywords specified that are not recognized by the IUCV interface.
6 - DUPLICATE OPTION: ooooooo
The named TCPIP START OPTIONS operand was duplicated.
7 - PREFIX OPTION INVALID: oooooo
The 'PREFIX' TCPIP START option is not valid.
8 - NODE OPTION INVALID: oooooo
The 'NODE' TCPIP START option is not valid.
10 - LOAD FAILED FOR modname
The interface was unable to load a required module.
21 - IUCVMINI FAILED, R15=rrr return code is displayed. The most likely reason is that the IUCV address space is not active.
22 - IUCVMCOM CONNECT FAILED, R15=rrr TARGET JOBNAME: jjjjj
An attempt to connect to the TCP/IP region using IUCV failed. The most likely reason is that the target jobname is not active.
23 - IUCV CONNECT REQUEST WAS SEVERED, REASON rrrrr
The IUCV CONNECT request was refused for the displayed reason.
24 - IUCV INITIAL SEND ERROR, R15=rrr
The IUCV initial send failed. The return code is displayed.
30 - IUCV GETHOSTADDR FAILED (1), r15=rrr
An attempt to obtain the local host IP address failed. The return code is displayed.
31 - IUCV GETHOSTADDR FAILED (2), r15=rrr
An attempt to obtain the local host IP address failed. The return code is displayed.
35 - IUCV GETHOSTNAME FAILED (1), r15=rrr
An attempt to obtain the local host domain name failed. The return code is displayed.
36 - IUCV GETHOSTNAME FAILED (2), r15=rrr
An attempt to obtain the local host domain name failed. The return code is displayed.
37 - IUCV GETHOSTNAME FAILED (3), NAME BLANK
An attempt to obtain the local host domain name failed. The returned name is blank.
100 - DDNAME dddddd IS ALLOCATED DUMMY
The SYSTCPD ddname is allocated as DD DUMMY, preventing the interface from obtaining necessary information from the TCPIP.DATA dataset.
101 - DATASET dsname ALLOC SHR FAILED, IN USE as it is in exclusive use by another user or job.
102 - DATASET dsname ALLOC SHR FAILED, CODE aaaa-bbbb
The named TCPIP.DATA dataset could not be allocated DISP=SHR, as a SYNALLOC failure occurred. The DYNALLOC error and info codes are displayed.
110 - RDJFCB FAILED for ddddd R15=rrr
A RDJFCB macro failed for the indicated (TCPIP.DATA) ddname.
111 - OPEN FAILED FOR dsname
The indicated (TCPIP.DATA) dataset could not be opened.
112 - OPEN ABENDED FOR dsname CODE: abcode
The indicated (TCPIP.DATA) dataset could not be opened, as an ABEND occurred.
113 - dsname INVALID RECFM OR LRECL
The indicated (TCPIP.DATA) dataset could not be used, as it had an invalid record format (not F, FB, V, VB) or record length (F up to 255, V from 4 to 259).
119 - I/O ERROR READOING dsname INFO: synmsg
The indicated (TCPIP.DATA) dataset had an I/O error during processing. The MVS SYNAD error message text is displayed.
120 - TCP DATA FILE STMT ERROR: text
The indicated source line in the TCPIP.DATA file had an error, related to the TCPIPUSERID statement.
121 - TCP DATA FILE STMT ERROR: text
The indicated source line in the TCPIP.DATA file had an error, related to the DOMAINORIGIN statement.
122 - TCP DATA FILE STMT ERROR: text
The indicated source line in the TCPIP.DATA file had an error, related to the DATASETPREFIX statement.
123 - TCP DATA FILE STMT ERROR: text related to the HOSTNAME statement.
System Action:
TCP/IP initialization fails. Depending on the error, it may be automatically retried in 30 seconds.
User Action:
If the error is permanent (no retry), then correct the problem and issue another TCPIP START command.
If the error is temporary (retry will occur), then attempt to correct the problem so that the retry will succeed.
Reason:
This message is issued in response to a SHOW TCPIP command when the IUCV interface is in use in MVS. It shows the TCP/IP region jobname, TCP/IP node name, and TCPIP.DATA dataset name.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW TCPIP command when the IUCV interface is in use in VM. It shows the TCP/IP virtual machine userid.
System Action:
None.
User Action:
None.
Reason:
This message is issued to the SOLVE log when the TCP/IP IUCV interface has certain errors
System Action:
None.
User Action:
Refer any message to the product support engineer.
Reason:
This message is issued when the IUCV interface subtask has an initialization failure. The reasons are listed below and descriptions are provided.
The interface was unable to obtain required storage.
An attempt to initialize the macro interface failed. The target TCP/IP job is shown, with the return code and error number.
System Action:
If this error occurs during TCPIP START processing, initialization fails. If it occurs later, an individual SOCKET verb fails.
User Action:
Examine the error information and determine whether the correct jobname is used.
You may need to contact Technical Support.
Reason:
This message is issued to the SOLVE log when the TCP/IP IUCV interface receives an IUCV SEVER. The sever reason is displayed.
SEVER reasons are documented in the IBM TCP/IP application programming reference (SC31-7187) chapter 8, section 8.7.1.2.
The most common reason is 'KILL -38' which indicates that TCP/IP is being shut down.
System Action:
The TCP/IP interface will automatically stop.
User Action:
Determine the reason that the IUCV SEVER was issued and take appropriate corrective action.
Reason:
This message is issued in response to the TCPIP START command if an attempt to use the HPNS interface is made in an environment that does not support it.
System Action:
The TCPIP START command fails.
User Action:
Determine the correct interface type for the current operating system and environment. Issue another TCPIP START command using the TYPE=tttt operand with the correct type specified.
Reason:
This message is issued in response to a TCPIP START command when the HPNS interface to TCP/IP is unable to initialize because of one of the following reasons:
The interface was unable to obtain required storage.
The interface was unable to obtain required storage.
The interface was unable to load a required module. If the module name is EZASOH03, it probably indicates that IBM TCP/IP V3.2 is not installed on this system. Other names generally indicate that the required IBM C runtime libraries are not installed.
The interface was unable to locate the control blocks to obtain the required information.
The OPTIONS operand of the TCPIP START command specified keywords that are not recognized by the IUCV interface.
The named OPTIONS operand of the TCPIP START command was duplicated.
The PREFIX option of the TCPIP START command is not valid.
The NODE option of the TCPIP START command is not valid.
The PATH option of the TCPIP START command is not valid.
The interface was unable to load a required module.
The JOB option of the TCPIP START command is not valid.
The HOST option of the TCPIP START command is not valid.
The DOMAIN option of the TCPIP START command is not valid.
The DATADD option of the TCPIP START command is not valid.
The DATADSN option of the TCPIP START command is not valid.
An attempt to establish a connection to TCP/IP failed. The return code is displayed. The most likely reason is that the target TCP/IP address space is not active.
An attempt to create a socket failed. The return code is displayed.
An attempt to create a socket failed. The return code is displayed.
An attempt to create an AF_INET6 socket failed. The system has not been configured for AF_INET6 sockets to be created.
An attempt to destroy a socket failed. The return code is displayed.
An attempt to destroy a socket failed. The return code is displayed.
An attempt to obtain the local host IP address failed. The return code is displayed.
An attempt to obtain the local host IP address failed. The return code is displayed.
An attempt to obtain the local host domain name failed. The return code is displayed.
An attempt to obtain the local host domain name failed. The return code is displayed.
An attempt to obtain the local host domain name failed. The returned name is blank.
The SYSTCPD ddname is allocated as DD DUMMY, preventing the interface from obtaining necessary information from the TCPIP.DATA data set.
The indicated TCPIP.DATA data set could not be allocated DISP=SHR because it is in exclusive use by another user or job.
The indicated TCPIP.DATA data set could not be allocated DISP=SHR because a DYNALLOC failure occurred. The DYNALLOC error and information reason codes are displayed.
The indicated TCPIP.DATA data set could not be allocated DISP=SHR because the name is invalid or the data set could not be located.
A RDJFCB macro failed for the indicated TCPIP.DATA ddname.
The indicated TCPIP.DATA data set could not be opened.
The indicated TCPIP.DATA data set could not be opened because an ABEND occurred.
The indicated TCPIP.DATA data set could not be used because it had an invalid record format (not F, FB, V, or VB) or record length (F up to 255 and V from 4 to 259).
The indicated TCPIP.DATA data set had an I/O error during processing. The MVS SYNAD error message text is displayed.
The indicated source line in the TCPIP.DATA file had an error related to the TCPIPUSERID or TCPIPJOBNAME statement.
The indicated source line in the TCPIP.DATA file had an error related to the DOMAINORIGIN statement.
The indicated source line in the TCPIP.DATA file had an error related to the DATASETPREFIX statement.
The indicated source line in the TCPIP.DATA file had an error related to the HOSTNAME statement.
The indicated TCPIP.DATA file could not be allocated because the path name is invalid or the file could not be located.
The indicated TCPIP.DATA file could not be allocated because a DYNALLOC failure occurred. The DYNALLOC error and information reason codes are displayed.
The path name of an allocated TCPIP.DATA file could not be obtained because a DYNALLOC failure occurred. The DYNALLOC error and information reason codes are displayed.
System Action:
Initialization of TCP/IP fails. Depending on the error, it may be automatically retried in 30 seconds.
User Action:
If the error is permanent (no retry), then correct the problem and issue another TCPIP START command.
If the error is temporary (retry will occur), then correct the problem so that the retry will succeed.
Reason:
This message is issued in response to a SHOW TCPIP command when the HPNS interface is in use. It shows the TCP/IP region jobname, TCP/IP node name, and TCPIP.DATA dataset name.
The TCP/IP version is shown in vvvv (For example, 3.2). If the version cannot be determined, 'UNKNOWN' is displayed.
System Action:
None.
User Action:
None.
Reason:
This message is issued when the HPNS interface subtask has an initialization failure. The reasons are listed below and description are provided.
The interface was unable to obtain required storage.
An attempt to initialize the macro interface failed. The target TCP/IP job is shown, with the return code and error number.
System Action:
If this error occurs during TCPIP START processing, initialization fails. If it occurs later, an individual SOCKET verb will fail.
User Action:
Examine the error information and determine whether the correct jobname is being used.
You may need to contact your software support office.
Reason:
This message is issued to the SOLVE log when the TCP/IP HPNS interface receives a TCP/IP termination notification, The reason is displayed.
Termination reasons are:
1: The TCP/IP address space has terminated
2: TCP/IP has terminated the connection to SOLVE
4: Other reason (Manual says CALL IBM).
System Action:
The TCP/IP interface will automatically stop.
User Action:
Determine the reason that the termination has occurred and take appropriate corrective action.
Reason:
This message is issued in response to the TCPIP START command if an attempt to use the TCPAXS interface is made in an environment that does not support it.
System Action:
The TCPIP START command fails.
User Action:
Determine the correct interface type for the current operating system and environment. Issue another TCPIP START command using the TYPE=tttt operand with the correct type specified.
Reason:
This message is issued in response to a TCPIP START command when the interface to TCPaccess is unable to initialize. A reason number and description are provided. The reasons are listed below...
1 - NO STORAGE FOR GLOBAL CONTROL BLOCKS
The interface was unable to obtain required storage.
5 - UNRECOGNIZED OPTION: ooooooooo
The TCPIP START commands OPTIONS operand had keywords specified that are not recognized by the TCPAXS interface.
6 - DUPLICATE OPTION: ooooooo
The named TCPIP START OPTIONS operand was duplicated.
8 - SSID OPTION INVALID: oooooo
The 'SSID' TCPIP START option is not valid.
9 - GTF OPTION INVALID: oooooo
The 'GTF' TCPIP START option is not valid.
10 - APPL OPTION INVALID: oooooo
The 'APPL' TCPIP START option is not valid.
11 - PW OPTION INVALID: oooooo
The 'PW' TCPIP START option is not valid.
12 - DNS OPTION INVALID: oooooo
The 'DNS' TCPIP START option is not valid.
20 - AOPEN FAILED RC=rr R0=oo DIAG=ddddd
The TCPaccess AOPEN call failed. Refer to the TCPaccess messages and codes reference for detailed explanation. This is not considered to be a retryable error.
21 - AOPEN FAILED RC=rr R0=oo DIAG=ddddd
The TCPaccess AOPEN call failed. Refer to the TCPaccess messages and codes reference for detailed explanation. 31 - BAD RET HOSTNAME LEN: llll
A TCPaccess GET HOST,BYNAME returned a name with an unacceptable length.
System Action:
TCP/IP initialization fails. Depending on the error, it may be automatically retried in 30 seconds.
User Action:
If the error is permanent (no retry), then correct the problem and issue another TCPIP START command.
If the error is temporary (retry will occur), attempt to correct the problem so that the retry will succeed.
Reason:
This message is issued in response to a SHOW TCPIP command when the TCPAXS interface is in use. It shows the TCPAXS SSID in use.
If the version can be determined, it will be displayed. Otherwise, 'UNKNOWN' will be displayed.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a TCPIP START command when the interface to Interlink TCPAXS encounters an error whilst obtaining the local IP address and domain name. The DIRSRV macro encountered the displayed error.
The return code and diagnostic information can be analyzed using the TCPAXS unprefixed messages and codes manual.
System Action:
TCP/IP initialization fails. Depending on the error, it may be automatically retried in 30 seconds.
User Action:
If the error is permanent (no retry), then correct the problem and issue another TCPIP START command.
If the error is temporary (retry will occur), attempt to correct the problem so that the retry will succeed.
Reason:
This message is issued to the SOLVE log when the TCP/IP TCPAXS interface receives a TCP/IP termination notification, The reason is displayed.
Termination reasons are:
0: Operator has drained TCPAXS subsystem.
4: Operator has stopped TCPAXS subsystem.
8: TCPAXS subsystem has abended.
System Action:
The TCP/IP interface will automatically stop.
User Action:
Determine the reason that the termination has occurred and take appropriate corrective action.
Reason:
You issued the TCPIP START command in an environment that does not support the Hitachi XNF/TCP interface.
System Action:
The TCPIP START command fails.
User Action:
Determine the correct interface type for the current operating system and environment. Issue another TCPIP START command using the TYPE=tttt operand with the correct type specified.
Reason:
You issued the TCPIP START command when the XNF/TCP interface to TCP/IP was unable to initialize. A reason number and description are provided.
The reasons are listed below:
1 - NO STORAGE FOR GLOBAL CONTROL BLOCKS
The interface was unable to obtain the required storage.
2 - NO STORAGE FOR LOCAL CONTROL BLOCKS
The interface was unable to obtain the required storage.
3 - LOAD FAILED FOR INTERFACE MODULE nnnnnnn
The interface was unable to load a required module. If the module name is JJTXAPI, it probably indicates that XNF/TCP is not installed on this system, or that the XNF/TCP modules are not in the Linklist.
4 - JJTXAPI EP FORMAT INVALID FOR: aaaaaaaa
The XNF/TCP interface module (JJTXAPI) entry point table was not formatted correctly, for the named entry point.
5 - UNRECOGNIZED OPTION: ooooooooo
The TCPIP START command's OPTIONS operand had keywords specified that are not recognized by the XNF/TCP interface.
6 - DUPLICATE OPTION: ooooooo
The named TCPIP START OPTIONS operand was duplicated.
7 - UCE OPTION INVALID: oooooo
The 'UCE' TCPIP START option is not valid. The UCE option value must be a 1-8 character name, with the first character alphabetic or national (@#$), and the remaining characters alphanumeric or national.
Normally the UCE option is not required, as the XNF/TCP interface locates the correct UCE automatically. If specified, the UCE name must be the primary UCE name in the XTCPDF table.
Specifying UCE=NONE sets the UCE name to null. An XAPI XQUERY call to XNF/TCP to obtain the UCE name failed. The return code is shown.
11 - XQUERY (1) FAILED TO RETURN UCE NAME
An XAPI XQUERY call to XNF/TCP to obtain the UCE name worked, but the returned UCE name was blank.
20 - XOPEN FAILURE, RC: nn
An XAPI XOPEN call to open a UDP port to listen for XNF/TCP termination failed. The XOPEN return code is displayed.
This return code indicates a fatal error.
21 - XOPEN FAILURE, RC: nn
An XAPI XOPEN call to open a UDP port to listen for XNF/TCP termination failed. The XOPEN return code is displayed.
This return code indicates that the call can be retried.
30 - XQUERY (2) FAILURE, RC: nn
An XAPI XQUERY call to XNF/TCP to obtain the host name and IP address failed. The return code is shown.
31 - XQUERY (2) DID NOT RETURN HOST NAME
An XAPI XQUERY call to XNF/TCP to obtain the host name and IP address worked, but the returned host name was blank.
System Action:
TCP/IP initialization fails. Depending on the error, it may be automatically retried in 30 seconds.
User Action:
If the error is permanent (no retry), then correct the problem and issue another TCPIP START command.
If the error is temporary (retry will occur), attempt to correct the problem so that the retry will succeed.
Reason:
This message is issued when the region establishes a connection to the Hitachi XNF/TCP interface. P1 shows the UCE name for the connection.
System Action:
None.
User Action:
Connections to the NetMaster Telnet server may now be established. If XNF/TCP is the region's primary access method, XNF CONNECT P1 commands may be issued to create a terminal session to the region.
Reason:
This message is issued to the SOLVE log when the TCP/IP XNF/TCP interface has certain errors.
System Action:
None.
User Action:
Refer any message to the product support engineer.
Reason:
This message is issued to the SOLVE log when the XNF/TCP interface is tracing certain events.
System Action:
None.
User Action:
Refer any message to the product support engineer.
These messages are only produced if internal tracing is enabled.
Reason:
This message is issued to the SOLVE log when the XNF/TCP interface is tracing certain events.
System Action:
None.
User Action:
Refer any message to the product support engineer.
These messages are only produced if internal tracing is enabled.
Reason:
This message is issued to the SOLVE log when the XNF/TCP interface is tracing certain events.
System Action:
None.
User Action:
Refer any message to the product support engineer.
These messages are only produced if internal tracing is enabled.
Reason:
This message is issued when the XNF/TCP interface subtask has an initialization failure. A reason number and description are provided.
The reasons are listed below:
The interface was unable to obtain required storage.
An XAPI XQUERY call to obtain the host IP address and name failed, and the return code is displayed.
System Action:
If this error occurs during TCPIP START processing, initialization fails. If it occurs later, an individual SOCKET verb fail.
User Action:
Examine the error information and determine whether the problem can be corrected.
You may need to contact Technical Support.
Reason:
This message is issued to the SOLVE log when the TCP/IP XNF/TCP interface is posted to terminate.
The XRECV call return codes are documented in the Hitachi XNF/TCP Description and Reference (6190-3-581).
The most common return code is 32 which indicates that XNF/TCP is being shut down.
System Action:
The TCP/IP interface will automatically stop.
User Action:
Determine the reason that the SHUTDOWN was issued and take appropriate corrective action.
Reason:
A TCPIP START TYPE=TISP command has been entered in an operating system environment which does not support the Fujitsu TISP interface.
System Action:
The TCPIP START command fails.
User Action:
Determine the correct interface type for the current operating system and environment. Issue another TCPIP START command using the TYPE=tttt operand with the correct type specified.
Reason:
A TCPIP START TYPE=TISP command was entered to start the TISP interface to TCP/IP but the interface was unable to initialize. A reason code and description are provided.
The reasons are listed below:
1 - NO STORAGE FOR GLOBAL CONTROL BLOCKS
The interface was unable to obtain the required storage.
2 - NO STORAGE FOR LOCAL CONTROL BLOCKS
The interface was unable to obtain the required storage.
3 - UNRECOGNIZED OPTION: ooooooooo
The TCPIP START command's OPTIONS operand had keywords specified that are not recognized by the TISP interface.
4 - DUPLICATE OPTION: ooooooo
The named TCPIP START OPTIONS operand was duplicated.
5 - OPTION VALUE IS INVALID: oooooo
The TCPIP START option shown is not valid.
6 - TCP/UDP APPL NAME RANGES OVERLAP
The values specified on the OPTIONS TCP= and OPTIONS UDP= operands could result in the same APPL name being generated for both a TCP APPL and a UDP APPL.
If the same APPL name prefix is used, the ranges specified should not overlap.
7 - INTERNAL ERROR - 3I5 RETURN CODE WAS nnnn
An internal error has occurred.
8 - TIOPEN FOR applname FAILED, CODE nnnn
An attempt to OPEN the APPL specified on OPTIONS APPL= failed. The APPL name and return code are shown.
9 - TISP IS STOPPING OR IS INACTIVE
TISP is stopping, is inactive, has abended or has been In this case the TCPIP START request will retry automatically.
10 - APPL applname IS ALREADY IN USE
An attempt to OPEN the APPL specified on OPTIONS APPL= failed because the APPL is already in use.
11 - APPL applname IS NOT DEFINED TO TISP
An attempt to OPEN the APPL specified on OPTIONS APPL= failed because the APPL is not defined to TISP.
12 - APPL applname IS NOT DEFINED WITH PROTOCOL=TCP
The APPL specified on OPTIONS APPL= is not defined with PROTOCOL=TCP.
13 - APPL applname IS NOT DEFINED WITH PORT=0
The APPL specified on OPTIONS APPL= is not defined with PORT=0.
14 - TIINF FOR applname FAILED, CODE nnnn
After opening the APPL specified on OPTIONS APPL=, SOLVE issues a TIINF macro to obtain information about the APPL definition. The TIINF macro has failed with the code nnnn.
System Action:
TCP/IP initialization fails. Depending on the error, it may be automatically retried in 30 seconds.
User Action:
If the error is permanent (no retry), then correct the problem and issue another TCPIP START command.
If the error is temporary (retry will occur), attempt to correct the problem so that the retry will succeed.
Reason:
SOLVE has established a connection to TISP using the APPL name shown.
System Action:
None.
User Action:
None.
Reason:
This message is sent to the SOLVE activity log when the TISP TCP/IP interface is tracing certain events. It shows the completion information for a TISP macro. The following information is shown:
nnnnn - The socket ID of the requesting socket macro
- The name of the TISP macro xxx
- The macro type (AIB for AIB based macros, or TIB for TIB based macros) cccc
- The return code from the macro. If the return code has more than one part (for example, TIBYERR1 and TIBYERR2), the second part is shown as well. That is, the code is displayed as cccc,dddd.
System Action:
None.
User Action:
Refer any message to the product support engineer.
These messages are only produced if internal tracing is enabled.
Reason:
This message is sent to the SOLVE activity log when the TISP TCP/IP interface is tracing certain events. It indicates that the following information is a dump of storage, which is described by aaaaaaaaaaaa.
System Action:
None.
User Action:
Refer any message to the product support engineer.
These messages are only produced if internal tracing is enabled.
Reason:
This message is sent to the SOLVE activity log when the TISP TCP/IP interface is tracing certain events. It shows a dump of an area of storage. Preceding this storage dump will be message TVIB91 which describes what the storage is.
System Action:
None.
User Action:
Refer any message to the product support engineer.
These messages are only produced if internal tracing is enabled.
Reason:
The keyword parameter P1 was either omitted or specified incorrectly.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
The user security exit ($CAUAUEX) encountered an error. A specific error message was not returned.
System Action:
The security check requested is terminated.
User Action:
Correct and retry.
Reason:
An invalid return code was returned from the user security exit ($CAUAUEX).
System Action:
The security check requested is terminated.
User Action:
Correct and retry.
Reason:
Security check processing is not supported for application P1 .
System Action:
The security check requested is terminated.
User Action:
Contact your local support representative.
Reason:
The maintenance of resource security information is not supported.
System Action:
The requested function is terminated.
User Action:
Contact your local support representative.
Reason:
The keyword parameter P1 was either omitted or specified incorrectly.
System Action:
The request is rejected.
User Action:
Correct and retry.
Reason:
A parameter was specified incorrectly when calling the User Authorization Manager.
System Action:
None.
User Action:
Correct the call parameters and retry.
Reason:
An invalid command was passed to the User Authorisation Manager.
System Action:
None.
User Action:
Correct the command and retry.
Reason:
The requested command is not allowed on the currently displayed panel.
System Action:
The command is rejected.
User Action:
Erase the command from the command line.
Reason:
Userid P1 is not authorized to perform maintenance functions in UAMS.
System Action:
The function is terminated.
User Action:
Contact the System Administrator if the function is required.
Reason:
The requested action was cancelled by use of the CANCEL command or CANCEL function key.
System Action:
None.
User Action:
None.
Reason:
The requested page number is not present in the current series of panels.
System Action:
None.
User Action:
None.
Reason:
The requested userid was not found on the UAMS Database.
System Action:
None.
User Action:
None.
Reason:
The user definition was successfully updated on the database.
System Action:
None.
User Action:
None.
Reason:
The user definition was successfully added to the database.
System Action:
None.
User Action:
None.
Reason:
The user definition was successfully deleted from the database.
System Action:
None.
User Action:
None.
Reason:
The user password was successfully updated on the database.
System Action:
None.
User Action:
None.
Reason:
The password was verified successfully.
System Action:
None.
User Action:
FILE the password change by pressing F3 or by using the SAVE command.
Reason:
The user definition to be added already exists on the database.
System Action:
None.
User Action:
Correct the name of the record to be added, or use the update option to modify the existing record.
Reason:
The requested user definition does not exist on the database.
System Action:
None.
User Action:
Correct the name of the requested record and retry, or use the ADD option to create a new record.
Reason:
The NPF Command Member and the NPF Message Member must be blank if an NPF Resource List is provided.
System Action:
None.
User Action:
Erase one of the conflicting values.
Reason:
This field must not be entered unless the PPO message receipt indicator is set to YES .
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Erase the field in error, or change the PPO message indicator to YES .
Reason:
The field must not be entered unless the NPF Undeliverable Message Receipt field is set to 'NO'.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Erase the field in error, or set the NPF Undeliverable Message Receipt field to 'NO'.
Reason:
The supplied group definition is invalid.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the definition.
Reason:
The user is not authorized for the requested feature. The user's parameters for this feature cannot be altered.
System Action:
None.
User Action:
If authorization is required, alter the Access Authority table.
Reason:
The requested group definition does not exist on the database.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the name of the requested group definition and retry.
Reason:
The route code field value is invalid - it must be ALL or NONE or a list of route codes from 1 to 128 (eg 3,6-10).
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the route code value and retry.
Reason:
The message level is invalid - it must be ALL or NONE or a list of message levels from the values WTOR, I, CE, E, IN, BC.
System Action:
None.
User Action:
Correct the message level value and retry.
Reason:
A force password change for the requested user is invalid as this is a group user definition and cannot be used for logon.
System Action:
The request is rejected.
User Action:
None.
Reason:
A MAI session model has not been supplied when the the MAI privilege class is 'B', 'C' or 'D'.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the MAI privilege class or provide an MAI session model.
Reason:
A PRIVATE Access Mask must be provided if the user is authorised for private transmission requests or private transmission control.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Enter the FTS Access Mask or disallow private transmission requests and control.
Reason:
A SYSTEM Access Mask must be provided if the user is authorised for system transmission requests or system transmission control.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the FTS Access Mask or disallow system transmission requests and control.
Reason:
P1 is a required field and must be provided.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Enter a value in the required field.
Reason:
The field requires an NPF Message member to be supplied as this field determines if, in spite of any restrictions on the message delivered to the user, the user is able to receive messages about resources for which no other user is authorised.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Erase the field in error, or set the NPF Undeliverable Message Receipt field to 'NO'.
Reason:
An ADD user request has been issued. The user id specified contains characters that are invalid. Valid characters are A-Z, 0-9 and national characters @, # and $.
System Action:
The ADD operation is rejected.
User Action:
Correct the user id value and retry the ADD operation.
Reason:
The indicated field must contain only Y or N to indicate Yes or No for the days sunday to saturday (SMTWTFS).
System Action:
The cursor is placed on the field in error and the field(s) highlighted.
User Action:
Correct the field and retry the operation.
Reason:
The indicated field can only be specified if the 'Notify By' field is supplied.
System Action:
The cursor is placed on the field in error and the field(s) highlighted.
User Action:
Correct the field by either supplying a notification mode or remove the field and retry the operation.
Reason:
The indicated field specifies a time that is incorrect. The time must be between 0000 and 2359.
System Action:
The cursor is placed on the field in error and the field(s) highlighted.
User Action:
Correct the field by supplying a correct time.
Reason:
The field P1 is only permitted to be specified it the Notify by field specifies a Notification Mode of EXIT.
System Action:
The cursor is placed on the field in error and the field is highlighted.
User Action:
Correct the field by blanking it out or change the Notify by field to EXIT.
Reason:
The field P1 is required if the Notify by field specifies a Notification Mode of EXIT.
System Action:
The cursor is placed on the field in error and the field is highlighted.
User Action:
Correct the field by specifying an NCL exit procedure name.
Reason:
The Primary Menu entered in the field indicated contains an invalid specification. The required format is 3 character application id defined in the application register followed by a 3 character menu identifier from 001 to 255.
System Action:
The cursor is placed on the field in error and the field is highlighted.
User Action:
Correct the field by specifying a valid primary menu id.
Reason:
The USERID being added with the UAMS copy function is already defined to the security subsystem.
System Action:
The cursor is placed on the field in error and the field is highlighted.
User Action:
Correct the field by specifying a user id that is not already defined or CANCEL the ADD function.
Reason:
The password field must have a length between the defined password minimum and maximum lengths set by the system parameters PWMIN and PWMAX (SYSPARMS PWMIN= and SYSPARMS PWMAX=).
System Action:
The cursor is placed on the field in error and the field is highlighted.
User Action:
Correct the password field length by specifying the required number of characters between the minimum and maximum password lengths allowed by your installation.
Reason:
A password change or user add request has specified invalid characters for the password. The password must not contain embedded blanks.
System Action:
The cursor is placed on the field in error and the field is highlighted.
User Action:
Correct the password by removing any blanks and retry the operation.
Reason:
Access to the Object Services Security procedures is not permitted if Object Services Access is not allowed.
System Action:
The cursor is placed on the field in error and the field is highlighted.
User Action:
Correct the Object Services Security Access authorisation.
Reason:
The Primary Menu entered in the field indicated contains an invalid specification. The required format is 3 character application id defined in the application register followed by a 3 character menu identifier from 001 to 255.
System Action:
The cursor is placed on the field in error and the field is highlighted.
User Action:
Correct the field by specifying a valid primary menu id.
Reason:
The user indicated that the notification mode is EXIT, however the exit procedure name has not been specified.
System Action:
The cursor is placed on the field in error and the field is highlighted.
User Action:
Correct the field by specifying a valid exit procedure name or change the notification mode.
Reason:
When a user updates or deletes a UAMS userid a LOCK is obtained for the duration - all updates and deletes for the same userid are denied until such time as the LOCK is freed (ie. when the user holding the lock has completed processing for the indicated userid).
System Action:
The request to update or delete a user definition is rejected.
User Action:
Try the request again at a later time.
Reason:
An attempt to delete a group user failed because there are still users defined to the group.
P1 indicates the first user encountered that is defined to the group, however, this may not be the only user.
System Action:
The request to delete the definition is rejected.
User Action:
Either delete the user definitions that reference the group or update them to remove the reference.
Reason:
The APPC access key/lock field specified an invalid value. Valid values are any number, range or combination of numbers from 1 to 16.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the value and retry.
Reason:
A request to delete a user has been entered. This delete requires confirmation.
System Action:
None.
User Action:
Press the ENTER key to confirm the delete of the user, or the CANCEL key to cancel the delete request.
Reason:
An authority level of 1 has been specified for SOLVE:Connect for Netware user authority. Authority level 1 is not yet supported.
System Action:
The field in error is hilighted.
User Action:
An authority level of 0 or 2 must be specified. Correct the field in error and continue the operation.
Reason:
The value for timeout P1 is invalid. Correct formats are:
MMM.SS MMM .SS
Where MMM are minutes, SS are seconds. The range for MMM is 0 to 999. The range for SS is 0 to 59.
System Action:
The cursor is placed on the field in error and the field is highlighted.
User Action:
Correct the timeout field and retry the operation.
Reason:
Of the panels available for user setup, there are no more required for this user ID. This may be because the features are not available or authorized for this user ID.
System Action:
None.
User Action:
None. Information only.
Reason:
The MSDM Access setting conflicts with the Privilege Class.
System Action:
The update request is rejected.
User Action:
Change the Privilege Class to A or set the MSDM Access to 0.
Reason:
The user or group definition was successfully deleted from the database.
System Action:
None.
User Action:
None.
Reason:
You specified an incorrect parameter when calling the Selection List Manager.
System Action:
The request is rejected.
User Action:
Correct the call parameters and retry.
Reason:
There are no users defined in the UAMS database.
System Action:
None.
User Action:
Define users using the Add option. You must define at least one user with UAMS authority.
Reason:
You requested a generic selection from the Selection List Manager. No users match the supplied criteria. The criteria ( P1 ) is shown as User Prefix=xxxx and/or Group=yyyy depending on the parameters that you provided.
System Action:
None.
User Action:
None.
Reason:
The password and/or the user details for user P1 were updated successfully.
System Action:
None.
User Action:
None.
Reason:
The password for user P1 was verified successfully. User P1 is able to perform the logon process.
System Action:
None.
User Action:
None.
Reason:
A new password was entered. It must be entered a second time for verification.
System Action:
None.
User Action:
Re-enter the new password, or press the Cancel key to cancel the change of password.
Reason:
The two entries of the new password did not match. They must both be re-entered.
System Action:
None.
User Action:
Re-enter the new password or press the Cancel key to cancel the change of password.
Reason:
The password was verified successfully. To save your changes press the 'file' key.
System Action:
None.
User Action:
None.
Reason:
Your user password has expired and a new password must be entered before continuing.
System Action:
None.
User Action:
Enter a new password.
Reason:
A Userid is being used for the first time. The password must be changed before continuing.
System Action:
None.
User Action:
Enter a new password.
Reason:
The password for user P1 was verified unsuccessfully and user P1 is unable to perform the logon process.
System Action:
None.
User Action:
None.
Reason:
A required field has not been entered. Enter either your current password and new password, or change your user details.
System Action:
Processing of the password change request does not proceed until the required fields are entered.
User Action:
Enter the required data; either current password and new password, or update your user details.
Reason:
A user request to change their own password requires verification of their current password. The verification of their current password failed.
System Action:
The change password request will not proceed until the user has entered their current password correctly.
User Action:
Correct the current password and retry the password change operation.
Reason:
A user has requested the password update function from an LU1 device and has cancelled the password change request.
System Action:
The password change function is cancelled. The users current password remains unchanged.
User Action:
None.
Reason:
During logon processing the password of a new user or a user whose password has been force changed must be changed. The user has cancelled out of the password change function so the session has been terminated.
System Action:
The user is logged off the system.
User Action:
A new password must be supplied if the user is to log on.
Reason:
A user on an LU1 device who is attempting a password change has been requested to enter their current or new password and has entered an invalid password string.
System Action:
The password must be re-entered.
User Action:
The password must be a single word of not more than 8 characters. Re-enter a valid password.
Reason:
The password entered as a new password failed verification because the first byte contained an illegal character.
System Action:
Password verification fails and you are asked to re-enter a valid password.
User Action:
Re-enter a valid password.
Reason:
The requested command is not allowed on the currently displayed panel.
System Action:
The command is rejected.
User Action:
Erase the command from the command line.
Reason:
An invalid command was passed to the User Authorisation Manager.
System Action:
None.
User Action:
Correct the command and retry.
Reason:
The requested action was cancelled by use of the CANCEL command or function key.
System Action:
None.
User Action:
None.
Reason:
The requested page number is not present in the current series of panels.
System Action:
None.
User Action:
None.
Reason:
The requested userid was not found on the UAMS Database.
System Action:
None.
User Action:
None.
Reason:
A Userid is being used for the first time. The User NAME must be entered. LOCATION and PHONE NUMBER are optional.
System Action:
None.
User Action:
Enter User Details.
Reason:
This message is displayed when a UAMS update by one of the UAMS utility procedures $UAUTILx fails. The message indicates the userid for which the error occured and the reason for that error as returned by the
SECCALL UPDATE call.
System Action:
The indicated user is not updated, processing continues.
User Action:
Examine the cause of the failure to determine the best action to correct the error.
Reason:
This message indicates the number of userids processed and the number of errors encountered when using the utility procedures $UAUTIL1/2. It is displayed when all userid processing is complete.
System Action:
NONE
User Action:
If the message indicates there were errors then message UAUT01 would have appeared for each error encountered. The reason for the failure is indicated in that message, thus, take the action appropriate to the error.
Reason:
The timezone name entered is invalid. A timezone name must contain only the characters A - Z , 0 - 9, and the national characters @, # and $. Additionally, the name must not be SYSTEM or USER.
System Action:
The field in error is highlighted and the entry cannot be filed until the error is corrected.
User Action:
Correct the timezone name in error.
Reason:
Data Warehouse Services attempted to call back an application, but an error was encountered loading the call-back package. The procedure being loaded was P1 which was in the package P2 . The OML error code was P3 . This message is written to the log.
System Action:
The associated application function is not performed.
User Action:
To determine why the application package is not loading, refer to the messages in the log. Notify the systems administrator.
Reason:
An error occurred while manipulating an NCL VARTABLE in the procedure $URCALL. P1 is the vartable identifier, P2 is the function being performed, and P3 is the feedback code set by the vartable verb.
System Action:
None
User Action:
Notify your systems administrator.
Reason:
While forwarding data to warehouse server P1 incomplete or incorrect data was encountered. This data cannot be sent to the server and was discarded. The data's record ID is P2.
System Action:
The data is discarded and processing continues.
User Action:
This condition may occur if the system is terminated suddenly via an FSTOP, abend or cancel. Data may have been partially saved in the store for the server when the system terminated.
To avoid this condition use the shutdown command.
Reason:
An attempt to relate an application to a data warehouse server failed because the server specified was not defined and not enough information was supplied to define the sever. At least a host name must be specified. The server specified was P1.
System Action:
Request rejected.
User Action:
Define the server or supply the server details on the store request.
Reason:
An attempt to start a data warehouse server failed because the server was not defined. The server specified was P1.
System Action:
Request rejected.
User Action:
Define the server to Data Warehouse Services.
Reason:
An attempt to start a data warehouse server failed. Additional messages are written in the log. The server name was P1.
System Action:
Request failed.
User Action:
Check the log and contact your support representative.
Reason:
Details for data warehouse object could not be retrieved because the definition does not exist. P1 is the object class and P2 is the name.
System Action:
None.
User Action:
None.
Reason:
A data warehouse store definition failed because the data class mask specified exceeded 20 characters. The mask is P1.
System Action:
Request rejected.
User Action:
Ensure that all data class masks are less than or equal to 20 bytes in length.
Reason:
A request to access the data warehouse queue file failed. The file ID is
P1 and the action being performed is P2. P3 is the file return code and the VSAM feedback code in the form nn/ff. P4 is an optional system message.
System Action:
Processing terminates.
User Action:
Interpret the return code using the NCL Reference and the VSAM feedback code using the VSAM Guide.
Reason:
A request to initialize a data warehoue queue failed because another process is already accessing the queue. The server was P1 and the that currently has the queue is P2.
System Action:
Processing terminates.
User Action:
None.
Reason:
Details for data warehouse object could not added because the definition already exists. P1 is the object class and P2 is the name.
System Action:
None.
User Action:
None.
Reason:
The server cannot be updated because the user P1 is already updating it.
System Action:
Request rejected.
User Action:
None.
Reason:
The server P1 could not queue data for transmission to the data warehouse because the queue was full and data was in the process of being sent, thus old data could not be discarded and the newly arrived data was instead discarded.
System Action:
The data to be queued is discarded and processing continues.
User Action:
Ensure that the performance of the server and network can cope with the load of data transmission or enlarge the maximum queue depth to cater for the largest peaks of data.
Reason:
The server P1 could not queue data for transmission to the data warehouse because the queue was full. The latest data was queued and oldest data was discarded.
System Action:
The data to be queued was successfully queued however older data was discarded.
User Action:
Ensure that the performance of the server and network can cope with the load of data transmission or enlarge the maximum queue depth to cater for the largest peaks of data.
Reason:
This is a trace message issued when diagnostics are requested. P1 can be any variable information.
System Action:
None.
User Action:
Collect ALL of these messages and send them to your local support representative.
Reason:
An error has been detected in NetMaster Java Framework OML command processing. This is the OML code that runs in the NetMaster region and establishes and maintains IP socket connections with the NetMaster Java Framework started task in the USS environment. The specific connection call was P1
System Action:
None.
User Action:
Retry the operation. If necessary, stop and re-start the NetMaster Java Framework started task. Ensure this NetMaster region is not experiencing environmental problems such as storage shortages or userid/ security definition problems.
If the problem recurs, contact support, providing the NetMaster Activity log around the time of the errors.
Reason:
A data collection agent has supplied invalid data (x'00') to the NetMaster data warehouse client. The invalid data is changed to blanks.
P1 shows the XML tag that was built using the data.
System Action:
Processing continues.
User Action:
Investigate why the invalid data is being supplied to the NetMaster data warehouse.
Reason:
An serious logic error was encountered in a data warehouse connection manager client process. The name of the data warehouse server definition is P1 and the error code is P2.
System Action:
The connection is terminated.
User Action:
Contact your local support representative.
Reason:
An invalid identity record was received from the remote adaptor. The server name for the remote adaptor is P1, P2 is the MDO return code, P3 is the feedback code and P4 is the component in error.
System Action:
The connection is terminated.
User Action:
Ensure that the correct server details are defined and that the adaptor on the server is the correct version.
Reason:
The NetMaster Java Framework using Data Warehouse Server P1 sent an unauthorized access key with its identity credentials.
System Action:
The connection is terminated.
User Action:
Ensure that the correct Data Warehouse Server details are defined on this NetMaster region. Ensure that the NetMaster Java Framework intialization file contains the correct identity key for this NetMaster region.
Reason:
The remote adaptor on server P1 sent an invalid XML document as a response from a warehouse update request. The server name is P1.
System Action:
The connection is terminated.
User Action:
There is an associated message written to the log. Collect all the message details and contact your local support representative.
Reason:
Data Warehouse Services attempted to call back an application for the server P1, but an error was encountered in the call-back package. The package being called is P2 and the procedure in error was P3. P4 is the OML error code received. Additional diagnostic messages are written to the log.
System Action:
The application is de-registered and no more data for that application will be sent to the data warehouse server P1.
User Action:
Contact your local support representative.
Reason:
The remote adaptor on server P1 sent a response indicating that the database update failed. The server name is P1 and the return code from the server is P2 and the error message from the server is P3.
System Action:
Processing continues and the data is discarded.
User Action:
There may be associated messages written to the log. Collect all the message details and contact your local support representative.
Reason:
An update of the data warehouse database failed for record with ID P2 for a count of P3 records. The warehouse is located on server P1.
System Action:
Processing continues and the data is discarded.
User Action:
Check the log for additional messages that may indicate the cause of the error.
Reason:
This is a continuation of message URCO0106. P1 is the remainder of the error message from the server.
System Action:
None.
User Action:
None.
Reason:
The target warehouse server has not responded to a send document within the alloted time frame. The server name is P1. The document was sent to the server at time P2 and no response was received by time P3.
System Action:
The client is recycled and the connection is reestabilished.
User Action:
If this error occurs frequently then it may indicate a problem with the server's or network's performance. Another possibility is that an error occurred at the server, check the log for the server.
Reason:
The format of the global variable is incorrect; therefore, no blackout period is set.
A blackout period enables the processing load to be spread over the hour. Data sampling continues, but all records are placed in the Data Warehouse Server's queue. At the conclusion of the blackout period, data records are sent to the ReportCenter Java Task.
The global variable $URBOMin must be in the format aa bb.
aa specifies the start time of the blackout period in minutes. bb specifies the stop time in minutes.
They must also be in the range of 0 to 59.
System Action:
None.
User Action:
We recommend that you set this global variable in the NMINIT or NMREADY procedure by inserting the following line:
000$URBOMIN = aa bb
You can also set it dynamically by issuing the following command from OCS or the Command Entry panel:
$GLBL $URBOMIN aa bb
If you do this, you must also issue the RCY command against your Data Warehouse Server. To do this, enter the menu shortcut /DWS to list the servers.
Reason:
An serious logic error was encountered in a data warehouse connection manager client process. The name of the data warehouse server definition is P1 and the error code is P2.
System Action:
The connection is terminated.
User Action:
Contact your local support representative.
Reason:
An invalid identity record was received from the Java Task.
The DWS server name is P1, P2 is the MDO return code, P3 is the feedback code and P4 is the component in error.
System Action:
The connection is terminated.
User Action:
Ensure that the correct Java Task details are defined on this NetMaster region. Ensure that the Java Task code has been correctly installed and is using a correct initialization parameter file.
Reason:
The Java Task Data Warehouse Server P1 sent an unauthorized access key with its identity credentials.
System Action:
The connection is terminated.
User Action:
Ensure that the correct Java Task details are defined on this NetMaster region. Ensure that the Java Task intialization file contains the correct identity key for this NetMaster region.
Reason:
The ReportCenter Data Feed destination P1 has been deleted.
System Action:
An APPLICATION type event with name $URSTOREDELETE specifying the server name as the resource is issued.
User Action:
None
Reason:
The Data Feed Destination P1 is defined by a Customizer parameter group, and can only be updated by actioning that parameter group.
This is to avoid discrepancies in the destination definitions.
This destination is defined by one of the following parameter groups:
REPORTCENTER, on a ReportCenter control region REPORTDATA, on a region that feeds data to ReportCenter
System Action:
None
User Action:
If you want to change the IP or Port Address of this destination, update the REPORTDATA or REPORTCENTER parameter group, which can be found using the /PARMS shortcut.
In normal operation, you will only do this if the IP address or port number of your primary ReportCenter Java Task changes after implementation.
Reason:
The message indicates that the CHK command was issued for the Data Feed Destination P1.
System Action:
The system checks that this NetMaster region still has an active IP connection with the ReportCenter Java Task pointed to by the Data Feed destination.
User Action:
None.
Reason:
The value specified for field P1 is not a valid mask. The mask MUST be composed of alphanumeric, national characters and the asterisk (*). The first character must not be numeric and no imbedded blanks are allowed.
System Action:
The field is set in error.
User Action:
Specify a valid mask for the field.
Reason:
The field P1 must be specified if the field P2 is specified.
System Action:
The field is set in error.
User Action:
Specify a value for P1 or blank out P2.
Reason:
A value for field P1 must be specified.
System Action:
The field is set in error.
User Action:
Specify a valid value for P1.
Reason:
The server P1 cannot be updated because the user P2 is already updating it.
System Action:
Request rejected.
User Action:
None.
Reason:
The record was successfully saved. P1 is the name of the record.
System Action:
None.
User Action:
None.
Reason:
The action was cancelled as requested by the user.
System Action:
None.
User Action:
None.
Reason:
The Utilities external interface procedure $UTCALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $UTCALL terminates.
User Action:
Check the syntax of the call to procedure $UTCALL.
Reason:
The Utilities external interface procedure $UTCALL failed during request processing because a mandatory parameter was omitted. The keyword was P1 and the $UTCALL option was P2 .
System Action:
The request is rejected and procedure $UTCALL terminates.
User Action:
Check the syntax of the call to procedure $UTCALL.
Reason:
A request to allocate a dataset was successful.
System Action:
None.
User Action:
None.
Reason:
A request to open a dataset was successful.
System Action:
None.
User Action:
None.
Reason:
A request to allocate and open a dataset was successful.
System Action:
None.
User Action:
None.
Reason:
A request to close a dataset was successful.
System Action:
None.
User Action:
None.
Reason:
A request to unallocate a dataset was successful.
System Action:
None.
User Action:
None.
Reason:
A request to close and unallocate a dataset was successful.
System Action:
None.
User Action:
None.
Reason:
A request to allocate a dataset failed for the reason ( P1 ) stated which may be one of:
- DATASET IS NOT CATALOGED The dataset has not been cataloged (DAIR code 1708)
- EXCLUSIVE REQUEST FAILED The dataset cannot be shared exclusively (DAIR code 020C). You have requested DISP=OLD but the dataset is already allocated.
- DAIR CODE nnnn Dynamic Allocation has failed, failure code is nnnn.
System Action:
The dataset is not allocated.
User Action:
Refer to the failure reason. If the message is a DAIR code, detailed explanations of these are available in the NETINFO database.
Reason:
A request to open a dataset failed for the reason ( P1 ) stated which may be one of:
DATASET IS NOT ALLOCATED
The dataset has not been allocated (ACB CODE 80)
RESTRICTED BY SHAREOPTIONS
The SHAREOPTIONS value for the cluster prevent the dataset from being opened in the manner requested (ACB CODE A8). For example, you are attempting to open a SHAREOPTIONS(2) file for output but it is already open for output, perhaps in another region.
ACB CODE xx
The VSAM OPEN macro with the error code X'xx'.
System Action:
The dataset is not opened.
User Action:
Refer to the failure reason. If the message is an ACB code, detailed explanations of these are available in the NETINFO database.
Reason:
A request to unallocate a dataset failed for the reason ( P1 ) stated which may be one of:
DATASET IS OPEN
The dataset has not been closed (DAIR code 0420)
SPECIFIED DD NAME NOT FOUND
This dataset has not been allocated (DAIR code 0438)
DAIR CODE nnnn
Dynamic Allocation has failed, failure code is nnnn.
System Action:
The dataset is not unallocated.
User Action:
Refer to the failure reason. If the message is a DAIR code, detailed explanations of these are available in the NETINFO database.
Reason:
The Memo NCL Interface procedure $UTMO06Z failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and the procedure terminates.
User Action:
Correct the keyword value and retry the request.
Reason:
The current status of the Memo API Server is described by P1 . If the status is ACTIVE then the Memo Interface is available for use.
System Action:
None.
User Action:
None.
Reason:
The Memo NCL Interface has been called to start the Memo API Server but the Memo API Server has already been started. The current status of the Memo API Server is P1 .
System Action:
The procedure terminates without further action.
User Action:
None.
Reason:
The Memo NCL Interface has started the Memo API Server in a background region.
System Action:
The procedure terminates without further action. The Memo API Server continues to process in a background region.
User Action:
None.
Reason:
The Memo NCL Interface was called to access the Memo email system but the Memo Interface was not available. P1 describes the access function requested.
System Action:
The procedure terminates without further action.
User Action:
Start the Memo Interface and retry the operation.
Reason:
The Memo NCL Interface was called to perform a POST function and has successfully passed the mail item to the Memo API Server. P1 is the Memo ID to which the mail item will be delivered while P2 is the local User ID of the sender.
System Action:
The procedure terminates. The Memo API Server attempts to deliver the mail item to the Memo email system.
User Action:
None.
Reason:
The Memo NCL Interface was called to access the Memo email system but the Memo API Server failed to respond within the timeout period. P1 describes the likely result of the timeout event.
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
The Memo NCL Interface has received an invalid response from the Memo API Server.
System Action:
The procedure terminates.
User Action:
Contact the system administrator.
Reason:
The Memo NCL Interface was called to send a mail item to the Memo email system but the amount of data passed exceeds the maximum allowed.
System Action:
The request is rejected.
User Action:
Reduce the amount of data in the mail item and retry the request.
Reason:
The Memo API Server procedure $UTMO07Z failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The procedure terminates.
User Action:
Correct the indicated keyword value specified when invoking the Memo NCL Interface procedure $UTMO06Z with OPT=START.
Reason:
An invalid request parameter value was passed to the Memo API Server procedure. The parameter was P1 and the value was P2 .
System Action:
The Memo API Server ignores the request.
User Action:
Contact the system administrator.
Reason:
The Memo API Server has been unable to define the subsystem required to enable the Memo Interface. P1 is the name of the subsystem and P2 is the program name.
System Action:
The Memo API Server terminates.
User Action:
Review the activity log for other messages relating to the SUBSYS command to determine the cause of the error.
Reason:
The Memo API Interface has returned an error indication to the Memo API Server procedure. P1 was the function requested. P2 indicates the message number of an associated message in the log which further describes the nature of the error.
System Action:
The requested function fails.
User Action:
Review the activity log for the message indicated by P2 .
Reason:
The Memo API Server has rejected a request to access the Memo email system. P1 was the requested function and P2 is the reason for the rejection.
System Action:
The requested function fails.
User Action:
Review the reason given in P2 .
Reason:
The Memo API Server has has been either successfully initialised or terminated. P1 indicates the completed state.
System Action:
None.
User Action:
None.
Reason:
This message displays the MVS system name of the system that UTIL0043 is executing on.
System Action:
None.
User Action:
None.
Reason:
This message indicates that UTIL0043 was able to load CNMNETV.
System Action:
None.
User Action:
None.
Reason:
This message follows the UT4302I message and displays information about the loaded copy of CNMNETV.
p1 is:
SOLVE if the loaded CNMNETV appears to be the SOLVE version. NETVIEW if the loaded CNMNETV appears to be the IBM NETVIEW version. UNKNOWN if the loaded CNMNETV version could not be determined.
p2 is:
VERS=Vnnn PTF=nnnnnn if p1 is SOLVE, displaying the SOLVE module version and PTF number.
DATE=dd/mm/yy CRT=xxxxxxx if p1 is NETVIEW, displaying the internal date and copyright information of the module.
<arbitrary data> if p1 is UNKNOWN, displaying the first 40 bytes of the module, in character form.
System Action:
None.
User Action:
None.
Reason:
This message indicates that UTIL0043 was unable to load CNMNETV. The return code (aaa) and reason code (bb) from the LOAD macro are displayed.
If the return code is 806, the module was not found in any accessible library (including LINKLST and LPA).
System Action:
None.
User Action:
None.
Reason:
This message indicates that UTIL0043 is commencing a scan of the active step or job library for CNMNETV.
p1 is the DDNAME of the library being scanned (normally STEPLIB or JOBLIB).
System Action:
None.
User Action:
None.
Reason:
This message indicates that UTIL0043 has finished a scan of the active step or job library datasets for CNMNETV.
The ddname scanned is shown as p2. The number of occurrences is shown as p1.
System Action:
None.
User Action:
None.
Reason:
This message indicates that UTIL0043 is commencing a scan of the active system LINKLIST library datasets for CNMNETV.
System Action:
None.
User Action:
None.
Reason:
This message indicates that UTIL0043 has finished a scan of the system LINKLIST library datasets for CNMNETV.
The number of occurrences is shown as p1
System Action:
None.
User Action:
None.
Reason:
This message indicates that UTIL0043 is commencing a scan of the active system LPALIST library datasets for CNMNETV.
System Action:
None.
User Action:
None.
Reason:
This message indicates that UTIL0043 has finished a scan of the system LPALIST library datasets for CNMNETV.
The number of occurrences is shown as p1.
System Action:
None.
User Action:
None.
Reason:
This message indicates that a copy of CNMNETV was found in the indicated dataset (part of the concatenation being scanned as indicated by the preceding UT4310I, UT4312I, or UT4314I message).
The following UT4321I message provides additional information.
System Action:
None.
User Action:
None.
Reason:
This message follows the UT4320I message and displays information about the located copy of CNMNETV.
p1 is:
SOLVE if the loaded CNMNETV appears to be the SOLVE version. NETVIEW if the loaded CNMNETV appears to be the IBM NETVIEW version. UNKNOWN if the loaded CNMNETV version could not be determined.
p2 is:
VERS=Vnnn PTF=nnnnnn if p1 is SOLVE, displaying the SOLVE module version and PTF number.
DATE=dd/mm/yy CRT=xxxxxxx if p1 is NETVIEW, displaying the internal date and copyright information of the module.
<arbitrary data> if p1 is UNKNOWN, the first 40 bytes of the module, in character form.
System Action:
None.
User Action:
None.
Reason:
This message indicates that an attempt to allocate the nominated dataset p1 (part of a step/joblib, linklist, or LPAlist concatenation) failed. The DYNALLOC error (p2) and info (p3) codes are indicated.
System Action:
Processing will continue with the next dataset.
User Action:
Examine the error codes and determine why the allocation failed.
Reason:
This message indicates that an error occurred when opening the nominated dataset p1 (part of a step/joblib, linklist, or LPAlist concatenation) failed.
System Action:
Processing will continue with the next dataset.
User Action:
This error should not occur. Contact your support office.
Reason:
This message indicates that an error occurred when opening the nominated dataset p1 (part of a step/joblib, linklist, or LPAlist concatenation) failed. The OPEN abended with the indicated abend/reason code.
The most likely abend code is 913-38, indicating a security violation.
System Action:
Processing will continue with the next dataset.
User Action:
RACF protected datasets cannot be opened by UTIL0043. Contact the security administrator to permit READ access to the dataset(s).
Reason:
This message indicates that an error occurred when attempting to load CNMNETV from the indicated dataset p1 (part of a step/joblib, linklist, or LPAlist concatenation) failed. The LOAD failed with the indicated abend/reason code.
System Action:
Processing will continue with the next dataset.
User Action:
This error should not occur, as the dataset was opened and a BLDL indicated that CNMNETV was present. However, a corrupt dataset could cause this. If the dataset does not appear to be corrupted, contact your SOLVE support office for advice.
Reason:
This message indicates that the SWAREQ macro returned the indicated error while attempting to process entries in the step/joblib concatenation.
System Action:
Processing will continue with the next dataset.
User Action:
Contact your SOLVE support office.
Reason:
This message indicates that all UTIL0043 output is completed.
System Action:
UTIL0043 will terminate if executing in batch.
The return code will be based on the type of CNMNETV module detected on the initial load (that is, the UT4302 or UT4304 message), as follows:
0 - if a SOLVE CNMNETV was found
4 - if a NETVIEW CNMNETV was found
8 - if an UNKNOWN CNMNETV was found
12 - if the load for CNMNETV failed
User Action:
none.
Reason:
A Packet Analyzer scan must complete within 60 seconds so that the recorded data is consistent. The current scan exceeded 60 seconds and has been terminated.
This message can indicate that the system is very busy, and that the requesting region or SSI region is not running with a sufficiently high priority to process requests in a timely manner.
System Action:
The scan is terminated prior to completion.
User Action:
Retry the action when the system is less busy. For assistance, contact Technical Support.
Reason:
The web server has received an incorrectly formatted HTTP response.
P1 is the data received.
System Action:
Processing continues.
User Action:
Report the error to your system administrator.
Check that the recipient of the HTTP request is using the HTTP protocol.
Reason:
A OML UNIX environment has been opened, and USS SHELL commands have been successfully processed. The interface between this region and the NM SSI region which communicates with OS/390 UNIX System Services is fully functional, however, 'STDERR' output has been received in response to a UNIX shell command.
System Action:
None.
User Action:
Examine the STDERR output, and accompanying log error messages, if any. STDERR output is sometimes the result of USS/OMVS setup problems and may not necessarily indicate a problem with the command or NM region.
Review the syntax and correctness of the USS command that was requested: refer to the Z/OS or OS/390 UNIX System Services Command Reference.
Investigate any specific UNIX Shell error messages that appear on your Activity log.
Reason:
An OML UNIX verb has failed.
P1 is the failing UNIX verb operand, P2 and P3 are the return code and feedback, and P4 is the reason text.
System Action:
None.
User Action:
Look at the NetMaster SSILOG and Activity Log and see if they contain any messages indicating more specific error conditions.
Confirm that you have set up the USS SSI interface correctly, including:
- Upgrading the NetMaster SSI software to the correct level
- Adding parameter UNIX=YES to the NetMaster SSI region
- Adding a RACF/ACF2/Top Secret OMVS segment, defined with a valid user ID, to the user ID associated with the SSI started task.
If you are unable to determine the nature of the error by using this information, contact your Techical Support Representative.
Reason:
A UNIX assembler call or subtask initialization call has failed.
P2 indicates the specific macro call which failed. The value shown corresponds to the call offset listed in the 'System Control Offsets to Callable Services' chapter in the OS/390 or Z/OS UNIX System Services Assembler Callable Services manual.
P3 and P4 are the return code and reason code from the failing macro call. These are listed in the OS/390 or Z/OS UNIX System Services Messages and Codes manual.
System Action:
None.
User Action:
Confirm that you have set up the USS SSI interface correctly, including:
- Upgrading the NetMaster SSI software to the correct level
- Adding parameter UNIX=YES to the NetMaster SSI region
- Adding a RACF/ACF2/Top Secret OMVS segment, defined with a valid user ID, to the user ID associated with the SSI started task
Reason:
An attempted P2 operation on HFS file P3 failed with error condition P1.
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.
System Action:
None. The requested operation cannot be performed.
User Action:
Contact your Systems Programmer or UNIX Administrator.
Provide them with the full error details from this message and any related messages. In some cases, there may be additional error details on the NetMaster Activity Log, in messages UTUSS011 or N1AM99.
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 USS HFS return codes is provided in the IBM manual z/OS Unix System Services Messages and Codes, in a chapter titled 'Return Codes (Errnos) Listed by Value'
Additional information about z/OS HFS implementation is available from the IBM Redbook publication Hierarchical File System Usage Guide.
Reason:
This message follows message UTUSS010 and provides details of the return code, reason codes, and messages returned from NetMaster's HFS file interface.
System Action:
The requested HFS file operation cannot be performed.
User Action:
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 UNIX System Services Messages and Codes for your operating system level.
Additional information about OS/390 and z/OS HFS implementation is available from the IBM Redbook publication Hierarchical File System Usage Guide.
Reason:
This message contains trace information for UTUSS calls
System Action:
None.
User Action:
Provide this information to support staff, if requested.
Reason:
A parameter was not supplied when calling the Validation Manager.
System Action:
None.
User Action:
Correct the command and retry.
Reason:
A parameter was specified incorrectly when calling the Validation Manager.
System Action:
None.
User Action:
Correct the call parameters and retry.
Reason:
The validation tables were successfully loaded into NCL VARTABLEs.
System Action:
None.
User Action:
None.
Reason:
A load of the validation tables was requested but the tables have already been loaded.
System Action:
None.
User Action:
If the tables must be refreshed, re-enter the command using the 'RELOAD=YES' parameter.
Reason:
The field must contain only alphabetic or national characters (A - Z, #, @, $) or numbers (0 - 9).
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The value supplied for the field does not match any of the valid values defined in the Validation Manager.
System Action:
None.
User Action:
Either correct the entry and retry, or enter a question mark (?) in the field to obtain a list of valid values.
Reason:
No records are defined on the database for the requested record type.
System Action:
None.
User Action:
Add the required records to the Validation Manager database.
Reason:
An invalid command was passed to the Validation Manager.
System Action:
None.
User Action:
Correct the command and retry.
Reason:
The requested command cannot be used in the current window.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
None.
Reason:
No value was selected from the displayed selection list.
System Action:
None.
User Action:
None.
Reason:
The field length must be greater than or equal to the value specified.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The validation tables are being reloaded from the database and cannot be used.
System Action:
None.
User Action:
Wait for a short period of time and then retry.
Reason:
The field value entered was not 'YES' or 'NO'. These values may be entered in abbreviated form by overtyping the first character of the field with 'Y' or 'N'. The field value will be automatically be changed to 'YES' or 'NO'.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field must contain either zero or a positive integer.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field value is not in standard date format or is outside the range of dates supported. Dates must be entered in standard DD-MMM-YYYY format or in any of the allowed shorthand formats.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field value is not in the standard time format. Times must be entered in the format HH.MM.SS or in any of the allowed shorthand formats.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field value is not in one of the allowable number formats. Numbers may be integers, real numbers, or in scientific notation.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field value must be in valid name format. Names may only consist of alphabetic characters (A - Z), numbers (0 - 9), and the national characters '@', '#' and '$'. Additionally, they cannot start with a number.
System Action:
None.
User Action:
Correct the entry and retry.
Reason:
The field must contain a value greater than or equal to the value specified.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field must contain a value less than or equal to the value specified.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field must contain only alphabetic characters (A - Z) and numbers (0 - 9).
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field must contain alphabetic characters (A - Z) only.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
An invalid validation edit number was passed to the Validation Manager on the EDITS keyword parameter.
System Action:
None.
User Action:
Correct the edit number and retry.
Reason:
The field may only contain alphabetic characters (A - Z), numbers (0 - 9), and the special characters '@', '#' and '$'.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field must contain either zero or a signed integer in the range -2147483648 to 2147483647.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field may only contain a value in expanded hexadecimal format.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field must conform to the dataset name rules. The full dataset name must be entered without quotes. If the dataset is partitioned (PDS) then a member name, enclosed in parentheses, can be appended to the dataset name.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
Blanks are only permitted at the beginning and end of the field value, they cannot be placed within the field value.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field length must be less than or equal to the value specified.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
An error occurred while manipulating an NCL VARTABLE.
System Action:
None.
User Action:
Determine the cause of the error from the return and feedback codes and retry.
Reason:
A field could not be validated because the validation tables have not been loaded.
System Action:
None.
User Action:
Load the validation tables for the specified application and retry.
Reason:
The validation table specified for validating the field does not exist.
System Action:
None.
User Action:
Add the validation table definition to the Validation Manager database, or change the name of the requested table definition.
Reason:
An error occurred while manipulating an NDB.
System Action:
None.
User Action:
Determine the cause of the error from the return code and retry.
Reason:
The field length must be equal to the value specified.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field must contain a value in the range specified.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field length must be in the range specified.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The field must contain the specified value.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
An invalid scroll amount has been entered. The valid scroll amounts are PAGE, HALF, CSR, DATA, MAX or a number. Scroll amounts can be abbreviated to the first character (ie. P, H, C, D or M).
System Action:
None.
User Action:
Enter a valid scroll amount and retry.
Reason:
The requested command is not allowed on the currently displayed window.
System Action:
None.
User Action:
Erase the command from the command line.
Reason:
Userid P1 is not authorized to create new tables or modify existing tables. System Support Services access is required.
System Action:
The function is terminated.
User Action:
Contact the System Administrator if the function is required.
Reason:
Userid P1 is not authorized to create new tables entries or modify existing table entries. System Support Services access is required.
System Action:
The function is terminated.
User Action:
Contact the System Administrator if the function is required.
Reason:
The requested action was cancelled by the user.
System Action:
None.
User Action:
None.
Reason:
The requested page number is not present in the current series of panels.
System Action:
The request is rejected.
User Action:
Correct the page number entered in the command line and retry.
Reason:
The field must not contain an ncl keyword.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The requested table entry was not found.
System Action:
None.
User Action:
None.
Reason:
A request was made to retrieve one or all entries from a table but the table did not have a type of 'TABLE'. The GET operation is not supported for other types of table.
System Action:
The request is rejected.
User Action:
None.
Reason:
The validation tables were successfully loaded into memory.
System Action:
None.
User Action:
None.
Reason:
More than 840 records were found as the result of a search for an INFO/MASTER field. The records were not displayed.
System Action:
None.
User Action:
Enter a partial field value for the search request which will reduce the number of matching records, and retry.
Reason:
The field value must be an IP Address. IPv4 addresses use a dotted decimal notation nnn.nnn.nnn.nnn where nnn can be a number from 0–255. IPv6 addresses use the form x:x:x:x:x:x:x:x where the x's are one to four hexadecimal digits. The alternative compressed format, for example, ::1 is also valid. Mixed IPv4 and IPv6 address notations are not allowed.
System Action:
None.
User Action:
Correct the entry and retry.
Reason:
The field value must conform to SQL rules which is a-z@#$ for the first character and a- z@#$_0-9 for the subsequent characters.
System Action:
None.
User Action:
Correct the entry and retry.
Reason:
The field value entered is invalid.
System Action:
None.
User Action:
Correct the field value and retry.
Reason:
The two fields are mutually exclusive, and only one or the other may be be entered.
System Action:
None.
User Action:
Erase one of the conflicting fields.
Reason:
A value must be entered for Field P1 if field P2 is present.
System Action:
None.
User Action:
Enter a value for the field in error, or erase field P2.
Reason:
A value must not be entered in P1 unless a value has been entered in field P1.
System Action:
None.
User Action:
Clear the field which is in error, or enter a value in the second field.
Reason:
This is a prompt message which is displayed to allow the user to verify that the selected record is to be deleted before the delete request is actioned.
System Action:
None.
User Action:
Press the ENTER key to allow the record to be deleted, or press the CANCEL key to cancel the delete request.
Reason:
A request was made to perform a function for a feature which is not configured in this region.
System Action:
The request is rejected.
User Action:
Contact the System Administrator if the feature is required.
Reason:
A request was made to add a Table Definition which already exists.
System Action:
The request is rejected.
User Action:
Correct the name of the field to be added and retry.
Reason:
A request was made to add a Table Entry which already exists.
System Action:
The request is rejected.
User Action:
Correct the value of the entry to be added and retry.
Reason:
A request was made to save or file a Table Entry with an abbreviated value has already been used for another entry in the same table.
System Action:
The request is rejected.
User Action:
Change the abbreviated value of the entry and retry.
Reason:
A request was made to add a Table Definition with a name which is an NCL keyword.
System Action:
The request is rejected.
User Action:
Change the name of the field to be added and retry.
Reason:
Function key P1 was pressed and the command assigned to it was invalid.
System Action:
The command is rejected.
User Action:
Correct the setting of the function key and retry.
Reason:
A Text Description field contains an invalid character. Certain characters are used internally by Validation Manager and therefore cannot be used in the Text Description fields.
System Action:
None.
User Action:
Remove any invalid characters from the field value and retry.
Reason:
The field value must be a valid HTTP URL commencing with http:// ...
System Action:
None.
User Action:
Correct the entry and retry.
Reason:
This field value must be a valid CA Service Desk Web Services URL.
This is the HTTP URL of the Web Services definitions on the CA Service Desk server. This server is where requests are created from alerts when you forward alerts to a SERVICEDESK destination.
In some cases, you can leave this value blank to let the CAISDI/soap component determine the default server.
This value must satisfy the following:
This URL points to the Web Services definitions that CAISDI/soap invokes to create requests. It is not the same as the URL that is used to log in to the CA Service Desk client application.
Example: http://hostname:8080/axis/services/USD_R11_WebService
System Action:
None.
User Action:
Correct the entry, and retry.
Reason:
The requested table entry has been deleted from the database by you or another user.
System Action:
None.
User Action:
The Refresh command can be used to remove deleted records from the list.
Reason:
The validation tables for the requested application are in use by another user.
System Action:
None.
User Action:
Retry the operation later.
Reason:
A request was made to load validation tables, but no table definitions were found on the database for the selected application.
System Action:
None.
User Action:
None.
Reason:
A request to present a field list failed because there were no attributes defined for the class. The ID of the class is P1 .
System Action:
The request is rejected.
User Action:
None.
Reason:
A request to present a field list failed because there were no attributes defined with IDs starting with the characters P1 . The ID of the class is P2 .
System Action:
The request is rejected.
User Action:
None.
Reason:
The select (S) command was entered on a valid value list, but the selected value did not match any of the full or (if present) abbreviated values in the list.
System Action:
None.
User Action:
Change the parameter on the select command so that it matches an existing value in the list.
Reason:
The select (S) command was entered on a valid value list, but the value to be selected was not entered.
System Action:
None.
User Action:
Enter the value of the entry to be selected.
Reason:
A request to issue a command to a z/VM node cannot be executed because the node was not identified using the NODE= operand.
The VMCMD command has the following format:
VMCMD NODE=nnnnnnnn CMD='command_text' WAIT=dd
System Action:
The command is not issued.
User Action:
Include the NODE= operand, and retry the command.
Reason:
A request to issue a command to a z/VM node cannot be executed because the z/VM command handler for this node is not running in the main task of Linux Connector.
p1 identifies the node.
System Action:
The command is not issued.
User Action:
Ensure that the z/VM agent is running and that the z/VM server servlet ($LXVMMON) has been started in the Linux Connector region.
Use the SERVERS command to display the current state of the Linux Connector servers:
F region_name,SERVERS
If the servlet has started, a message similar to the following is in the responses:
CAPKG032I Server VMMON socket registered on port 2608 servlet=$LXVMMON
Reason:
A VMCMD command was issued without the CMD= parameter.
System Action:
The command is rejected.
User Action:
Correct and retry the command.
Reason:
This message is the last response to commands issued through the VMCMD interface.
System Action:
None.
User Action:
None.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |