Reason:
You issued the ATF LOAD command and the requested translation table has been loaded successfully.
System Action:
None.
User Action:
None.
Reason:
You issued the ATF LOAD command but the requested translation table could not be loaded.
The preceding error messages describe the problem.
System Action:
The requested table is not loaded.
User Action:
Review the preceding error messages and correct the problem. Then reissue the ATF LOAD command.
Reason:
You issued the ATF UNLOAD command and the requested translation table has been unloaded successfully.
System Action:
None.
User Action:
None.
Reason:
You issued the ATF UNLOAD command and the requested translation table could not be unloaded.
The preceding error messages describe the problem.
System Action:
The requested table is not unloaded.
User Action:
Review the preceding error messages and correct the problem. Then reissue the ATF UNLOAD command.
Reason:
You issued the ATF DEFINE command and the named translation table has been defined.
System Action:
None.
User Action:
The named table can now be used when requesting ATF translation services.
Reason:
You issued an ATF command but the named table has an encoding type that is algorithmic. Only translation names defined as table-based can be manipulated by the ATF command.
System Action:
The command is ignored.
User Action:
Correct the table name and, if relevant, reissue the command.
Reason:
You issued the ATF LOAD command but the named table is already loaded.
System Action:
The command is ignored.
User Action:
If you wish to reload the table after changing the related load modules, first issue an ATF UNLOAD command, then reissue the ATF LOAD command.
Reason:
You issued the ATF UNLOAD command but the named table is not loaded.
System Action:
The command is ignored.
User Action:
Probably none. The table does not need to be unloaded.
Reason:
You issued the ATF command but the supplied table name is invalid.
System Action:
The command is ignored.
User Action:
Check that the correct table name has been supplied. If you are issuing an ATF DEFINE command, these conditions apply:
- The table name is from 1 to 16 characters long,
- The first character is alphabetic or national (@#$),
- The remaining characters are alphanumeric, national, or the underscore.
Reason:
You issued an ATF command but the named table does not exist.
System Action:
The command is ignored.
User Action:
Correct the table name and reissue the command. To obtain a list of known table names, use the SHOW ATF command.
Reason:
You issued an ATF DEFINE command but there are no slots left for defining new tables.
System Action:
The command is ignored.
User Action:
If you need to define additional ATF translation tables, contact Technical Support for assistance.
To determine the number of available free slots, issue a SHOW ATF command. The last line indicates how many free slots are still available. (The distributed product has four.)
Reason:
You issued an ATF DEFINE command but the named table already exists.
System Action:
The command is ignored.
User Action:
Choose a new unique table name and reissue the command.
Reason:
You issued an ATF DEFINE command but the supplied encoding name is invalid.
System Action:
The command is ignored.
User Action:
Supply a valid encoding name.
To determine encoding names, issue a SHOW ATF ENCODING command. Only 'TABLE' type encoding names can be used with ATF DEFINE.
Reason:
You issued the ATF DEFINE command but the supplied encoding name is not recognised.
System Action:
The command is ignored.
User Action:
Supply a valid known encoding name.
To determine encoding names, issue a SHOW ATF ENCODING command. Only 'TABLE' type encoding names can be used with ATF DEFINE.
Reason:
This is the heading message for a SHOW ATF command. The column headings are:
TABLE NAME This column contains the name of the translation table (that is, the name that can be used in NCL verbs, and so on).
ENCODING NAME This column shows the name of the encoding technique used by this table.
TYP This column will contain either 'ALG', or 'TAB'. ALG means that this is an algorithmic encoding type (that is, conversion to/from Unicode uses an algorithm). 'TAB' means that this is a table-driven encoding type (that is, conversion to/from Unicode uses a table).
LOAD For 'TAB' types, this indicates whether the tables have been loaded into storage.
PRI-LM For 'TAB' types, this indicates the primary conversion tables load module name.
SEC-LM For 'TAB' types, this indicates the secondary conversion tables load module name.
OFST The allocated Unicode table entry offset (hex)
INDX The allocated slot index for this table
System Action:
None.
User Action:
None.
Reason:
This is the detail message for a SHOW ATF command. Refer to message NT0410 for an explanation of column headings.
System Action:
None.
User Action:
None.
Reason:
This is the final message for a SHOW ATF command. The number of free table entries is displayed.
System Action:
None.
User Action:
None.
Reason:
This is the first message for a SHOW ATF TABLE=tttt command. It is the start of information for this display.
System Action:
None.
User Action:
None.
Reason:
This is an information message for a SHOW ATF TABLE=tttt command. The encoding name, internal code, and general type (TABLE or ALGORITHMIC) are shown.
System Action:
None.
User Action:
None.
Reason:
This is an information message for a SHOW ATF TABLE=tttt command. The primary table load module name is displayed.
System Action:
None.
User Action:
None.
Reason:
This is an information message for a SHOW ATF TABLE=tttt command. The secondary table load module name is displayed.
System Action:
None.
User Action:
None.
Reason:
This is an information message for a SHOW ATF TABLE=tttt command. The UNICODE table entry offset for this table is displayed.
System Action:
None.
User Action:
None.
Reason:
This is an information message for a SHOW ATF TABLE=tttt command. The internal table slot index for this table is displayed.
System Action:
None.
User Action:
None.
Reason:
This is an information message for a SHOW ATF TABLE=tttt command. The current table load status is shown. Values are: NOT LOADED - The table has not been loaded. LOADED - The table has been successfully loaded. LOAD FAILED - The table load failed.
System Action:
None.
User Action:
None.
Reason:
This is an information message for a SHOW ATF TABLE=tttt command. The date and time that the table was loaded into storage are shown.
System Action:
None.
User Action:
None.
Reason:
This is an information message for a SHOW ATF TABLE=tttt command. The substitution character values for single-byte and double-byte replacement are shown (in hex). These values are used during conversion to this character set when the source character has no equivalent in this character set.
System Action:
None.
User Action:
None.
Reason:
This is an information message for a SHOW ATF TABLE=tttt command. The date and time that a table module was compiled (by the NMBLDXLT program) are displayed. The TYPE field will be (PRIMARY) or (SECONDARY), indicating which module date/time is displayed.
System Action:
None.
User Action:
None.
Reason:
This is an information message for a SHOW ATF TABLE=tttt command. The amount of additional storage for double-byte translation lookup tables is shown (in Kbytes). Note that tables that only contain single-byte conversions will have 0K for this value.
System Action:
None.
User Action:
None.
Reason:
This is an information message for a SHOW ATF TABLE=tttt command. This message indicates which of the four tables of a specific type (SINGLE or DOUBLE) is defined for this translation table. Each indicator is Y or N.
System Action:
None.
User Action:
None.
Reason:
This is the heading message for a SHOW ATF ENCODING command. The column headings are:
ENCODING NAME The encoding name that this line describes.
CODE The internal code assigned to this encoding name.
TYPE The encoding type, either 'ALG' or 'TAB'. 'ALG' means that this is an algorithmic encoding type (that is, conversion to/from Unicode uses an algorithm) 'TAB' means that this is a table-driven encoding type (that is, conversion to/from Unicode uses a table).
SB1 Indicates (for 'TAB' types) whether the single-byte conversion table 1 is required or optional.
SB2 As for SB1, for single byte table 2
SB3 As for SB1, for single byte table 3
SB4 As for SB1, for single byte table 4
DB1 Indicates (for 'TAB' types) whether the double-byte conversion table 1 is required or optional.
DB2 As for DB1, for double byte table 2
DB3 As for DB1, for double byte table 3
DB4 As for DB1, for double byte table 4
System Action:
None.
User Action:
None.
Reason:
This is the detail message for a SHOW ATF ENCODING command. Refer to message NT0450 for an explanation of column meanings.
System Action:
None.
User Action:
None.
Reason:
This message is issued in response to a SHOW ATF command when the supplied table name is invalid.
System Action:
The command is ignored.
User Action:
Correct the table name and reissue the command.
Reason:
This message is issued by the OML CSCONV function if an output string area overflow occurred during execution of the translation.
System Action:
An OML ERROR is raised.
User Action:
Reduce the length of the input string. CSCONV supports a maximum output size of 64K. Some input strings and conversion types can result in an output string that is much longer than the input string.
Reason:
This message is issued by the OML CSCONV function if a syntax error was detected in the input string to be converted.
The offset in the input where the error was detected is also shown. This offset may precede the actual error point.
The syntax errors are:
2 - A double-byte string (or substring) was not an even length.
3 - Invalid input character for current mode or character set (that is, the definition of the character set prohibits the value)
4 - Input exhausted unexpectedly, for example, in the middle of a shift sequence.
5 - UNICODE surrogate pair error (First or second of pair is missing. Only detected if output is UTF8)
6 - Invalid shift sequence
7 - Truncated shift sequence
System Action:
An OML ERROR is raised.
User Action:
Examine the input data and determine why the error occurred.
Reason:
This message is issued by the OML CSCONV function if an invalid or unknown translation table name is supplied.
iiiiii is the table type (INPUT or OUTPUT). tttttt is the supplied table name.
System Action:
An OML ERROR is raised.
User Action:
Check the names of the tables used. (The SHOW ATF command shows the valid names.)
Reason:
This message is issued by the OML CSCONV function if a requested translation table failed to load.
iiiiii is the table type (INPUT or OUTPUT). tttttt is the supplied table name.
There will be messages on the SOLVE log describing the load failure problem.
System Action:
An OML ERROR is raised.
User Action:
Check the SOLVE log for load failure messages (NT11?? messages). Take corrective action as required.
Reason:
The ATF table loader issues this message when a basic error in the translation table load process occurs.
The table name is shown.
The errors are:
The primary load module, as defined in the table definition (use SHOW ATF TABLE=tttttt), could not be loaded.
The secondary load module, as defined in the table definition (use SHOW ATF TABLE=tttttt), could not be loaded.
The required conversion tables, as required by the encoding name for this table, were not all present in the primary and secondary load modules.
Insufficient storage was available.
System Action:
The ATF translation table load fails. This failure can cause an NCL conversion request to fail.
User Action:
Correct the problem based on the error description.
Reason:
This message is issued by the ATF table loader when an error in the translation table load process occurs.
The table name is shown. The name of the load module being processed is shown.
The errors are described below.
TABLE HEADER ERROR: eeeeeeeeeee An error in the load module table header was detected. Errors indicate a problem with the table header. The errors are:
HEADER VALIDATION ERROR 1 HEADER VALIDATION ERROR 2 HEADER VALIDATION ERROR 3 HEADER VALIDATION ERROR 4
ENCODING NAME MISMATCH The encoding name in the table does not match the encoding name in the load module.
SINGLE TABLE n ERROR: eeeeeeeee An error in a single-byte table (n indicates the number, 1 to 4), was detected. The errors are:
EYECATCHER INVALID The internal eyecatcher was invalid.
INTERNAL TABLE CODE WRONG The internal table code was not the expected code.
NO ENTRIES There are no entries in the table.
TOO MANY ENTRIES There are too many entries in the table (> 256).
DOUBLE TABLE n ERROR: eeeeeeeee An error in a double-byte table (n indicates the number, 1 to 4) was detected. The errors are:
EYECATCHER INVALID The internal eyecatcher was invalid.
INTERNAL TABLE CODE WRONG The internal table code was not the expected code.
NO ENTRIES
TOO MANY ENTRIES There are too many entries in the table (> 256).
System Action:
The ATF translation table load fails. This may cause an NCL conversion request to fail.
User Action:
Correct the problem based on the error description.
Reason:
This message is issued by the ATF table loader when it detects that two single-byte translation tables map the same Unicode to two different single-byte codes.
For example, single byte table 1 may map input character X'45' to Unicode entry X'0045', but single byte table 2 may map input character X'C1' to Unicode entry X'0045'.
This cannot be handled by the present ATF design.
Note: Different translation tables can of course map different characters to the same Unicode (to facilitate conversion). However, for character sets with multiple modes (for example, EUC, or JIS7) where escape sequences switch between modes, ATF presently disallows different single-bytes mapping to the same Unicode.
System Action:
The ATF translation table load fails. This may cause an NCL conversion request to fail.
User Action:
Correct the translation tables to remove the overlap.
Reason:
This message is issued by the ATF table loader when it detects that two double-byte translation tables map the same Unicode to two different double-byte codes.
For example, double byte table 1 may map input character X'4545' to Unicode entry X'6578', but double byte table 2 may map input character X'A2C1' to unicode entry X'6578'.
This cannot be handled by the present ATF design.
Note: Different translation tables can of course map different characters to the same Unicode (to facilitate conversion). However, for character sets with multiple modes (for example, EUC, or JIS7) where escape sequences switch between modes, ATF presently disallows different double-bytes mapping to the same Unicode.
System Action:
The ATF translation table load fails. This may cause an NCL conversion request to fail.
User Action:
Correct the translation tables to remove the overlap.
Reason:
This message is issued by the ATF translation table compiler to indicate that it is starting a compilation.
System Action:
Compilation commences.
User Action:
None.
Reason:
This message is issued by the ATF translation table compiler to display an input line when an error is detected.
The error message will follow.
System Action:
Error messages related to this line follow.
User Action:
Examine the error message(s).
Reason:
This message is issued by the ATF translation table compiler to indicate that end-of-file was detected on the input file.
System Action:
Compilation proceeds.
User Action:
None.
Reason:
This message is issued by the ATF translation table compiler to indicate that it is proceeding to generate the named translation table, and the load module name.
System Action:
Compilation proceeds.
User Action:
None.
Reason:
This message is issued by the ATF translation table compiler to indicate that it has completed table generation.
System Action:
Compilation finishes.
User Action:
None.
Reason:
This message is issued by the ATF translation table compiler to indicate that it found statements in the source after the 'END TABLE' statement.
System Action:
Compilation terminates.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), is not a valid statement.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), is not valid between a START and END sequence.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), is duplicated. (For example, two MODULE statements were found.)
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), has invalid data after the valid operand(s).
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), a 'START' statement, has an unrecognised operand. The operand must be 'SINGLE' or 'DOUBLE' and a number from 1 to 4.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), a 'START' statement, was not preceded by an 'ENCODING' statement. This is a fatal error.
System Action:
Compilation terminates.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), an 'END' statement, has an unrecognised operand. The operand must be 'SINGLE', 'DOUBLE', or 'TABLE'.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), a 'NAME' statement, is not valid.
The reasons it can be invalid are:
- No table name was supplied. - The table name is too long (more than 16 characters). - The table name is invalid. (First character must be alpha or national, the remainder must be alphanumeric, national, or underscore.)
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), an 'ENCODING' statement, is not valid.
The reasons it can be invalid are:
-No encoding name was supplied.
-The encoding name is too long (more than 16 characters).
-The encoding name is invalid. (First character must be alpha or national, the remainder must be alphanumeric, national, or underscore.)
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), an 'MODULE' statement, is not valid.
The reasons it can be invalid are:
- No module name was supplied.
- The module name is too long (more than 8 characters).
- The module name is invalid. (First character must be alpha or national, the remainder must be alphanumeric or national.)
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), a 'SINGLE_SUB' statement, is not valid.
The reasons it can be invalid are:
- No value was supplied.
- The value was not two characters long, or the characters were not valid hexadecimal digits (0-9 or A-F).
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), a 'DOUBLE_SUB' statement, is not valid.
The reasons it can be invalid are:
- No value was supplied.
- The value was not four characters long, or the characters were not valid hexadecimal digits (0-9 or A-F).
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), an 'ENCODING' statement, is not valid.
The reasons it can be invalid are:
- The encoding name was not found in the table of valid encoding names.
- The encoding name was found, but the encoding type is 'algorithmic' (Only 'table' encoding types are valid.)
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), a 'START SINGLE' statement, has an invalid table number after it. The value must be 1 to 4.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), a 'START SINGLE' statement, has a table number that has already been seen.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), a 'START SINGLE' statement, has an invalid option after the table number. The only valid option is 'REPLACE'.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), a 'START SINGLE' statement, has a table number that is not allowed for the encoding name specified.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), a code/Unicode map statement (for a single table), has a duplicate source value. This source value has already appeared on an earlier statement.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), an 'END SINGLE' statement, is not valid, as no single table is presently being processed.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), an 'END SINGLE' statement, terminates a single table, but there were no mapping statements after the 'START SINGLE' statement.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), a 'START DOUBLE' statement, has an invalid table number after it. The value must be 1 to 4.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), a 'START DOUBLE' statement, has a table number that has already been seen.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), a 'START DOUBLE' statement, has an invalid option after the table number. The only valid option is 'REPLACE'.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), a 'START DOUBLE' statement, has a table number that is not allowed for the encoding name specified.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), a code/Unicode map statement (for a double table), has a duplicate source value. This source value has already appeared on an earlier statement.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), an 'END DOUBLE' statement, is not valid, as no double table is presently being processed.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the displayed statement (previous print line, MSG NT3002), an 'END DOUBLE' statement, terminates a double table, but there were no mapping statements after the 'START DOUBLE' statement.
System Action:
Compilation proceeds for error checking purposes only.
User Action:
Correct the error and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that the JCL PARM value is invalid.
The position where invalid data was detected is displayed.
System Action:
The compiler immediately terminates.
Note that this message will be WTO'd, as no files are open yet.
User Action:
Correct the parameter error.
Reason:
This message is issued by the ATF translation table compiler to indicate that an unrecognised JCL PARM option was found.
The invalid parm is displayed.
System Action:
The compiler immediately terminates.
Note that this message will be WTO'd, as no files are open yet.
User Action:
Correct the parameter error.
Reason:
This message is issued by the ATF translation table compiler to indicate that a duplicated JCL PARM option was found.
The invalid parm is displayed.
System Action:
The compiler immediately terminates.
Note that this message will be WTO'd, as no files are open yet.
User Action:
Correct the parameter error.
Reason:
This message is issued by the ATF translation table compiler to indicate that the JCL PARM 'IN' option had an invalid ddname value.
The invalid value is displayed.
System Action:
The compiler immediately terminates.
Note that this message will be WTO'd, as no files are open yet.
User Action:
Correct the parameter error.
Reason:
This message is issued by the ATF translation table compiler to indicate that the JCL PARM 'OUT' option had an invalid ddname value.
The invalid value is displayed.
System Action:
The compiler immediately terminates.
Note that this message will be WTO'd, as no files are open yet.
User Action:
Correct the parameter error.
Reason:
This message is issued by the ATF translation table compiler to indicate that the JCL PARM 'PRINT' option had an invalid ddname value.
The invalid value is displayed.
System Action:
The compiler immediately terminates.
Note that this message will be WTO'd, as no files are open yet.
User Action:
Correct the parameter error.
Reason:
This message is issued by the ATF translation table compiler to indicate that it was unable to open the indicated file.
System Action:
The compiler immediately terminates.
Note that this message may be WTO'd, depending on which file cannot be opened.
User Action:
Refer to the job log for other error messages (for example, missing ddname). Correct the error and rerun the compiler.
Reason:
This message is issued by the ATF translation table compiler to indicate that after processing all input, no 'NAME' statement was found.
System Action:
Compilation terminates.
User Action:
Add a NAME statement and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that after processing all input, no 'ENCODING' statement was found.
System Action:
Compilation terminates.
User Action:
Add an ENCODING statement and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that after processing all input, no 'MODULE' statement was found.
System Action:
Compilation terminates.
User Action:
Add a MODULE statement and recompile the table.
Reason:
This message is issued by the ATF translation table compiler to indicate that it was unable to load module NM072002, which contains the encoding names table.
System Action:
Compilation terminates.
User Action:
Ensure that the SOLVE load library is available to the compiler job.
Reason:
This message is issued by the ATF translation table compiler to indicate that the validation of the NM072002 module failed. An error code is displayed.
System Action:
Compilation terminates.
User Action:
Contact Technical Support.
Reason:
This message is issued by the ATF translation table compiler to indicate that, due to previous errors, generation of the assembler source for the translation table has been suppressed.
System Action:
Compilation terminates.
User Action:
Correct the previous errors.
Reason:
The interface that enables communication with CA NetSpy has been initialized.
System Action:
None
User Action:
None
Reason:
This message is produced during NetMaster initialization, if the NETSPY interface cannot be initialized.
If the VTAM access method has been omitted (via the AM=... JCL PARM), then the NETSPY interface has no way of communicating.
System Action:
The NETSPY interface is not initialized.
User Action:
Normally, none. It is not normal to omit VTAM as an access method.
Reason:
This message indicates that a SHOW NETSPY command was successfully processed. The command option is shown.
System Action:
None
User Action:
None
Reason:
This message commences the output of a SHOW NETSPY CONN command.
System Action:
None
User Action:
None
Reason:
This message is the first heading of a SHOW NETSPY CONN command. It contains the column headings for the NT5413 message, as follows:
CONN-NAME - Shows the value of the NSYXNAME parameter in the INITPRM member of each NetSpy linked to this region.
APPL - Shows the VTAM application name for each NetSpy.
STATUS - Shows the current status of each NetSpy link.
PEND-STATUS - Shows the pending (desired) status of each NetSpy link.
ACT-DATE - Shows the date when each NetSpy link was activated.
ACT-TIME - Shows the time when each NetSpy link was activated.
System Action:
None.
User Action:
None.
Reason:
This message is the second heading of a SHOW NETSPY CONN command. It contains the column headings for the NT5414 message, as follows:
INFORMATION - Shows the internally generated link name for each NetSpy linked to your region.
PRI-ACB - Shows the ACB name of each NetSpy.
VERSION - Shows the version of each NetSpy.
SYSNAME - Shows the local identifier of the region, as set at system initialization.
INTERVAL - Shows the time between retries when connecting NetSpys.
SYNC - Shows the NetSpy SYNC initialization value.
ALTBITVL - Shows the NetSpy ALTBITVL initialization value.
RETRY - Shows the current retry number and maximum number of retries for a given link.
System Action:
None.
User Action:
None.
Reason:
This message is the first detail line of a SHOW NETSPY CONN command. It contains information about a NETSPY connection. Refer to message NT5411 for column headings.
System Action:
None
User Action:
None
Reason:
This message is the second detail line of a SHOW NETSPY CONN command. It contains additional information about a NETSPY connection. Refer to message NT5412 for column headings.
System Action:
None
User Action:
None
Reason:
This message commences the output of a SHOW NETSPY USERS command.
System Action:
None
User Action:
None
Reason:
This message is the first heading of a SHOW NETSPY USERS command. It contains the column headings for the NT5423 message, as follows:
USERID - Shows the user ID using NetSpy.
NCLID - Shows the NCL is of the procedure using NetSpy.
BASEPROC - Shows the name of the current procedure using NetSpy.
LAST-ID - Shows the NetSpy link identifier last used.
System Action:
None.
User Action:
None.
Reason:
This message is the second heading of a SHOW NETSPY USERS command. It contains the column headings for the NT5424 message, as follows:
REQ-ID - Shows the value of the correlator
ID-NAME - Shows the value of unique request identifier
TGT-NETSPY - Shows the name of the target NetSpy
System Action:
None.
User Action:
None.
Reason:
This message is the first detail line of a SHOW NETSPY USERS command. It contains information about a NETSPY connection user (process). Refer to message NT5421 for column headings.
System Action:
None
User Action:
None
Reason:
This message is the second detail line of a SHOW NETSPY USERS command. It contains information about defined commands for the user. Refer to message NT5422 for column headings.
System Action:
None
User Action:
None
Reason:
This message commences the output of a SHOW NETSPY DEF command. It shows NetSpy command requests currently active.
System Action:
None
User Action:
None
Reason:
This message is the first heading of a SHOW NETSPY DEFS command. It contains the column headings for the NT5433 message, as follows:
DEF-ID - Shows the correlator for this command request definition.
TERMNAME - Shows logical terminal name for this command request.
USERID - Shows the ID of the user that defined the request.
REQ-ID - Shows unique request identifier.
NCLID - Shows NCL ID of the procedure that defined the request.
SSEQ# - Shows the the number of send request since last reset.
RSEQ# - Shows the number of reset request.
TGT-NETSPY - Shows the identifier of the target NetSpy or * if the request is not targetting any specific NetSpy.
System Action:
None.
User Action:
None.
Reason:
This message is the second heading of a SHOW NETSPY DEFS command. It contains the column headings for the NT5434 message, as follows:
COMMAND... - Shows the command represented by this request.
System Action:
None
User Action:
None
Reason:
This message is the first detail line of a SHOW NETSPY DEFS command. It contains details of a command definition. Refer to message NT5431 for column headings.
System Action:
None
User Action:
None
Reason:
This message is the second detail line of a SHOW NETSPY DEFS command. It contains the defined command text.
System Action:
None
User Action:
None
Reason:
This message indicates that an NSPCONN command was successfully processed. The command option is shown.
System Action:
None
User Action:
None
Reason:
An NSPCONN DEFINE command was not processed. The definition name for the NETSPY connection was already defined.
System Action:
The command is ignored.
User Action:
Choose a unique definition name and re-enter the command.
Reason:
An NSPCONN DEFINE command was not processed. The APPL name specified (or defaulted as the first 8 characters of the definition name) was already in use by another NETSPY connection definition.
System Action:
The command is ignored.
User Action:
Correct the application name and re-enter the command.
Reason:
An NSPCONN DEFINE command was not processed. The specified APPL name (or defaulted as the first eight characters of the definition name) was already used in this region (for example, a terminal name or another link application name).
System Action:
The command is ignored.
User Action:
Correct the application name, and reenter the command.
Reason:
An NSPCONN command was not processed. The option requested is shown. The targeted definition could not be altered, as its current state is not compatible with the request. For example, NSPCONN START for an already-running definition.
System Action:
The command is ignored.
User Action:
Check the state of the definition and correct and re-enter the command if necessary.
Reason:
An NSPCONN command was not processed. The option requested is shown. The targeted definition could not be found.
System Action:
The command is ignored.
User Action:
Check the name of the definition and correct and re-enter the command if necessary.
Reason:
This message is issued when an error occurs while receiving data on a NETSPY connection.
The name of the NETSPY connection is shown, as well as the VTAM application name.
The information in the message will be in one of two formats:
RC=xx,FBK2=xx,SENSE=xxxxxxxx
- which indicates a VTAM error occurred whilst receiving data. The VTAM return code, feedback code, and sense code are shown.
INVALID DATA RECEIVED, CODE: nn
- which indicates that invalid or incorrectly formatted data was received. The codes are:
04 - invalid length buffer received
System Action:
The VTAM session with NETSPY will be terminated
User Action:
Examine the reason for failure. Use the NSPCTL command to restart the connection.
If the error persists, contact your local support representative.
Reason:
A connection request was received from a CA NetSpy region. The sourcing application name is shown.
NetMaster does not accept inbound connection requests from CA NetSpy. To connect this region and CA NetSpy, this region must initiate the connection (using the NSPREQ command).
Note: This message is produced only if the CA NetSpy region making the request is Version 5.4 or later.
System Action:
The connection request is refused.
User Action:
Alter the CA NetSpy region to stop it from attempting to connect to NetMaster.
Reason:
Invalid or unrecognized user data was supplied on the BIND request from CA NetSpy, resulting in one of the following reason codes:
1 indicates that the user data does not start with NTNLOGON.
2 indicates that no information vectors were supplied. (This error can occur if an attempt is made to connect to a CA NetSpy region that is not at least Version 5.4.)
3 indicates that information vectors were incorrectly formatted.
1xx indicates that vector number xx was missing or formatted incorrectly.
The activity log contains further information, in the form of an NT6991 message and NT6992 messages containing a dump of the BIND user data.
System Action:
The BIND request is rejected.
User Action:
Check that the APPL name identifies a CA NetSpy region. If not, stop the software using that application name from attempting to connect to NetMaster.
If the application is CA NetSpy, ensure that it is at least Version 5.4.
Reason:
This message follows message NT6990. It indicates that a dump of the BIND user data follows.
System Action:
None
User Action:
See message NT6990.
Reason:
This message follows message NT6991. It displays a dump of the BIND user data.
System Action:
None
User Action:
See message NT6990.
Reason:
This message is issued if you attempt to perform some operations on an application name (APPLname) that is presently related to a NETSPY connection. The command name is shown in the message.
System Action:
THe command is ignored.
User Action:
Check that the correct application name was specified on the command.
Reason:
This message indicates that a connection to the indicated NETSPY has completed successfully.
System Action:
None
User Action:
None
Reason:
This message indicates that a connection to the indicated NETSPY has terminated.
System Action:
None
User Action:
If the termination was not as a result of an NSPCONN STOP command, check the log for messages relating to the connection.
Reason:
This message indicates that a connection to the indicated NETSPY is being terminated.
System Action:
None
User Action:
None
Reason:
This message indicates that a connection to the indicated NETSPY is being attempted.
System Action:
None
User Action:
None
Reason:
This message indicates that a connection to the indicated NETSPY was unsuccessful.
The connection failure reason is displayed. This will typically be a VTAM reason. The various return, reason, and sense codes can be looked up using the /CODES shortcut.
System Action:
None
User Action:
Check the log for error messages relating to the connection failure.
Reason:
This message indicates that a VTAM UNBIND or LOSTERM was received for the indicated NETSPY connection.
System Action:
The connection is terminated.
User Action:
Determine why NETSPY disconnected.
Reason:
This message indicates that a limit of start retries of the link to NETSPY was reached. P1 is the number of unsuccessful link starts limit reached. See preceeding message NT7080 for last start failure details.
System Action:
Link restarts will be discontinued. Link will enter FAILED state.
User Action:
Start/redefine the link after addressing the reasons for failure.
Reason:
This message indicates that a VTAM ENABLE-INPUT failed on the indicated NETSPY connection.
System Action:
The connection is terminated.
User Action:
None
Reason:
This message indicates that an invalid buffer was received from NETSPY.
System Action:
The buffer is ignored.
User Action:
Contact your support representative. The information in this and subsequent messages will aid problem determination.
Reason:
This message indicates that incoming data from NETSPY was unable to be matched with an outstanding request. The LUNAME is an internal name used to separate out individual requests.
System Action:
The data is ignored.
User Action:
Contact your support representative. The information in this and subsequent messages will aid problem determination.
Reason:
This message indicates that incoming data from NETSPY had an incorrect length.
System Action:
The data is ignored.
User Action:
Contact your support representative. The information in this and subsequent messages will aid problem determination.
Reason:
This message follows other NT738x messages and displays a hex and character dump of the invalid buffer.
System Action:
None
User Action:
See messages NT7380-NT7382.
Reason:
This message indicates that a VTAM SEND to the indicated NETSPY failed with the indicated error.
System Action:
The connection is terminated.
User Action:
Contact your support representative. The information in this and subsequent messages will aid problem determination.
Reason:
This message is returned from the NETSPY assembler API when a DEFINE request fails due to a storage shortage.
System Action:
The internal DEFINE request fails.
User Action:
Increase available storage.
Reason:
This message is returned from the NETSPY assembler API when a DEFINE request fails due to a syntax error in the TH=(...) operand of the NETSPY command.
There was a basic problem with this operand, such as:
- Unbalanced parenthesis.
- List too long.
- Null parameters.
System Action:
The internal DEFINE request fails.
User Action:
Correct the TH operand.
Reason:
This message is returned from the NETSPY assembler API when a DEFINE request fails due to a syntax error in the TH=(...) operand of the NETSPY command.
The list must have a multiple of 3 entries (3, 6, 9, ...).
System Action:
The internal DEFINE request fails.
User Action:
Correct the TH operand.
Reason:
This message is returned from the NETSPY assembler API when a DEFINE request fails due to a syntax error in the TH=(...) operand of the NETSPY command.
The indicated field name is invalid or null.
System Action:
The internal DEFINE request fails.
User Action:
Correct the TH operand.
Reason:
This message is returned from the NETSPY assembler API when a DEFINE request fails due to a syntax error in the TH=(...) operand of the NETSPY command.
The indicated field name is not known.
System Action:
The internal DEFINE request fails.
User Action:
Correct the TH operand.
Reason:
This message is returned from the NETSPY assembler API when a DEFINE request fails due to a syntax error in the TH=(...) operand of the NETSPY command.
The indicated relation operator value is invalid or omitted.
System Action:
The internal DEFINE request fails.
User Action:
Correct the TH operand.
Reason:
This message is returned from the NETSPY assembler API when a DEFINE request fails due to a syntax error in the TH=(...) operand of the NETSPY command.
The indicated relational operator value is not allowed for this field.
System Action:
The internal DEFINE request fails.
User Action:
Correct the TH operand.
Reason:
This message is returned from the NETSPY assembler API when a DEFINE request fails due to a syntax error in the TH=(...) operand of the NETSPY command.
The indicated value is not a valid number.
System Action:
The internal DEFINE request fails.
User Action:
Correct the TH operand.
Reason:
This message is returned from the NETSPY assembler API when a DEFINE request fails due to a syntax error in the TH=(...) operand of the NETSPY command.
The indicated field name and relational operator are duplicated.
System Action:
The internal DEFINE request fails.
User Action:
Correct the TH operand.
Reason:
This message is returned from the NETSPY assembler API when a DEFINE request fails due to a syntax error in the TH=(...) operand of the NETSPY command.
The list contains too many thresholds for the current NETSPY command.
System Action:
The internal DEFINE request fails.
User Action:
Correct the TH operand.
Reason:
This message is returned from the NETSPY assembler API when a DEFINE request fails for a command that must be specifically targeted to a single NETSPY.
The supplied NETSPY mask was not an exact name.
System Action:
The internal DEFINE request fails.
User Action:
Correct the supplied NETSPY name mask to be an exact name. Note that even if the mask would only match one NETSPY, this is not acceptable. A non-wildcard value must be supplied.
Reason:
This message is returned from the CA NetSpy assembler API when a DEFINE request fails for a MONITOR command because the assigned MONITOR name is not globally unique in this region.
System Action:
The internal DEFINE request fails.
User Action:
Correct the MONITOR name. It must be unique in this region.
Reason:
This message is returned from an NSPREQ OML verb that detects a duplicate path name definition.
System Action:
The NSPREQ Define fails with return code 8, feedback code 81. &SYSMSG is set to this message.
User Action:
Correct the procedure.
Reason:
This message is returned from an NSPREQ OML verb that detects an unknown path name.
System Action:
The NSPREQ request fails with return code 8, feedback code 83. &SYSMSG is set to this message.
User Action:
Correct the procedure.
Reason:
This message is returned from an NSPREQ SEND OML verb when the path that the send was requested on has an outstanding asynchronous request.
System Action:
The NSPREQ SEND fails with return code 8, feedback code 84. &SYSMSG is set to this message.
User Action:
Correct the procedure.
Reason:
This message is returned from an NSPREQ SEND OML verb when the send fails. The return code from the inner API is shown.
Possible return code values are:
04 - Unknown RCORR value (should not happen with OML)
08 - Previous send not completed (Should not happen with OML)
12 - No suitable target NETSPYs. (should not happen with OML)
System Action:
The NSPREQ SEND fails with return code 8, feedback code 87. &SYSMSG is set to this message.
User Action:
Correct the procedure.
Reason:
This message is issued if the SYSPLEX feature is licenced in a SOLVE system that is executed on an operating system that is not at least MVS/ESA 5.1. It indicates that the SYSPLEX feature is not useable in this environment
System Action:
SOLVE processing continues, however the SYSPLEX feature is not activated.
User Action:
Use the EXC JCL parameter to omit the SYSPLEX feature.
Reason:
This message is issued during SOLVE initialization if the ARM facility is activated and the SOLVE region is not APF-authorized. (ARM is the Automatic Restart Manager).
System Action:
Processing continues; however, the ARM facility is not available.
User Action:
Ensure that the region is set up to run APF-authorized.
Reason:
This message is issued during SOLVE initialization if the ARM facility is activated and the MVS/ESA level is not at least 5.2. This is because the ARM (Automatic Restart Manager) component of MVS/ESA first appeared in MVS/ESA 5.2.
System Action:
Processing continues, however, the ARM facility is not available.
User Action:
Upgrade MVS/ESA to at least version 5.2.
Reason:
This message is issued during SOLVE initialization if the ARM facility is activated. It indicates that a successful registration with ARM (Automatic Restart Manager) has occurred. The ARM element name is also displayed. The default name is SVM_acbname unless changed using JCL initialization parameters.
System Action:
Processing continues, with possible restarts under ARM control.
User Action:
None.
Reason:
This message is issued during SOLVE initialization if the ARM facility is activated. It indicates that a successful WAITPRED request to ARM (Automatic Restart Manager) occurred.
System Action:
Processing continues, with possible restarts under ARM control.
User Action:
None.
Reason:
This message is issued during SOLVE initialization if the ARM facility is activated. It indicates that a successful READY request to ARM (Automatic Restart Manager) occurred.
System Action:
Processing continues, with possible restarts under ARM control.
User Action:
None.
Reason:
This message is issued during SOLVE termination if the ARM facility is activated. It indicates that a SOLVE has deregistered from ARM (Automatic Restart Manager).
System Action:
SOLVE continues termination. ARM will not restart SOLVE.
User Action:
None.
Reason:
This message is issued during SOLVE processing if the ARM facility is requested. It indicates that an error occurred during processing of an ARM (Automatic Restart Manager) request. The return code and reason code (R0) are displayed.
System Action:
Processing continues. However, ARM services will not be used.
User Action:
Examine the return and reason codes and determine the appropriate action. Explanations for the return and reason codes are in the MVS/ESA Version 5 Sysplex Services References manual, in the section on the IXCARM macro.
Reason:
This message is issued by the STATUS command if the ARM facility was requested in the SOLVE JCL parameters. It indicates the current status of the ARM connection and shows the element name and element type that SOLVE is known to ARM by.
System Action:
None.
User Action:
None.
Reason:
This message is issued by the STATUS command if the ARM facility is requested. It indicates that an error occurred during processing of an ARM (Automatic Restart Manager) request. The request in error and the return code and reason code (R0) are displayed, as well as the element name that was used.
System Action:
None.
User Action:
Examine the return and reason codes and determine the appropriate action. Explanations for the return and reason codes are in the MVS/ESA Version 5 Sysplex Services References manual, in the section on the IXCARM macro.
Reason:
This message is issued if the SYSPLEX feature is licenced in an NMSSI region that is executed on an operating system that is not at least MVS/ESA 5.1. It indicates that the SYSPLEX feature cannot be used in this environment.
System Action:
NMSSI processing continues; however, the SYSPLEX feature is not activated.
User Action:
Use the EXC initialization parameter to omit the SYSPLEX feature.
Reason:
This message is issued during NMSSI initialization if the XCF facility is activated and the MVS/ESA level is not at least 5.1. The XCF facility requires at least MVS/ESA 5.1
System Action:
NMSSI processing continues; however, the XCF facility is not available.
User Action:
Upgrade MVS/ESA to at least version 5.1.
Reason:
This message is issued by the SSI STATUS command if the XCF facility was requested in the NMSSI JCL parameters. It indicates that the XCF facility is active, and provides the XCF member name, group name, and XCF token
System Action:
None.
User Action:
None.
Reason:
This message is issued during NMSSI initialization if an error occurs while initializing the XCF interface. NMSSI was unable to obtain storage needed to initialize the XCF interface.
System Action:
NMSSI terminates.
User Action:
Check the amount of storage available to the NMSSI region and increase it if possible.
Reason:
This message is issued during NMSSI initialization if an error occurs while attempting to connect to XCF (using the IXCJOIN macro). The return code and reason code (R0) are displayed.
System Action:
NMSSI terminates.
User Action:
Check the return and reason codes in the MVS/ESA Sysplex Services Reference guide (the IXCJOIN macro) and correct the problem if possible. If not, contact Technical Support.
Reason:
This message is issued by the SHOW SSISTATS command if the XCF facility was requested in the NMSSI JCL parameters. It indicates that XCF statistical information follows.
System Action:
None.
User Action:
None.
Reason:
This message is issued by the SHOW SSISTATS command if the XCF facility was requested in the NMSSI JCL parameters. It provides column headings for the following NXSB22 messages.
Columns are:
MEMBER NAME The XCF member name of a member in the group
BUF-SENT The number of data buffers sent to the member
BYT-SENT The total number of bytes sent to the member
BUF-RCVD The number of data buffers received from the member
BYT- RCVD the total number of bytes received from the member
System Action:
None.
User Action:
None.
Reason:
This message is issued by the SHOW SSISTATS command if the XCF facility was requested in the NMSSI JCL parameters. It provides information about an XCF member in the same group as this NMSSI region.
Refer to message NXSB21 for column meanings.
System Action:
None.
User Action:
None.
Reason:
This message is issued by the SHOW SSISTATS command if the XCF facility was requested in the NMSSI JCL parameters. It provides column headings for the following NXSB23 messages.
Columns are:
POOLTYPE The type of storage pool being described
ELT-SIZE The size of elements in the pool
FRM-POOL The number of satisfied requests for elements from the pool GETMAIN The number of requests for elements that had to be getmained as the pool was empty
System Action:
None.
User Action:
None.
Reason:
This message is issued by the SHOW SSISTATS command if the XCF facility was requested in the NMSSI JCL parameters. It provides information about XCF-related storage pools.
Refer to message NXSB23 for column headings.
System Action:
None.
User Action:
None.
Reason:
This message is issued by the SHOW SSISTATS command if the XCF facility was requested in the NMSSI JCL parameters. It provides column headings for the following NXSB26 message.
Columns are:
#-EVENTS The number of XCF events that were seen
#-EV-LST The number of XCF events lost due to storage shortages
#-MS-RCV The number of incoming messages that were seen
#-MS-LST The number of messages lost due to storage shortages
#-MS-SNT The number of outgoing messages sent
System Action:
None.
User Action:
None.
Reason:
This message is issued by the SHOW SSISTATS command if the XCF facility was requested in the NMSSI JCL parameters. It provides statistics about various XCF events and messages.
Refer to message NXSB25 for column meanings.
System Action:
None.
User Action:
None.
Reason:
This message is issued by the SHOW SSIEPS command if the XCF facility was requested in the NMSSI JCL parameters. It indicates that the XCF facility is active, and provides the XCF member name, group name, and token.
System Action:
None.
User Action:
None.
Reason:
This message is issued by the SHOW SSIEPS command if the XCF facility was requested in the NMSSI JCL parameters. It provides column headings for the following NXSD11 message(s).
The headings are:
MEMBER-NAME The XCF member name of a member of the same XCF group as this NMSSI region. (Normally the XCF member name is <sysname||ssid>.)
MEMBER-TOKEN The XCF member token of the member
ID The NMSSI-assigned internal id of this member
SYSNAME The system name this member is on
F1 Flags: 80 - if on, this is 'this' XCF member (ie us)
02 - if on, this member is 'dead'
01 - if on, this member has a different version of the NMSSI XCF code, and is not supported.
F2 Flags: 08 - if on, this member is of indeterminate status
System Action:
None.
User Action:
None.
Reason:
This message is issued by the SHOW SSIEPS command if the XCF facility was requested in the NMSSI JCL parameters. It provides details about each XCF member in the same XCF group.
Refer to message NXSD10 for column headings and descriptions.
System Action:
None.
User Action:
None.
Reason:
This message is issued during NMSSI initialization if the ARM facility is activated and the MVS/ESA level is not at least 5.2. This is because the ARM (Automatic Restart Manager) component of MVS/ESA first appeared in MVS/ESA 5.2.
System Action:
NMSSI processing continues; however, the ARM facility is not available.
User Action:
Upgrade MVS/ESA to at least version 5.2.
Reason:
This message is issued during NMSSI initialization if the ARM facility is activated. It indicates that a successful registration with ARM (Automatic Restart Manager) has occurred. The ARM element name is also displayed. (The default name if not changed in the JCL parms is SVS_sysnamessid.)
System Action:
NMSSI processing continues, with possible restarts under ARM control.
User Action:
None.
Reason:
This message is issued during NMSSI initialization if the ARM facility is activated. It indicates that a successful WAITPRED request to ARM (Automatic Restart Manager) occurred.
System Action:
NMSSI processing continues, with possible restarts under ARM control.
User Action:
None.
Reason:
This message is issued during NMSSI initialization if the ARM facility is activated. It indicates that a successful READY request to ARM (Automatic Restart Manager) occurred.
System Action:
NMSSI processing continues, with possible restarts under ARM control.
User Action:
None.
Reason:
This message is issued during NMSSI termination if the ARM facility is activated. It indicates that a NMSSI has deregistered from ARM (Automatic Restart Manager).
System Action:
NMSSI continues termination. ARM will not restart NMSSI.
User Action:
None.
Reason:
This message is issued during NMSSI processing if the ARM facility is requested. It indicates that an error occurred during processing of an ARM (Automatic Restart Manager) request. The return code and reason code (R0) are displayed.
System Action:
Processing continues. However, ARM services will not be used.
User Action:
Examine the return and reason codes and determine the appropriate action. Explanations for the return and reason codes are in the MVS/ESA Version 5 Sysplex Services References manual in the section on the IXCARM macro.
Reason:
This message is issued by the SSI STATUS command if the ARM facility was requested in the NMSSI JCL parameters. It indicates the current status of the ARM connection and shows the element name and element type that NMSSI is known to ARM by.
System Action:
None.
User Action:
None.
Reason:
This message is issued by the SSI STATUS command if the ARM facility is requested. It indicates that an error occurred during processing of an ARM (Automatic Restart Manager) request. The request in error, the return code, and reason code (R0) are displayed, as well as the element name that was used.
System Action:
None.
User Action:
Examine the return and reason codes and determine the appropriate action. Explanations for the return and reason codes are in the MVS/ESA Version 5 Sysplex Services References manual in the section on the IXCARM macro.
Reason:
An attempt to connect to the local router was refused.
System Action:
The XAPI one-shot backend exit terminates, since this is a system error.
User Action:
Investigate any previous messages from the local router.
Reason:
An attempt to acquire storage by the one-shot XAPI backend exit failed.
System Action:
The XAPI one-shot backend exit terminates, since this is a system error.
User Action:
Increase the size of the region running SSI.
Reason:
An attempt to connect to the local router failed.
System Action:
The XAPI one-shot backend exit terminates, since this is a system error.
User Action:
Investigate the return code in the message.
Reason:
An attempt to send data to the local router failed.
System Action:
The XAPI one-shot backend exit terminates, since this is a system error.
User Action:
Investigate the return code in the message.
Reason:
The structure of the MDO supplied to the XAPI one-shot interface is invalid.
System Action:
The message is ignored.
User Action:
This is an error in the user exit issuing the XAPI call. Verify the MDO structure being sent.
Reason:
SOLVESSI SMF Exit registration was successful.
System Action:
SOLVESSI initialization continues.
User Action:
None.
Reason:
The current execution of SOLVESSI SMF Exit registration detected that SMF Exits are already registered. A previous run of SOLVESSI registered the exits.
System Action:
SOLVESSI initialization continues.
User Action:
None.
Reason:
The expected System Anchor Block was not found. This should not happen, because the SAB should have been created in an earlier stages of the SOLVESSI processing.
System Action:
SOLVESSI initialization terminates.
User Action:
Check whether the SOLVESSI log contains any previous messages related to SAB creation or any other abnormal situations. If the problem persists, contact Technical Support.
Reason:
Obtaining storage for SMF control block P1 failed. Normally, this should not happen unless the system has a serious storage constrain.
P1 describes the control block for which GETMAIN failed:
SMFQ - Reply area for CAISMFQ function.
SMCT - SMF Master Control Table.
SMCU - 512 bytes for the SMCT migration.
System Action:
SOLVESSI initialization continues and depending on P1 , the following occurs: SMFQ (SP0) - SMF registration terminates. SMCT (CSA) - SMF registration terminates. SMCU (CSA) - SMCT upgrade terminates; SMF registration continues.
User Action:
Ensure there is a memory shortage. If so, resolve the shortage and restart SOLVESSI. CSA storage shortage is normally accompanied by relevant messages issued to the system console. If the problem persists, contact Technical Support.
Reason:
At least one of the NetMaster modules corresponding to SMF IEF83, IEF84, IEF85, or common code was not found in the searched link libraries. This may indicate incomplete installation and/or customization of NetMaster SMF support.
System Action:
SOLVESSI initialization continues.
User Action:
Check whether the library containing Y7FU83, Y7FU84, Y7FU85, and SOLVESSI SMF modules is available for the SOLVESSI task. If it is not available, correct the situation.
Reason:
An attempt to register SMF exit P2 failed with return code P1 . This situation may indicate that exits are already registered and enabled (RC=4), or there is a more serious reason, for example, CSA shortage, load errors, or incomplete installation of CA Common Services.
RC=4 can be considered normal, although it may indicate incomplete SMF control block creation. It may happen during consecutive SOLVE SSI starts after a system IPL.
System Action:
SOLVESSI initialization continues.
User Action:
If P1 is higher than 4, ensure CA Commmon Services is installed and active, using the following return codes as guidelines:
08 - Unable to load requested module, product not installed: Check if CA Common Services is installed correctly and it is the required level, minimum 0300. Check for other CA Common Services related messages in the SSI or system log. Contact your System Programmer for assistance.
12 - Environmental error (no CSA, LOAD error, and so on): Check for the case of the system resources shortage, load library errors. This situation may be accompanied by CA Common Services induced messages and dumps. Check system log. Contact your System Programmer for assistance.
16 - Invalid parameter list: Internal coding error, contact Technical Support.
If the problem persists, contact Technical Support.
Reason:
One or more SMF exit registrations failed.
System Action:
SOLVESSI initialization continues.
User Action:
Check for the occurrence of NY3006 for more details.
Reason:
The required CA Common Services environment (CAS9) was not established. This indicates either that TNGFW was not properly installed/customized and/or that CAS9 was not started.
System Action:
SOLVESSI initialization continues.
User Action:
Check for the reasons why CA Common Services was not started, fix the problem, and restart SOLVESSI.
Reason:
An attempt to use one of dynamic CA Common Services SMF functions failed due to one or more load modules missing. This normally indicates problems with accessing the CA Common Services library.
System Action:
SOLVESSI initialization continues.
User Action:
Check the availability to SOLVESSI (link list/STEPLIB) of the library containing TNG Framework SMF functions. Fix the problem and restart SOLVESSI.
Reason:
SOLVESSI SMF exit registration function detected that SMF processing was disabled.
System Action:
SOLVESSI initialization continues.
User Action:
Check the reasons for SMF processing disablement. Enable and restart SMF processing, if necessary.
Reason:
The TNG Framework #SMFQ function returned unexpected results. This may indicate incomplete installation of TNG Framework.
System Action:
SOLVESSI initialization continues.
User Action:
Check for previous problems with TNG Framework. Fix them and then restart SOLVESSI. If the problem persists, contact Technical Support.
Reason:
An attempt was made to activate CA Common Services for dynamic SMF Exit code registration, but the operating system is not IBM OS/390 V2R5 or above.
System Action:
SOLVESSI initialization continues; SMF exit registration is terminated.
User Action:
Make sure to run dynamic SMF registration on IBM OS/390 V2R5 or above.
Reason:
An attempt was made to activate NetMaster collection of IBM TCP/IP SMF record 119 (x'77), but the operating system is not IBM z/OS V1R2 or above.
System Action:
SOLVESSI initialization continues, but no SMF records will be collected.
User Action:
Change to collecting SMF record 118 (x'76') or upgrade to z/OS V1R2 or above.
Reason:
SSI reload of SMF exits common code detected that it was not able to remove a previous copy of the code from memory. This indicates that common code is still in use by another exit code. Common code storage release will be attempted on the return from the last active copy of this code.
System Action:
SOLVESSI initialization continues, and the next copy of the common code is loaded into memory.
User Action:
None.
Reason:
SSI SMF exits registration failed.
System Action:
SOLVESSI initialization continues.
User Action:
Check the SSI log for a more detailed explanation and proceed according to the messages logged there.
Reason:
The SSI detected that the level of CA Common Services P1 is lower than required to ensure the correct registration of SMF exits. It may indicate that some exits, typically Y7FU85, may not function correctly. If P1 is 000000, it indicates that the CAS9GLVL module holding the release information does not conform to the expected format. It may indicate that the CA Common Services used is not current. It may indicate that an old version of the CA Common Services library is specified in LNKLST or JOBLIB, or STEPLIB before the most current version.
System Action:
SOLVESSI initialization continues.
User Action:
Use the command SSI STATUS to see the CA Common Services level (look for message NY3116 CA COMMON SERVICES LEVEL DETECTED=nnnnnn).
Install the latest service pack of CA Common Services for z/OS.
Ask your systems programmer to verify LNKLST specifications.
Review the SSI JCL to check for JOBLIB/STEPLIB-specified CA Common Services library.
Reason:
This is the continuation of message NY3016, see its explanation for more details.
System Action:
SOLVESSI initialization continues.
User Action:
See message NY3016.
Reason:
SSI start detected that the CA Common Services CAISMFQ function was not available.
System Action:
SOLVESSI initialization continues.
User Action:
See message NY3016.
Reason:
The SSI detected that the SMF exit code cannot proceed with SMF data processing because it has detected an incomplete control block environment. P1 is the name of the exit that detected the error.
System Action:
SOLVESSI initialization continues.
No SMF data is processed by SMF exits until the situation is rectified.
User Action:
Check the SSI log for error messages. Generally, it indicates that the SMF exit code was started before the environment was created by the SSI. The actual starting of the SSI may have rectified the situation.
For information about how to get diagnostics on SMF exit configuration, contact Technical Support.
Reason:
The SSI detected that SMF exit code cannot proceed with SMF data processing as a result of detecting an incomplete control block environment. P1 is the name of the exit that detected the error.
System Action:
SOLVESSI initialization continues.
No SMF data is processed by SMF exits until the situation is rectified.
User Action:
Check the SSI log for error messages. Generally, it indicates that the SMF exits code was started before the environment was created by the SSI. It may also indicate that SSI detected an incomplete version (lack of CAISMFQ) of CA Common Services. The actual starting of the SSI may have rectified the situation.
For information about how to get diagnostics on SMF exit configuration, contact Technical Support.
Reason:
The SSI detected that SMF exit code cannot proceed with SMF data processing because it has detected an incomplete environment. P1 is the name of the exit that detected the error.
System Action:
SOLVESSI initialization continues.
No SMF data is processed by SMF exits until the situation is rectified.
User Action:
Check the SSI log for error messages. Generally, it indicates that the SMF exit code was started before the environment was created by the SSI. It indicates that the SMF exits common code module (SOLVESSISMF) was not loaded. The actual starting of the SSI may rectify the situation.
For information about how to get diagnostics on SMF exit configuration, contact Technical Support.
Reason:
The P1 exit cannot obtain dynamic storage for the save area. The message reports incidents that happened before the SSI was started. They may still be happening. The private storage shortage in the SMF exit caller (IBM stack normally) may prevent SMF record processing.
System Action:
None.
User Action:
Investigate, and correct possible private storage shortage in the running IBM stacks.
Reason:
The SSI SMF Management detected that the SMF Exits Common Code version is too low for this version of SSI.
System Action:
SOLVESSI initialization terminates. No SMF-related function, including SMF support of SSI commands, will be performed by this instance of the SSI.
User Action:
Review the contents of the SSI load library.
Reason:
Obtaining storage for SMF control blocks failed with reason code P1 . This should not normally happen unless the system has a serious memory shortage.
System Action:
SOLVESSI initialization continues.
User Action:
Check whether there is a memory shortage. If so, resolve the shortage and restart SOLVESSI. If the problem persists, contact Technical Support.
Reason:
An attempt to use one of dynamic CA Common Services functions failed due to one or more missing load modules. This normally indicates problems with accessing the CA Common Services library.
System Action:
SOLVESSI initialization continues.
User Action:
Check the availability to SOLVESSI (link list/STEPLIB) of the library containing CA Common Services SMF functions. Fix the problem and restart SOLVESSI.
Reason:
SSI reports the level of CA Common Services used as P1 .
System Action:
None.
User Action:
None.
Reason:
This is the continuation of message NY3016, see its explanation for details.
System Action:
SOLVESSI initialization continues.
User Action:
See message NY3016.
Reason:
This is the first message issued as a reply to the SSI STATUS command.
System Action:
None.
User Action:
None.
Reason:
This message indicates the current status of SMF processing. P1 can be ENABLED or DISABLED .
System Action:
None.
User Action:
None.
Reason:
This message indicates that SMF exit information follows. P1 is the number of entries received. P2 is the number of entries requested.
System Action:
None.
User Action:
None.
Reason:
This message, repeated for each NetMaster SMF exit found, provides the following information:
P1 is the Load Module Name.
P2 is the name of the Job/Started Task which registered the Exit.
P3 is the date of the registration in yyyymmdd format.
P4 is the time of the registration in hhmmsshh format.
P5 is the Attributes1 byte: 1... .... This entry is enabled. .1.. .... This entry has abended. ..1. .... Call test program on first call. ...1 .... Disable entry on abend. .... 1... Take SVC dump on abend. .... .1.. (unused) .... ..1. (unused) .... ...1 (unused) Note: A normal situation is indicated by: 98 - for SMF processing enabled 18 - for SMF processing disabled
P6 is the entry point address of the Exit code stub.
P7 is the number of processed SMF records received by the Exit.
P8 is the number of processed SMF records for which the Exit sent the write request to SMF. Note: These are indicative fields only, in hexadecimal format for brevity. They help in verifying if any SMF records are actually flowing through the interface.
System Action:
None.
User Action:
None.
Reason:
This message, repeated for each NetMaster SMF Exit found, and issued when #SMFQ failed, provides the following information:
P1 is the Load Module Name.
P2 is the name of the Job/Started Task which registered the Exit.
P3 is the date of the registration in yyyymmdd format.
P4 is the time of the registration in hhmmsshh format.
P5 is the number of processed SMF records received by the Exit.
P6 is the number of processed SMF records for which the Exit sent the write request to SMF. Note: These are indicative fields only, in hexadecimal format for brevity. They help in verifying if any SMF records are actually flowing through the interface.
System Action:
None.
User Action:
None.
Reason:
This message, repeated for each NetMaster SMF Exit found, and issued when the SAB chain walk fails, provides the following information:
P1 is the Load Module Name.
P2 is the product version number.
P3 is the Attributes1 byte (see message NY3124 for details).
P4 is the entry point address of the Exit code stub.
System Action:
None.
User Action:
None.
Reason:
This is a header message, followed by either NY3124 or NY3125, which provides information about the following messages (in tabulated form):
EXIT_NME - Load module name of the SMF exit
REG_JOB - Name of the Job/STC that registered the exit last
REG_DATE - Registration date in the format : YYYYMMDD
REG_TIME - Registration time in the format : HHMM
AT - CA Common Services attributes in hexadecimal
EP - SMF Exit entry point address in hexadecimal
RECV-REC - Number of received SMF records in hexadecimal
WRTN-REC - Number of SMF records returned to SMF (in hexadecimal) with write request
System Action:
None.
User Action:
None.
Reason:
This second header message provides information about consecutive NY3137 messages in the tabulated form of the SMF Exit modules information.
CSVER - CA Common Services Exit version in the format :
PPVV VERSION - Delivery level in the format : VVRR
PTF_LVL - PTF level of the module in the format : Z99999
CMP_DATE - Compilation time date in the format : YYYYMMDD
CMP_TIME - Compilation time in the format : HHMM
REJT_REC - Number of SMF records rejected (failed validity check) by the SMF exit
System Action:
None.
User Action:
None.
Reason:
This is the last message issued as a reply to the SSI STATUS command. It summarizes the query results, providing the number of entries returned by query (P1) and the number of required entries (P2).
A discrepancy between P1 and P2 indicates that there may be older versions of SMF exits registered or remaining in the exit lists. It is normal when migration from older versions is performed without an IPL of the operating system. All old and new SMF exits registered and deregistered are listed in this situation.
System Action:
None.
User Action:
No action is required unless P1 and P2 provide different values.
List this region's configuration details (/IPTEST), and investigate any errors.
For information about how to get diagnostics on SMF exit configuration, contact Technical Support.
Reason:
This message indicates that the System Anchor Block has not been found.
System Action:
None.
User Action:
None.
Reason:
This message indicates that the SMF Slot (Slot 2 in SAB) has not been found or that its formatting has not been finished.
System Action:
None.
User Action:
None.
Reason:
This message indicates that the SMF Control Table has not been found.
System Action:
None.
User Action:
None.
Reason:
This message indicates that the SMF Control Table formatting has not been finished.
System Action:
None.
User Action:
None.
Reason:
This message indicates that TNG FrameWork (CAS9) has not been run.
System Action:
None.
User Action:
None.
Reason:
This message indicates that the TNGFW SMF Query function returned an error. P1 is the error code.
System Action:
None.
User Action:
None.
Reason:
This message indicates that the CA Common Services (TNGFW) SMF Query Query function (CAISMFQ) is not available to SSI. Generally, it indicates that the installed version of CA Common Services is not at the minimum required level of SP3.
System Action:
None.
User Action:
Contact your system programmer to check the installation of the CA Common Services software.
Use the command SSI STATUS to determine the CA Common Services level (look for message NY3116 CA COMMON SERVICES LEVEL DETECTED=nnnnnn).
Install the latest service pack of CA Common Services for z/OS.
Ask your systems programmer to verify LNKLST specifications.
Review the SSI JCL to check for JOBLIB/STEPLIB-specified CA Common Services library.
Reason:
This message, repeated for each SMF exit found, provides the following information:
P1 is the CA Common Services registered SMF exit version string.
P2 is the delivery level.
P3 is the PTF level.
P4 is the compilation date.
P5 is the compilation time.
P6 is the rejected record count.
System Action:
None.
User Action:
None.
Reason:
This message, issued for the SMF exits common code, provides the location and currency of the load module:
P1 is the load module entry point.
P2 is the delivery level in the format of : VVRR
P3 is the PTF level of the module in the format of : Z99999
P4 is the compilation time date in the format of : YYYYMMDD
P5 is the compilation time in the format of : HHMM
System Action:
None.
User Action:
None.
Reason:
In response to the ssi status command, this message indicates that the CA Common Services Query service EPS receiver is active. P1 is the receiver name.
System Action:
None.
User Action:
None.
Reason:
Registration of the CA Common Services query service EPS receiver failed with return code P1 .
System Action:
SOLVESSI initialization continues.
User Action:
Restart SOLVESSI. If the problem persists, contact Technical Support.
Reason:
The SOLVESSI SMF command processor detected that the mandatory function code describing the function to perform is missing.
System Action:
SOLVESSI SMF command processing terminates.
User Action:
Check valid SOLVESSI SMF function codes and re-enter the command.
Reason:
The SOLVESSI SMF command processor detected that the function code describing the function to perform is invalid.
System Action:
SOLVESSI SMF command processing terminates.
User Action:
Check valid SOLVESSI SMF function codes and re-enter the command.
Reason:
SOLVESSI SMF command processor detected that the function code argument
P1 for the function to perform is invalid. This may indicate that the argument type is not compatible with the function (not a valid hexadecimal number) or that it is of the wrong length.
System Action:
SOLVESSI SMF command processing terminates.
User Action:
Check valid arguments for the function of the SOLVESSI SMF command and re-enter correct command.
Reason:
The expected System Anchor Block cannot be found. This should not happen because the SAB should be created in earlier stages of SOLVESSI processing.
System Action:
SOLVESSI processing continues.
User Action:
Check if the SOLVESSI log contains any previous messages related to SAB creation or any other abnormal situations. If you are unable to resolve the problem, contact Technical Support.
Reason:
The expected SMF Control Table cannot be found. This should not happen because the SMCT should be created in earlier stages of SOLVESSI processing.
System Action:
SOLVESSI processing continues.
User Action:
Check if the SOLVESSI log contains any previous messages related to SMCT creation or any other abnormal situations. If you are unable to resolve the problem, contact Technical Support.
Reason:
The SOLVESSI SMF DEREGISTER command completed without errors. All previously registered SMF exits were deregistered.
System Action:
None.
User Action:
None.
Reason:
An attempt to deregister SMF exit P2 failed with return code P1. This may indicate an internal CA NetMaster or CA Common Services error.
System Action:
SOLVESSI processing continues.
User Action:
If P1 is higher than 4, ensure CA Common Services is installed and active, and then check for such things as a shortage of system resources. If the problem persists, contact Technical Support.
Reason:
The current execution of SOLVESSI SMF exit deregistration detected that SMF exits are already deregistered.
System Action:
None.
User Action:
None.
Reason:
The SOLVESSI SMF DEBUG command has completed setting debug flags.
System Action:
None.
User Action:
None.
Reason:
At least one of the modules corresponding to SMF IEF83, IEF84, IEF85, or common code cannot be found in the searched link libraries. This may indicate in complete installation and customization of SMF support.
System Action:
SOLVESSI initialization continues.
User Action:
Check whether the library containing Y7FU83, Y7FU84, Y7FU85, and SOLVESSI SMF modules is available for the SOLVESSI task. If it is not available, correct the situation.
Reason:
The expected System Anchor Block cannot be found. This should not happen because the SAB should be created in earlier stages of SOLVESSI processing.
System Action:
SOLVESSI processing continues.
User Action:
Check if the SOLVESSI log contains any previous messages related to SAB creation or any other abnormal situations. If you are unable to resolve the problem, contact Technical Support.
Reason:
The expected SMF Control Table cannot be found. This should not happen because the SMCT should be created in earlier stages of SOLVESSI processing.
System Action:
SOLVESSI processing continues.
User Action:
Check if the SOLVESSI log contains any previous messages related to SMCT creation or any other abnormal situations. If you are unable to resolve the problem, contact Technical Support.
Reason:
Obtaining storage for SMF control block P1 failed. Normally, this should not happen unless the system has a serious storage constrain.
P1 describes the control block for which GETMAIN failed: SMFQ - Reply area for CAISMFQ function. SMCT - SMF Master Control Table. SMCU - 512 bytes for the SMCT migration.
System Action:
SOLVESSI initialization continues; depending on P1 , the following occurs: SMFQ (SP0) - SMF registration terminates. SMCT (CSA) - SMF registration terminates. SMCU (CSA) - SMCT upgrade terminate; SMF registration continues.
User Action:
Check whether there is a memory shortage. If so, resolve the shortage and restart SOLVESSI. CSA storage shortage is normally accompanied by relevant messages issued to the system console. If the problem persists, contact Technical Support.
Reason:
An attempt to register SMF exit P2 failed with return code P1. This may indicate that exits are already registered and enabled (RC=4), or there may be more serious reasons, such as CSA shortage, load errors, or incomplete installation of CA Common Services.
RC=4 can be considered normal, although it may indicate incomplete SMF control block creation. It may happen during consecutive SOLVESSI starts after a system IPL.
System Action:
SOLVESSI initialization continues.
User Action:
If P1 is higher than 4, ensure CA Commmon Services is installed and active, using the following return codes as the guidelines:
08 - Unable to load requested module, product not installed:
12 - Environmental error (no CSA, LOAD error, and so on):
16 - Invalid parameter list:
Internal coding error, contact Technical Support.
If the problem persists, contact Technical Support.
Reason:
This message indicates that the CA Common Services SMF query function returned an arror. P1 is the error code.
System Action:
None.
User Action:
None.
Reason:
An attempt to use one of dynamic CA Common Services SMF functions failed due to one or more load modules missing. This normally indicates problems with accessing the CA Common Services library.
System Action:
SOLVESSI initialization continues.
User Action:
Check the availability to SOLVESSI (link list/STEPLIB) of the library containing CA Common Services SMF functions. Fix the problem and restart the SOLVESSI.
Reason:
SSI reload of SMF exits common code detected that it was not able to remove a previous copy of the code from memory. This indicates that common code is in use by another exit code. Common code storage release is attempted on the return from the last active copy of this code.
System Action:
SOLVESSI initialization continues and the next copy of the common code is loaded into memory.
User Action:
None.
Reason:
One or more SMF exit registrations failed.
System Action:
SOLVESSI initialization continues.
User Action:
Check for the occurrence of NY3006 for more details.
Reason:
This is the continuation of message NY3016; see its explanation for more information.
System Action:
SOLVESSI initialization continues.
User Action:
See message NY3016.
Reason:
SOLVESSI SMF exit registration was successful.
System Action:
SOLVESSI initialization continues.
User Action:
None.
Reason:
The SOLVESSI SMF DEREGISTER command completed without errors. All previously registered SMF exits were deregistered.
System Action:
None.
User Action:
None.
Reason:
An attempt to deregister SMF exit P2 failed with return code P1. This may indicate an internal CA NetMaster or CA Common Services error.
System Action:
SOLVESSI processing continues.
User Action:
If P1 is higher than 4, ensure CA Common Services is installed and active, and then check for such things as a shortage of system resources. If the problem persists, contact Technical Support.
Reason:
The current execution of SOLVESSI SMF exit deregistration detected that SMF exits are already deregistered.
System Action:
None.
User Action:
None.
Reason:
The SMF facility front runner module terminated the SSI initialization due to the lack of one of the following prerequisistes described by P1:
NOT SUPPORTED ON THIS OPERATING SYSTEM The operating system level detected is lower than the minimum required, which is OS/390 2.10.
SMF RECORD=119 REQUIRES ZOS ABOVE 1.2 Processing of SMF record number 119 is supported on z/OSlevel 1.2 and above only.
CA COMMON SERVICES NOT ACTIVE SSI detected that the Common Services code is not started.
This normally indicates problems with accessing the latest level of the CA Common Services library.
CA COMMON SERVICES INCOMPLETE OR REL LOW SSI detected that the CA Common Services library is incomplete or at a release lower than required.
REQUIRED SMF MODULES NOT FOUND SSI detected that required SMF support modules are not available. All of the following modules are required:
NMSSISMF - SMF Common Code Y7FU83 - SMF IEFU83 Exit Y7FU84 - SMF IEFU84 Exit Y7FU85 - SMF IEFU85 Exit
SMF MANAGEMENT ALREADY ACTIVE SSI SMF Management detected that another copy is already active. Only one copy is allowed to run at the same time.
System Action:
SOLVESSI initialization terminates.
User Action:
NOT SUPPORTED ON THIS OPERATING SYSTEM: Ensure that the operating system used is at a minimum level of S/390 V2R10.
SMF RECORD=119 REQUIRES ZOS ABOVE 1.2: Ensure that the operating system used is at a minimum level of z/OS v1 rel 2. SMF record 119 does not exist below this level. Change IPSMF specification to 118 or move to the required minimum level of the operating system.
CA COMMON SERVICES NOT ACTIVE: Check that the CAS9 job executed prior to SSI start.
CA COMMON SERVICES INCOMPLETE OR REL LOW Ensure that the CA Common Services library available to NMSSI using link list or STEPLIB contains the following modules:
CAISMFQ CAS9GLVL
REQUIRED SMF MODULES NOT FOUND: Ensure that the NMSSI STEPLIB definition lists the libraries that contain the required modules.
The expected SAB (System Anchor Block) was not found. This should not happen because SAB should be created in earlier stages of NMSSI processing.
SMF MANAGEMENT ALREADY ACTIVE: Ensure that only one copy of SSI controls SMF activities.
Reason:
SMF facility front runner module terminated due to the following reason described by P1:
IPSMF=NO User specified NO in SSI startup parameter IPSMF.
System Action:
SMF processing is not initialized for this SSI instance.
User Action:
IPSMF=NO Ensure that SMF support is not needed for this SSI instance.
Reason:
The SMF facility front runner module is unable to access CA Common Services level information. This message is related to the processing of the CACS version modules definition table, either standard or modified. This message is issued when the loaded CACS version module does not match any entry in the table defining known version modules, and expected information offsets and values.
This is a warning message. The message does not necessarily indicate problems with the product.
P1 is the reason:
Indicates that the table does not define any CACS modules.
Indicates that the table contains errors.
Indicates empty tables.
Indicates that the version offset is 0.
Indicates that the version offset exceeds the length of the loaded version load module.
Indicates that the specified module fails the eye-catcher check.
Indicates that the region is unable to load the module specified by the table.
Indicates that the region is unable to locate the module specified by the table.
System Action:
None.
User Action:
To resolve the problem
NY3720 SMF Exits registered successfully
NY3002 SMF EXITS REGISTERED ALREADY
If the current version is installed and available through LPALIB or LNKLST, contact Technical Support.
CACS MODULE NOT FOUND
NO CACS VERSION TARGET
TABLE SKIPPED
VERSION OFFSET
OFFSET GT MODLEN
EYECATCHER
Reason:
The SMF facility front runner module is unable to process the CA Common Services version definition table. This message relates to the processing of the CACS version modules definition table, either standard or modified.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The SMF facility front runner module failed processing the CA Common Services version definition table. This message relates to the processing of the CACS version modules definition table, either standard or modified.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
This is part of the output resulting from an SSI STATUS command.
System Action:
Processing continues.
User Action:
None.
Reason:
A THREAD START command failed with return code P1
System Action:
SSI STARTUP fails.
User Action:
Contact Technical Support.
Reason:
A call to register an EPS service failed with return code P1
System Action:
SSI STARTUP fails.
User Action:
Contact Technical Support.
Reason:
An instance of the SMF API is active in another region on an LPAR. Only one instance of the SMF API is allowed to run on each LPAR.
System Action:
SSI STARTUP fails.
User Action:
Locate and terminate the other SMF API SSI region and retry.
Reason:
Both PKTANALYZER=YES and IPSMFAPIREC=YES have been specified in the SSI startup parameters.
System Action:
SSI STARTUP fails.
User Action:
Remove one of the parameters from the SSI startup and retry.
Reason:
A UNIX call P2 to stack P1 failed with errno P3 and errnojr P4.
System Action:
The operation is retried every 30 seconds.
User Action:
For more information about the error, see IBM's UNIX System Services Messages and Codes.
Reason:
A UNIX server in stack P1 terminated the connection with termination code P2.
System Action:
The operation is retried every 30 seconds.
User Action:
For more information about this error, see IBM's UNIX System Services Messages and Codes.
Reason:
The NMI server was unable to retrieve SMF records from the server before they were overwritten.
System Action:
Processing continues - SMF records are lost.
User Action:
Consider increasing the priority of the NMI SSI region.
Reason:
A call to retrieve records from server P1 failed with return value P2.
System Action:
Processing continues—the records are lost.
User Action:
Fore more information about this error, see IBM's Communications Server IP Programmer's Guide and Reference.
Reason:
The P1 service is not enabled on the P2 stack. Because more than one ErrnoJr may cause this message, the errno and ErrnoJr are included in the message.
System Action:
The operation is retried every 30 seconds.
User Action:
Add the NETMONITOR configuration statement to the stack's PROFILE.
Reason:
The user ID associated with the region is not authorized to connect to the P1 service on the P2 stack.
System Action:
The operation is retried every 30 seconds.
User Action:
Ask your security administrator to provide the necessary authorization for the user ID associated with the region to access the Network Management API.
Reason:
A CREATE SOCKET call made to stack P1 failed with errno P2 and errnojr P3.
System Action:
The region terminates with the following message:
NS9501 NMSSI ABEND N-Y4S-03...
User Action:
For more information about this error, see IBM's UNIX System Services Messages and Codes.
Reason:
A call to $NMXEVNT failed with R15= P1 and R0= P2
System Action:
Processing continues.
User Action:
Contact Technical Support.
Reason:
The application has created the SSM environment for the SSM application name P1, and has started to send heartbeat and status information to SSM.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
SSM support detected that the operating system under which SSM initialization is attempted is not at least z/OS V1R6.0.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
If the system is not running at least z/OS V1R6.0, specify SSM=NO.
Reason:
This message starts the SSM status report.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
The SSM support environment was created and activated.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
The indicated SSM status was sent and confirmed.
P1 is the status:
Note: The DOWN status, although sent, is not reported because the status information is not available anymore.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
The SSM heartbeat subtask was started.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
Initialization of SSM support failed.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
If the SSI is running on the LPAR without CA OPS/MVS EMA, remove all SSM initialization parameters, or at least, specify SSM=NO.
If CA OPS/MVS EMA is running on the LPAR, ensure that SSM support is activated.
If CA OPS/MVS EMA support is activated, issue the SHOW STOR=SMGV SSI command and contact CA Support with the output received accompanied with the SSI job log and SSM-activated CA OPS/MVS EMA log.
Reason:
The indicated SSM status was sent and failed.
P1 is the status:
Note: The DOWN status, although sent, is not reported because the status information is not available anymore.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
Review the preceding NY6502 message for diagnostic information.
For assistance, issue the SHOW STOR=SMGV SSI command, collect the SSI activity log, and contact CA Support.
Reason:
The indicated SSM status was sent but not confirmed yet.
P1 is the status:
Note: The DOWN status, although sent, is not reported because the status information is not available anymore.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
The SSM support initialization module activated the SSM status and heartbeat services for the SSM application name P1. At least one status update was successful.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
The SSM support initialization module failed to activate SSM support.
P1 indicates one of the following reasons:
RC is the return code returned by the SSM call.
RS is the reason code, if present, returned by the SSM call.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
For SSM support module(s) missing, verify whether the NMSSM01 and NMSSM02 load modules are present in the load library specification.
For SSM support not available, check whether the SSM-activated CA OPS/MVS EMA is active on the LPAR. If CA OPS/MVS EMA is not active, start it, or if the support is not present, add SSM=NO to the parameters specified by the PARMLIB or JCL PARM.
Otherwise, collect debugging information for the SSM-activated CA OPS/MVS EMA, application job log and activity log, and contact CA Support.
Reason:
The SSM support initialization detected that the SSM STATUS subtask failed.
RC is the return code.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
Check the SSI activity log for any messages that suggest corrective action. Take the corrective action.
If no suggestions are provided or the corrective action fails, issue the SHOW STOR=SMGV SSI command, collect the SSI activity and job logs, and contact CA Support.
Reason:
The SSM support module discovered that one of the previously sent SSM status updates did not terminate.
This condition can indicate a very busy system or problems with CA OPS/MVS EMA.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
Check z/OS activity indicators, the responsiveness of the SSI and CA OPS/MVS EMA, and any abnormal indicators.
If you cannot resolve the problem, issue the SHOW STOR=SMGV SSI command, collect the SSI activity and job logs, collect the SSM-activated CA OPS/MVS EMA log, and contact CA Support.
Reason:
Errors were reported while detaching SSM support subtask.
RC is the return code.
RS is the subtask abend information.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
Check the SSI activity log for any messages that suggest corrective action. Take the corrective action.
If no suggestions are provided or the corrective action fails, issue the SHOW STOR=SMGV SSI command, collect the SSI activity and job logs, and contact CA Support.
Reason:
The SSM support initialization module started the SSM heartbeat service.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
The SSM support module detected the call with invalid parameters and requires deactivation of the SSM support.
System Action:
None.
User Action:
Issue the SHOW STOR=SMGV SSI command, collect the SSI activity and job logs, and contact CA Support.
Reason:
The SSM support initialization module activated the SSM status and heartbeat services for the SSM application name P1. At least one status update was successful.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
The SSM support initialization module failed to activate SSM support.
P1 indicates one of the following reasons:
RC is the return code returned by the SSM call.
RS is the reason code, if present, returned by the SSM call.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
For SSM support module(s) missing, verify whether the NMSSM01 and NMSSM02 load modules are present in the load library specification.
For SSM support not available, check whether the SSM-activated CA OPS/MVS EMA is active on the LPAR. If CA OPS/MVS EMA is not active, start it, or if the support is not present, add SSM=NO to the parameters specified by the PARMLIB or JCL PARM.
Otherwise, collect debugging information for the SSM-activated CA OPS/MVS EMA, application job log and activity log, and contact CA Support.
Reason:
The SSM support initialization detected that the SSM STATUS subtask TUS failed.
RC is the return code.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
Check the region activity log for any messages that suggest corrective action. Take the corrective action.
If no suggestions are provided or the corrective action fails, issue the SHOW STOR=SMGV command, collect the activity and job logs, and contact CA Support.
Reason:
The SSM support module discovered that one of the previously sent SSM status updates did not terminate.
This condition can indicate a very busy system or problems with CA OPS/MVS EMA.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
Check z/OS activity indicators, the responsiveness of the product region and CA OPS/MVS EMA, and any abnormal indicators.
If you cannot resolve the problem, issue the SHOW STOR=SMGV command, collect the region activity and job logs, collect the SSM-activated CA OPS/MVS EMA log, and contact CA Support.
Reason:
Errors were reported while detaching SSM support subtask.
RC is the return code.
RS is the region abend information.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
Check the region activity log for any messages that suggest corrective action. Take the corrective action.
If no suggestions are provided or the corrective action fails, issue the SHOW STOR=SMGV command, collect the region activity and job logs, and contact CA Support.
Reason:
The SSM support initialization module started the SSM heartbeat service.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
The application has created the SSM environment for the SSM application name P1, and has started to send heartbeat and status information to SSM.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
SSM support detected that the operating system under which SSM initialization is attempted is not at least z/OS V1R6.0.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
If the system is not running at least z/OS V1R6.0, specify SSM=NO.
Reason:
This message starts the SSM status report.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
The SSM support environment was created and activated.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
The indicated SSM status was sent and confirmed.
P1 is the status:
Note: The DOWN status, although sent, is not reported because the status information is not available anymore.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
The SSM heartbeat subtask was started.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
Initialization of SSM support failed.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
If the region is running on the LPAR without CA OPS/MVS EMA, remove all SSM initialization parameters, or at least, specify SSM=NO.
If CA OPS/MVS EMA is running on the LPAR, ensure that SSM support is activated.
If CA OPS/MVS EMA support is activated, issue the SHOW STOR=SMGV command, and contact CA Support with the output, accompanied with the region job log and SSM-activated CA OPS/MVS EMA log.
Reason:
The indicated SSM status was sent, but the region failed to receive confirmation.
P1 is the status:
Note: The DOWN status, although sent, is not reported because the status information is not available anymore.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
Review the preceding NY6602 message for diagnostic information.
For assistance, issue the SHOW STOR=SMGV region command, collect the activity log, and contact CA Support.
Reason:
The indicated SSM status was sent, but receipt of the status is not confirmed yet.
P1 is the status:
Note: The DOWN status, although sent, is not reported because the status information is not available anymore.
Note: SSM support sends heartbeat and status information to System State Manager (SSM), which is a component of CA OPS/MVS EMA. For more information about SSM, see the CA OPS/MVS EMA documentation.
System Action:
None.
User Action:
None.
Reason:
FTP Exit Control Table was created or was already present.
System Action:
None.
User Action:
None.
Reason:
NMSSI initialization encountered errors during FTP Exit Control Table (FXTB) creation.
P1 is the reason code returned by the creation module:
08-FXTB is being created by another task.
12-SAB does not exist.
16-SAB location error.
20-Bad control blocks.
24-Private storage shortage.
System Action:
None.
User Action:
Depends on the reason provided:
08-There is another task in the same LPAR creating FXTB. Rerun your program, if needed.
12-SAB was not created. Ensure that at least one NMSSI is started and repeat the task.
16-Internal error; contact Technical Support.
20-Internal error; contact Technical Support.
24-Private storage shortage; increase the region size. Contact Technical Support if the problem persists.
Reason:
The SOLVESSI FTPX command processor detected that the mandatory function code describing the function to perform is missing.
System Action:
SOLVESSI FTPX command processing terminates.
User Action:
Check valid SOLVESSI FTPX function codes and reenter the command.
Reason:
The SOLVESSI FTPX command processor detected that the function code describing the function to perform is invalid.
System Action:
SOLVESSI FTPX command processing terminates.
User Action:
Check valid SOLVESSI FTPX function codes and reenter the command.
Reason:
The SOLVESSI FTPX command processor detected that the function code argument P1 for the function to perform is invalid. This may indicate that the argument type is not compatible with the function (not a valid hexadecimal number) or that it is of the wrong length.
System Action:
SOLVESSI FTPX command processing terminates.
User Action:
Check valid arguments for the function of the SOLVESSI FTPX command and reenter the correct command.
Reason:
The SOLVESSI FTPX DEBUG command has completed setting debug flags.
System Action:
None.
User Action:
None.
Reason:
The expected System Anchor Block cannot be found. This should not happen because the SAB should be created in earlier stages of SOLVESSI processing.
System Action:
SOLVESSI processing continues.
User Action:
Check if the SOLVESSI log contains any previous messages related to SAB creation or any other abnormal situations. If you are unable to resolve the problem, contact Technical Support.
Reason:
The expected FTP Exit Control Table cannot be found. This should not happen because the FXTB should be created in earlier stages of SOLVESSI processing.
System Action:
SOLVESSI processing continues.
User Action:
Check if the SOLVESSI log contains any previous messages related to FXTB creation or any other abnormal situations. If you are unable to resolve the problem, contact Technical Support.
Reason:
This message is issued as a response to an SSI STATUS command and indicates that the simple event service is active. The EPS service name is displayed, as well as the current numbers of registered listeners and senders.
System Action:
None.
User Action:
None.
Reason:
This message is issued as a response to a SHOW SSISTATS command and indicates that the simple event service is active. The number of listeners, events received, and senders is displayed.
System Action:
None.
User Action:
None.
Reason:
This message is issued as a response to a SHOW SSISTATS command and provides column headings for the following NY8012 messages. The columns are:
SYSNAME The system name that the sender or receiver resides on JOBNAME The jobname for the sender or receiver EVT-NAME The event name that the sender or receiver has registered for MODE The mode: SEND or RECV #-EV The number of events sent to a receiver, or received from a sender DESC... The description supplied by the sender or receiver when connecting
System Action:
None.
User Action:
None.
Reason:
This message is issued as a response to a SHOW SSISTATS command and provides information about a simple event sender or receiver. Refer to message NY8011 for column descriptions.
System Action:
None.
User Action:
None.
Reason:
This message is issued as a response to a SHOW SSISTATS command and provide a column heading for the following NY8014 messages. The column is:
MASK The mask value that was passed on registration. The value is displayed in hex.
System Action:
None.
User Action:
None.
Reason:
This message is issued as a response to a SHOW SSISTATS command and provides information about a simple event sender or receiver. Refer to message NY8013 for column descriptions.
System Action:
None.
User Action:
None.
Reason:
This message is issued during NMSSI startup if the XEVNT=YES operand was specified, but either the XMS=NO operand was specified, or the current operating system does not support (ESA-style) cross-memory services.
System Action:
The SOLVESSI startup fails.
User Action:
Change any XMS=NO parameter in the startup parms to XMS=YES. If the operating system does not support MVS/ESA-style Cross-memory services, the XEVNT facility cannot be used.
Reason:
This message is issued during SOLVESSI startup if the XEVNT=YES operand was specified, but the XAPI=NO operand was specified.
System Action:
The SOLVESSI startup fails.
User Action:
Change any XAPI=NO operand in the startup parms to XAPI=YES.
Reason:
The system ENQ for resource name $SYS.SIMPLE.EVENT of queue SOLVEEPS failed. This message is issued during SOLVESSI startup if the XEVNT=YES operand was specified. Another SOLVESSI address space has XEVNT=YES specified.
System Action:
The SOLVESSI region terminates.
User Action:
Ensure that only one SOLVESSI region has the XEVNT=YES operand specified.
Use the MVS system command D GRS,RES=(SOLVEEPS,$SYS.SIMPLE.EVENT) to determine the job name of the current owner.
Use the MVS system command D GRS,RES=(NMSSID,*) to determine the SSID of the current owner.
Reason:
This message is logged to the SOLVESSI log when a new connection to the Simple Event Sender occurs. The message shows information about the connector:
TP L (listener) or S (sender) SN The SYSNAME of the connector JN The JOBNAME of the connector NM The EVENT NAME supplied by the connector MS The first 4 bytes of the MASK supplied by the connector DE The description supplied by the connector
System Action:
None.
User Action:
None.
Reason:
This message is logged to the SOLVESSI log when a disconnection from the Simple Event Sender occurs. The message shows information about the connector:
TP L (listener) or S (sender) SN The SYSNAME of the connector JN The JOBNAME of the connector NM The EVENT NAME supplied by the connector MS The first 4 bytes of the MASK supplied by the connector DE The description supplied by the connector
If the disconnection of a sender occurs due to excessive errors, this is indicated by a suffix on the message.
System Action:
None.
User Action:
None.
Reason:
This message is returned as the response to an EPS CONNECT request to the simple event router, when the connection MDO (mapped by $NMSEVSM) CONNTYPE field has an invalid value.
System Action:
The EPS CONNECT is rejected.
User Action:
Correct the signon request MDO and retry.
Reason:
This message is returned as the response to an EPS CONNECT request to the simple event router, when the connection MDO (mapped by $NMSEVSM) contains a duplicate field. The field key and name is shown, as well as the (hex) offset into the MDO of the length/key/data.
System Action:
The EPS CONNECT is REJECTed.
User Action:
Correct the signon request MDO and retry.
Reason:
This message is returned as the response to an EPS CONNECT request to the simple event router, when the connection MDO (mapped by $NMSEVSM) contains a field value that is too long. The field key and name is shown, as well as the (hex) offset into the MDO of the length/key/data.
System Action:
The EPS CONNECT is REJECTed.
User Action:
Correct the signon request MDO and retry.
Reason:
This message is returned as the response to an EPS CONNECT request to the simple event router, when the connection MDO (mapped by $NMSEVSM) has an internal structure error. The (hex) offset into the MDO where the problem was detected is shown.
System Action:
The EPS CONNECT is REJECTed.
User Action:
Correct the signon request MDO and retry.
Reason:
This message is returned as the response to an EPS CONNECT request to the simple event router, when the connection MDO (mapped by $NMSEVSM) is missing a required field. The field key and name is shown.
System Action:
The EPS CONNECT is REJECTed.
User Action:
Correct the signon request MDO and retry.
Reason:
This message is returned as the response to an EPS CONNECT request to the simple event router, when the connection MDO (mapped by $NMSEVSM) has a field with an invalid length. The field key and name is shown.
System Action:
The EPS CONNECT is rejected.
User Action:
Correct the signon request MDO and retry.
Reason:
This message is written to the system console when a subtask engine instance ABENDs. The message contains the abend code, jobname,date and time of the abend.
System Action:
A formatted dump and system dump are taken. This message is followed by the NZ8602 and NZ8603 messages with additional information.
User Action:
Contact your support office with the details of the ABEND.
Reason:
This message is written to the system console when a subtask engine instance ABENDs. It follows the NZ8601 message and contains information about the ABEND. The fields are:
SRC=sss - The source of the abend information. sss is either:
AB - meaning that the information in this and the NS9503 message was derived from the PSW and registers at the time of the abend, or SE - meaning that the information was derived from the registers and PSW from the region's primary RB
PRD=pp1 - The product name
VRS=vvv - The product version (for example, V4.1)
PUT=pp2 - The product PUT level
ABC=ccc - The ABEND code: S-xxx for a SYSTEM abend U-nnn for a user abend N-aaa-bb for an internal abend
System Action:
See message NZ8601.
User Action:
See message NZ8601.
Reason:
This message is written to the system console when a subtask engine instance ABENDs. It follows the NZ8602 message and contains information about the ABEND. The fields are:
ALM=aaa - The ABEND load module
ALO=bbb - The offset within the ABEND load module
ACS=ccc - The ABEND CSECT, if it could be identified
ACO=ddd - The offset within the ABEND CSECT, if the CSECT could be identified
LLM=eee - The last apparent active load module
LCS=fff - The last apparent CSECT
System Action:
See message NZ8601.
User Action:
See message NZ8601.
|
Copyright © 2014 CA.
All rights reserved.
|
|