|
|
|
Reason:
A request to execute a Socket Management command was rejected because the background signon details have not been specified.
System Action:
Request rejected.
User Action:
Specify the background user ID and password to use in the ICS parameter group SOCKETMGMT and retry the request.
Reason:
A request to execute a Socket Management command was rejected because there was no target server specified.
System Action:
Request rejected.
User Action:
Specify a valid Socket Management Server.
Reason:
An APPC request to the remote system identified by P1 failed; the INMC link name P1 does not exist.
System Action:
The request is ignored.
User Action:
Use the SHOW LINKS command to verify INMC link names and status.
Reason:
An APPC request to the remote system identified by P1 failed; the INMC link name P1 is not active - the current status is P2.
System Action:
The request is ignored.
User Action:
Use the SHOW LINKS command to verify INMC link names and status.
Reason:
An APPC request to the remote system identified by P1 failed. The remote system is running a back-level version which does not support this type of request. The minimum requrment is P2.
System Action:
The request is ignored.
User Action:
None.
Reason:
An APPC request to the remote system identified by P1 failed with return code P2 and feedback code P3.
System Action:
An additional error message may be written to the activity log if RC=16.
User Action:
Contact your System Administrator.
Reason:
An attempt by Socket Management services to dynamically discover a resource failed. The resource name was P1 and the error message returned from the create was P2.
System Action:
Processing continues.
User Action:
Check the error message in P2.
Reason:
The user information needed by user P1 to signon to the SocketMgmt server P2 was reset/deleted.
System Action:
None
User Action:
None
Reason:
The requested command has been canceled.
System Action:
None
User Action:
None
Reason:
The field P1 must contain a value in the range P2 to P3 .
System Action:
None
User Action:
Correct the field value and retry.
Reason:
The field P1 must contain a value listed in P2 .
System Action:
None
User Action:
Correct the field value and retry.
Reason:
A serious logic error was encountered in a Socket Management server The name of the server is P1 and the error code is P2.
System Action:
The connection is terminated.
User Action:
Contact your local support representative.
Reason:
This is a trace message from NetMaster Socket Management Services.
System Action:
None.
User Action:
If tracing was requested by support, then gather all the related trace messages and send them to your support representative.
Reason:
An attempt to logon to a Socket Management command server failed. The name of the server is P1 and the reason for the error is P2.
System Action:
The connection is terminated.
User Action:
Check the reason and correct the authorization and/or configuration of the Socket Mangement server.
Reason:
An attempt to issue a Socket Management command was rejected because the command syntax was invalid. P1 is the server name, P2 is the command name and optionally the parameter in error, and P2 is the error condition.
System Action:
The command is rejected.
User Action:
Correct the syntax of the command and retry the request.
Reason:
A command request to Socket Management server P1 failed because the requested data for command P2 was not found.
System Action:
None.
User Action:
None.
Reason:
A command request for the Socket Management server P1 failed. The command requested was P2 and the reason code is P3.
System Action:
Processing for the specified command terminates.
User Action:
Correct the command and retry the request.
Reason:
An attempt to issue a Socket Management command was rejected because the SocketMgmt command server detected an error in the data sent to it. The error condition is P1 and the field in error is P2. P3 is the value of the field.
System Action:
The connection is terminated.
User Action:
Contact your local support representative.
Reason:
This message provides information about CICS SocketMgmt Command Entry. Command syntax information is presented in the Command Entry screen. Information includes commands available and relevant syntax.
System Action:
None.
User Action:
None.
Reason:
A command request to Socket Management server P1 failed because the requested port for command P2 is already in use.
System Action:
Processing for the specified command terminates.
User Action:
Correct the command and retry the request.
Reason:
A command request to Socket Management server P1 failed because the requested port for command P2 is not configured in T09CONFG member.
System Action:
Processing for the specified command terminates.
User Action:
Correct the command and retry the request.
Reason:
Command request P1 to Socket Management server P2 failed because of insufficient access authority.
System Action:
Processing for the specified command terminates.
User Action:
Notify your systems administrator.
Reason:
A Drop command was attempted on a Listener type connection without specifying TYPE=LISTENER.
System Action:
Processing for the specified command terminates.
User Action:
Correct the command and retry the request.
Reason:
A drop command was attempted on the Socket Management Command server. This action is not permitted.
System Action:
Processing for the specified command terminates.
User Action:
Correct the command and retry the request.
Reason:
An invalid call was made to the procedure. The keyword in error is identified by P1 and the value by P2 .
System Action:
None.
User Action:
Contact your System Administrator.
Reason:
An event receiver for the receiver ID identified by P1 has failed to start because there is an event receiver process active for the same receiver ID on this system.
System Action:
The event receiver stops.
User Action:
Check the activity log to search for previous SKEV25* messages which would indicate when the receiver was started.
Reason:
The define process for the event receiver whose receiver ID is P1 failed to start and the system entered a retry process. A request to stop the event receiver, and so cancel the retry process, has completed successfully.
System Action:
The event receiver is not defined and events will not be received.
User Action:
If the events are to be received, the event receiver must be restarted.
Reason:
The event receiver for the receiver ID ( P1 ) and event type ( P2 ) has started.
System Action:
The event receiver processes events of the specified type.
User Action:
None.
Reason:
The event receiver for the (EPS) receiver ID ( P1 ) did not connect to the Subsystem Interface (SSI). The reason that the connection was refused follows in message SKEV2508.
System Action:
The event receiver will not receive events using EPS.
User Action:
Refer to the refusal reason in message SKEV2508 which accompanies this message on the log. The most likely causes are:
- The Subsystem Interface (SSI) is inactive or does not support EPS. Refer to the NetMaster Installation and Implementation Instructions for information on how to set up the SSI. Ensure that EPS is correctly configured by including the following parameters:
XMEM=YES XAPI=YES XEVNT=YES
- The region has not connected to the correct SSI or it is not active. Issue the STATUS command and check the output for message N98601, which indicates the current status and subsystem ID. If there is no SSID, use the SYSPARM SSID command to connect to the SSI.
Reason:
This message accompanies message SKEV2507 when an EPS connection is refused. The refusal reason ( P1 ) is shown and will be either:
- Another message number - REFUSAL REASON UNAVAILABLE
System Action:
The event receiver will not receive events using EPS.
User Action:
Check the refusal reason:
- Refer to the description of the message in the reason. Also refer to the user actions described for message SKEV2507.
- REFUSAL REASON UNAVAILABLE indicates an internal error. (1) Check your maintenance tape to ensure that any APARs that relate to EPS are installed. (2) Perform the user actions described for message SKEV2507. (3) If the problem is not resolved, contact Technical Support.
Reason:
An event receiver for the P1 receiver ID has failed. The failure reason is detailed in message SKEV2510, which is written to the activity log along with this message.
System Action:
Message SKEV2510 includes one of the following types of EPS operation that failed:
The event receiver is not defined, and events are not received. The system is suspended for a time, and then the definition of the receiver will be tried again.
The EPS connection is closed and the process is suspended for 15 seconds, during which time events are not received. After this interval, the event receiver will attempt to connect to the SSI and any further errors are shown as for CONNECT.
The event receiver is terminated.
User Action:
Review the messages in the activity log. Message SKEV2510 includes the failure reason and the type of EPS operation that failed.
Use the feedback reason to determine why the event receiver failed:
These reasons indicate that the SSI (that this region is connected to) does not provide EPS event support because of one of the following reasons:
This usually indicates that you have not connected this region to the correct SSI.
EPS event support is provided by the XEVNT=YES SSI parameter.
This indicates that the connection to the SSI has been lost. This may occur if the SOLVESSI started task is terminated or the region is disconnected from the SOLVESSI because the SSID parameter has been reset.
Use the SHOW SYSPARM=SSID command to determine the SSID value. Ensure that the correct SSID is specified and that the SOLVESSI started task is active. Use the SSI STATUS command to verify the status of the SSI started task.
For a particular type of EPS operation, you can perform certain actions:
The event receiver, suspended in retry mode, may be canceled by stopping the receiver.
The event receiver may be restarted if required.
Note: Stopping or restarting the receiver should only be done under guidance from your system administrator or Technical Support.
List this region's configuration details (/IPTEST), and investigate any errors.
Reason:
This message follows message SKEV2509 and provides the EPS operation type ( P1 ), failure code ( P2 ), and reason ( P3 ).
System Action:
Refer to message SKEV2509.
User Action:
Refer to message SKEV2509.
Reason:
The object P1 was not found.
System Action:
None.
User Action:
None.
Reason:
Object P1 already exists.
System Action:
None.
User Action:
None.
Reason:
An error occurred while manipulating a VARTABLE in the procedure $SKCALL. 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:
A logic error has been detected in NetMaster Socket Management processing. This is the OML code that runs in the NetMaster region and establishes and maintains IP socket connections with the socket application server. The specific connection call was P1.
System Action:
The request is terminated.
User Action:
Ensure that the socket application being contacted is still active.
Reason:
An attempt to logon to Socket Management server P1 failed. The request timed out.
System Action:
The request is terminated.
User Action:
Check the log for additional messages.
Reason:
An error occurred trying to logon to a Socket Management server. The server name was P1 and the error message returned was P2.
System Action:
The request is terminated.
User Action:
Check the reason for the error and check the log for additional error messages.
Reason:
An error occurred trying to logon to a Socket Management server P1. The server IP address and port have not been discovered.
System Action:
The request is rejected.
User Action:
Take the appropriate action for the cause:
1) The CICS region is not running Start the CICS region and the IP address and port of the server will be dynamically discovered.
2) The SocketMgmt CICS Exit is not installed See the installation instructions on how to install the SocketMgmt Exit. Without this exit SocketMgmt cannot function correctly.
3) The SocketMgmt CICS Exit has abended Contact your local support representative.
Reason:
The SPROC keyword parameter was not specified on the call to the Selection List Manager.
System Action:
The call is rejected.
User Action:
Correct the call parameters and retry.
Reason:
The service procedure specified on the call to the Selection List Manager was not found in the NCL procedure library.
System Action:
The call is rejected.
User Action:
Correct the service procedure name or create the procedure in the NCL procedure library and retry.
Reason:
No data was found for display on the selection list.
System Action:
The Selection List call is terminated.
User Action:
None.
Reason:
This is a prompt message which is displayed to allow the user to verify that the selected actions are correct before they are carried out.
System Action:
None.
User Action:
Press the ENTER key to execute the highlighted selections, or press the CANCEL function key to cancel the requested actions.
Reason:
You specified an invalid scroll amount. Valid scroll amounts are CSR, PAGE, MAX, HALF, DATA, or a number. You only need to enter the first character, for example, P for PAGE. MAX is valid only when entered at the command prompt.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Enter a valid value in the scroll field.
Reason:
The operand specified with the find command was invalid. Some valid operands are FIRST, NEXT, PREV and LAST.
System Action:
The Find command is rejected.
User Action:
Correct the parameters on the Find command and retry.
Reason:
A selection list can only be displayed in a fullscreen 3270 environment.
System Action:
The command is not processed.
User Action:
None.
Reason:
The selected entry number does not exist.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Specify a valid entry number or press the Exit function key to cancel the selection.
Reason:
An invalid scroll value was specified. When scrolling to the left or right, the only values allowed are 'M', 'MAX' or a number.
System Action:
The scroll request is rejected.
User Action:
Correct the scroll value and retry.
Reason:
An unsupported return code was set by a selection list service procedure. The calltype was P2 , and the name of the service procedure was P3 .
System Action:
None.
User Action:
Correct the return code set by the Selection List Service Procedure.
Reason:
An unrecognized shortcut or selection list command was entered.
System Action:
None.
User Action:
Enter a valid shortcut, menu option, panel path, or command.
SHORTCUTS
Enter a shortcut name, preceded by a slash, at the ===> prompt (for example, /levels or /info or /ipmon).
This will take you directly to the function.
To see a list of all shortcuts and their associated functions, enter a single slash (/) at the ===> prompt.
Select the desired shortcut from the list by entering 'S' beside it.
If a shortcut exists for a menu option, it is displayed in turquoise, to the right of the option description.
Shortcuts may also be combined with menu options (for example, /bcast.s or =/bcast.s).
Shortcuts can be invoked in two ways:
1. A 'nested' shortcut
2. A shortcut skip
To retain and nest the current screen level, use a nested shortcut:
/shortcut_name
Exit will bring you back to the last nested screen in this window. Screens may be nested to a maximum of 64 levels.
To close all currently nested screen levels, use a shortcut skip:
=/shortcut_name
Exit will take you back to the Primary Menu.
If you no longer need any nested screens, a shortcut skip saves storage and resources.
(If you are currently at the Primary Menu, a nested shortcut and a shortcut skip behave the same.)
MENU OPTION
Each menu option is identified by a 1 to 3 character option string, displayed in yellow. Enter the option you want at the ===> prompt.
PANEL PATH
Like shortcuts, panel paths move directly to a function without having to access each submenu between it and the current menu.
A panel path consists of multiple menu options separated by periods (for example =U.M).
Also like shortcuts, the = sign functions as a skip character, closing all nested screens and effectively entering the path from the primary menu. (If you are currently at the Primary Menu, the skip character is not required.)
Frequently used panel paths have associated shortcuts.
If you don't remember a shortcut, enter / at the ===> prompt for a list.
Select one from the list, or enter it at the ===> prompt.
There is no difference between accessing a function using a panel path skip or a shortcut skip, although the shortcut should be easier to remember. Both close the current screen and go straight to the function.
Entering == at the ===> prompt from any panel closes all nested screens and returns you to the Primary Menu.
Reason:
P1 records were searched for the specified string but the string was not found. Press the FIND key to continue the search.
System Action:
None.
User Action:
Press the FIND function key if you wish to continue the search.
Reason:
The text string specified in the FIND command was found. The cursor is positioned at the beginning of the text string.
System Action:
None.
User Action:
None.
Reason:
The locate command was entered, but no record id was specified.
System Action:
The command is rejected.
User Action:
Re-enter the Locate command specifying the partial or full record id which is to be located.
Reason:
The scroll amount that was specified was too large. The scroll amount must be in the range 1 to 99999.
System Action:
The scroll request is rejected.
User Action:
Re-enter the scroll command specifying a valid scroll amount.
Reason:
The select option specified was invalid.
System Action:
The cursor is placed in the field in error and the field is highlighted.
User Action:
Correct the selection option and retry. Valid options are usually displayed above the first list entry.
Reason:
The bottom of data was reached when trying to find a string specified with the Find command.
System Action:
None.
User Action:
To continue the search press the Find function key. The search will continue from the top of the list.
Reason:
The top of the data was reached when trying to find a string specified with the Find command.
System Action:
None.
User Action:
To continue the search press the FIND function key. The search will continue from the bottom of the selection list.
Reason:
An asterisk (*) was entered as a parameter for the find command, but no previous find command has been entered. When an asterisk is entered as the character string for a find command, the character string from the last find command issued is used. If a literal asterisk is to be found, it should be entered in quotes (ie: '*').
System Action:
The Find command is rejected.
User Action:
Re-enter the Find command specifying a valid character string.
Reason:
This is a prompt message which is displayed to allow the user to verify that the selected records are to be deleted before the delete request is actioned.
System Action:
None.
User Action:
Press the ENTER key to action the delete request, or press the CANCEL function key to cancel the delete request.
Reason:
An error occurred when processing a VARTABLE.
System Action:
None.
User Action:
Determine the cause of the error from the return and feedback codes and retry.
Reason:
The selection list service procedure P1 has set an invalid value in the variable &$SLOPTIONS.
System Action:
The selection list is terminated.
User Action:
Correct the service procedure and retry.
Reason:
There is only one entry that can be selected from the list. The entry number that you specified is invalid.
System Action:
The selection request is rejected.
User Action:
Specify a valid entry number.
Reason:
The selection list service procedure was called with call type P1 from the Selection List Manager but it does not support that call type.
System Action:
The selection list is terminated.
User Action:
Fix the service procedure so that it supports the calltype.
Reason:
The selection list service procedure was called with an option which it does not support.
System Action:
None.
User Action:
Fix the service procedure so that it supports the selection or remove the select value from $SLOPTIONS.
Reason:
An unrecognized command was entered.
System Action:
None.
User Action:
Enter a valid menu option, panel path, or command.
Menu Option is identified by a one- to three-character string, displayed in yellow. Enter the option you want at the ===> prompt.
Panel Path enables you to move directly to a function without having to access each submenu between it and the current menu. A panel path consists of multiple menu options separated by periods (for example, A.C.P).
The = sign functions as a skip character, closing all nested screens and effectively entering the path from the primary menu. (If you are currently at the primary menu, the skip character is not required.)
Entering == at the ===> prompt from any panel closes all nested screens and returns you to the primary menu.
Reason:
The Find command could not be actioned because no character string was entered.
System Action:
The Find command is rejected.
User Action:
Re-enter the Find command specifying the character string to be found.
Reason:
The Locate command is not supported on this selection list.
System Action:
The Locate command is rejected.
User Action:
You must scroll up/down to find the desired record(s).
Reason:
Selection List Manager 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 Selection List Manager terminates.
User Action:
Correct the NCL procedure which executed List Handler.
Reason:
The maximum number of entries that could be selected on a select type list was exceeded. The maximum was P1 .
System Action:
The List is redisplayed.
User Action:
Correct the number of entries selected to be less than or equal to the maximum and retry.
Reason:
A Default option was set by the list service procedure, but the default option is not a valid select option for the list. P1 is the default option set by the service procedure.
System Action:
The list is not displayed.
User Action:
Correct the services procedure by erasing the default option or changing it to a valid option.
Reason:
The selection list service procedure P1 has set an invalid value P2 in the variable &$SLFNDMODE. The only valid value is ALL or null. The default is null.
System Action:
The selection list is terminated.
User Action:
Correct the service procedure, and retry.
Reason:
The selection list service procedure P1 has set an invalid value P2 in the variable &$SLFNDPROMPT. The valid values are NO , any unsigned integer between 100 and 2147483647, and null. The default is null.
System Action:
The selection list is terminated.
User Action:
Correct the service procedure, and retry.
Reason:
The P1 has been restored to its default setting, which is set by the service procedure.
System Action:
None.
User Action:
None.
Reason:
The operand P1 specified with the RESET command was invalid. Valid operands are:
ALL restores the default FMODE and FPROMPT settings. This is the default.
FMODE restores the default FMODE setting.
FPROMPT restores the default FPROMPT setting.
System Action:
The RESET command is rejected.
User Action:
Correct the operand on the RESET command, and retry.
Reason:
The operand P1 specified with the FMODE command was invalid. Valid operands are:
ALL enables the FIND command to search beyond the currently displayed columns.
DEFAULT or DFLT restores the default FMODE setting.
NORMAL or NORM restricts the FIND command to search the displayed columns only.
null displays the current FMODE setting.
System Action:
The FMODE command is rejected.
User Action:
Correct the operand on the FMODE command, and retry.
Reason:
The current selection list setting for P1 is P2 .
System Action:
None.
User Action:
None.
Reason:
The selection list setting P1 has been set to P2 .
System Action:
None.
User Action:
None.
Reason:
The operand P1 specified with the FPROMPT command was invalid. Valid operands are:
100 to 2147483647 specifies the number of records to search for before a progress message is displayed.
DEFAULT or DFLT restores the default FPROMPT setting.
NO specifies that no progress messages be displayed until the bottom or top of the searched data has been reached.
NORMAL or NORM sets the number of records to search for to 50 .
null displays the current FPROMPT setting.
System Action:
The FPROMPT command is rejected.
User Action:
Correct the operand on the FPROMPT command, and retry.
Reason:
The text string specified in the FIND command was not found.
System Action:
None.
User Action:
For a multi-panel list, issue FMODE ALL to scan all panels for the text string.
Reason:
The value P1 is invalid and cannot be processed.
System Action:
None
User Action:
Either enter a new value or ignore.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |