|
|
Reason:
The Web Server interface procedure $W3CALL failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2.
System Action:
The request is rejected and procedure $W3CALL terminates.
User Action:
Report the error to your System Administrator.
Reason:
The Web Server interface procedure $W3CALL failed during register processing because a server was already registered.
System Action:
The request is rejected and procedure $W3CALL terminates.
User Action:
Report the error to your System Administrator.
Reason:
The Web Server interface procedure $W3CALL failed during deregister processing because no server was registered.
System Action:
The request is rejected and procedure $W3CALL terminates.
User Action:
Report the error to your System Administrator.
Reason:
The Web Server interface procedure $W3CALL failed during processing because the web server process could not be started.
System Action:
The request is rejected and procedure $W3CALL terminates.
User Action:
Report the error to your System Administrator.
Reason:
The Web Server interface procedure $W3CALL timed out waiting for a response from the web server process.
System Action:
The request is rejected and procedure $W3CALL terminates.
User Action:
Report the error to your System Administrator. Check the log for error messages relating to the web server process, $W3SV10S.
Reason:
The Web Server interface has accepted a request to process on port P2.
System Action:
The web server registers on the named port.
User Action:
You can access the web server using a Uniform Resource Locator (URL) of the form 'http://IPaddress:P2/P1', where:
P2 is the port number (required if not using port 80)
P1 is the name of the web server component
IPaddress is the IP Host name or address of the local system Use the SHOW TCPIP command to display the local host name and IP address.
Reason:
The Web Server interface has accepted a request to stop processing on port P2.
System Action:
The web server removes the web component from the active list and if no longer required deregisters the associated port.
User Action:
None.
Reason:
A Web command was issued that specified an invalid positional parameter. The command requested was P1 and the invalid parameter was P2.
System Action:
The command is rejected.
User Action:
Correctly specify the parameter P2.
Reason:
A Web command was issued that specified an invalid keyword parameter. The command requested was P1, the keyword in error was P2 and the invalid value was P3.
System Action:
The command is rejected.
User Action:
Specify a valid value for the keyword parameter P2.
Reason:
An invalid Web command was specified.
System Action:
The command is rejected.
User Action:
Specify a valid Web command.
Reason:
This message is the heading line for the SHWEB USERS command.
System Action:
None.
User Action:
See the explanation for message W3CALL12 for details of the individual columns.
Reason:
This message is the detail line for the SHWEB USERS command. P1 Is the userid of a user currently logged onto the system via the Web interface. P2 Is the IP address from which the user is access the system. P3 Is the NCL ID of the Web server process for the user session.
System Action:
None.
User Action:
None.
Reason:
This message is the end message for the SHWEB USERS command. P1 is the number of users listed and logged onto the system via the Web interface. P2 is the total number of Web sessions listed.
System Action:
None.
User Action:
None.
Reason:
The WebCenter Command Entry page reached or exceeded the Maximum Wait For Response limit before a valid end message was received. The output may be incomplete.
System Action:
The Command Entry page is displayed with all output gathered before the wait limit was reached.
User Action:
Examine the displayed output. If you consider it to be incomplete, increase the Maximum Wait For Response value and execute the command again.
Reason:
The WebCenter Command Entry page reached or exceeded the Maximum Lines Returned limit before a valid end message was received. The output may be incomplete.
System Action:
The Command Entry page is displayed with all output gathered before the line limit was reached.
User Action:
Examine the displayed output. If you consider it to be incomplete, increase the Maximum Lines Returned value and execute the command again.
Reason:
The File Manager $W3DB000 was called with an invalid action request. The unsupported action was P1 .
System Action:
The request is rejected and procedure $W3DB000 terminates.
User Action:
Report the error to your System Administrator.
Reason:
An unrecoverable run time error was encountered by File Manager procedure $W3DB000. This heads a message group consisting of the File Manager request parameters and error details in message W3DB0003.
System Action:
The request is abandoned.
User Action:
Contact your local System Administrator.
Reason:
This is part of a message group issued for unrecoverable File Manager errors. It contains the File Manager request parameters and the run-time error details.
System Action:
The request is abandoned.
User Action:
Contact your local System Administrator.
Reason:
A file could not be added with the appl. specified, because the file already exists in the repository with a different appl.
P1 is the File Manager action that was requested.
P2 is the file name.
P3 is the specified application.
P4 is the application that the file already exists with.
System Action:
The File Manager $W3DB000 rejects the request.
User Action:
Review the request parameters: either replace the existing file by changing the requested appl, or create a new file by changing the requested file name.
Reason:
The contents of a PDS member have been successfully copied to a file in the repository.
P1 and P2 are the DD and member names.
P3 is the file name.
P4 is the userid.
System Action:
None.
User Action:
None. The file is now available for GET requests.
Reason:
The parameters passed on the P1 command for file P2 were in error:
P3 contains the error details.
System Action:
The request is rejected.
User Action:
Correct the parameters and retry the request.
Reason:
A 'privileged' user has been permitted update access to a MODS file other than the top level MODSUSR file.
System Action:
The File Manager $W3DB000 continues processing the request.
User Action:
None.
Reason:
The user has requested an update of a MODS DD other than MODSUSR, this is not permitted.
System Action:
The File Manager $W3DB000 rejects the request.
User Action:
None.
Reason:
The user has requested an update of an invalid MODS DD number. Valid DD numbers range from 1 to the total number of files in the MODS concatenation. P2 is the failing request, and P3 is the filename.
System Action:
The request is rejected.
User Action:
None.
Reason:
A file has been successfully updated in the repository.
P1 is the file name.
P2 is the operation (STORED/UPDATED) that was completed.
P4 is the MODS DD that the update was performed in.
System Action:
Any cached copy of the file will be deleted. The next GET of the file will return the updated copy.
User Action:
None. The file that was just updated/added/replaced is now available for GET processing.
Reason:
The File Manager $W3DB000 encountered an error trying to perform the requested action. P1 is the action that failed, P2 is the file name.
System Action:
The request is abandoned.
User Action:
Contact your Systems Administrator. Previous messages on the SOLVE log should indicate the exact error.
Reason:
A request was received to delete file P1 from DD P2 , however the file is located in DD P3 Files in P3 are visible to directories and available for GET requests but may only be updated/deleted by authorized users.
System Action:
The file is not deleted.
User Action:
None.
Reason:
A file has been successfully deleted from the indicated MODS DD.
System Action:
The file is deleted. Any cached copy will also be deleted.
User Action:
None. Note that if another copy of the file exists in another MODS DD, that copy will still be visible and available for GET processing.
Reason:
The indicated file was not found in the indicated MODS DD. (The file may exist in other MODS DD levels).
System Action:
The file is not deleted.
User Action:
None.
Reason:
A line by line GET was requested, but the specified file does not contain text.
System Action:
The request is ignored.
User Action:
None.
Reason:
This message is produced when Web Data Services tracing is active.
System Action:
None.
User Action:
None.
Reason:
A possible discrepancy was detected during a P1 operation on file
P2 . P3 contains further details. This does not necessarily mean that there is a problem with the actual data. It can occur, for example, as a result of incorrect character translations.
System Action:
Processing continues.
User Action:
None.
Reason:
A GET request was received, but the specified file conversion is not supported by the File Manager.
P1 is the file name.
P2 is the format that the file is physically stored in. P3 is the format that the requester wanted the file returned as.
System Action:
The GET request is abandoned.
User Action:
None.
Reason:
Duplicate TO and FROM file names were specified for a P1 request.
System Action:
The request is ignored.
User Action:
None.
Reason:
Rename and update requests are restricted to files in the top level MODS DD (usually MODSUSR).
System Action:
The RENAME or UPDATE request is ignored.
User Action:
None.
Reason:
A file has been successfully copied or renamed.
P1 is the "from" file
P2 is the operation (copy or rename)
P3 is the "to" file
System Action:
None.
User Action:
None.
Reason:
The File Manager $W3DB000 received an error on an OML File verb.
P1 is the file operation that was attempted.
P6 is the full or partial key used, P7 is the FILEID. The remaining fields contain error information returned by the File verb
System Action:
The request is abandoned and the File Manager terminates.
User Action:
If the errors indicate unrecoverable file damage, contact your Systems Administrator.
Reason:
The indicated file was not found in any of the concatenated MODS DDs.
System Action:
None.
User Action:
None.
Reason:
A user has requested an update operation on the specified file, but the file could not be 'locked'. Usually this means that another user is already updating the same file (eg. with CAS Edit).
System Action:
The update operation is not allowed.
User Action:
Retry the operation later.
Reason:
A user has requested a PDS member to be stored as a file on the repository, but the member could not be read.
System Action:
The STOREMEM operation is abandoned.
User Action:
Contact your Systems Administrator.
Reason:
An attempt was made to store a file named P1 on the Repository, but the requested file name is invalid. P2 describes the error.
System Action:
The request is abandoned - the new file is not stored.
User Action:
None.
Reason:
The indicated file name is too long - files stored in the Repository are restricted to file names of 60 characters or less.
System Action:
The GET request returns a 'file not found' condition.
User Action:
None.
Reason:
The File Manager $W3DB000 has received request P1 but found that the required initialization has not yet been attempted.
System Action:
The File Manager will call the initialization procedure, then continue processing.
User Action:
None. This is an informational message only.
Reason:
The File Manager $W3DB000 has received request P1 but found that the required initialization is still in progress and has not yet completed.
P2 is the user who requested the initialization.
System Action:
The File Manager will wait for the initialization lock to expire, then will continue processing the request.
User Action:
None. This is an informational message only.
Reason:
The File Manager $W3DB000 has received request P1 but has been unable to process it because the required initialization has not completed. RC 1: INIT was found to have been already attempted, and failed. RC 2: INIT was found to be in progress, but the WAIT for it failed. RC 3: INIT was started by this procedure, but failed to complete.
System Action:
The request is abandoned. If the error condition is permanent, all subsequent File Manager requests will also fail.
User Action:
Contact your Systems Administrator.
Check the SOLVE Activity log for any error messages issued during the $W3DB12W:INIT initialization process.
Reason:
The File Manager $W3DB000 received a GET request with the SEND parameter for a file greater than p4 bytes. This message is issued at the start of and at the completion of the send operation, and includes the highest individual socket send return code. This message is only issued for large files, typically software update downloads.
System Action:
SEND processing proceeds as normal.
User Action:
Usually, none. If the operation completes with a return code greater than 0, contact your Systems Administrator: other SOLVE log messages should indicate the error. If the SEND operation completes with a return code of zero but the download fails, contact your PC Support staff.
Reason:
The copy of the web file in question found in p1 was compared with the copy at the next level of the MODS concatenation and they were found to be identical.
System Action:
Compare processing ends normally.
User Action:
If you are comparing the copies of this file with a view to deleting the copy in p1 then it should be safe to delete it.
Reason:
The indicated file was not found in the indicated MODS DD. (The file may exist in other MODS DD levels).
System Action:
Compare processing terminates as it is only valid for a file that exists in the highest MODS concatenation.
User Action:
None.
Reason:
The copy of the web file in question found in p1 was compared with the copy found in p3 and they were found to be of different sizes.
System Action:
Compare processing terminates.
User Action:
None.
Reason:
The copy of the web file in question found in p1 was compared with the copy found in p3 and they were found to contain a different number of data records.
System Action:
Compare processing terminates.
User Action:
None.
Reason:
File p1 was found to occur only once in the MODS concatenation.
System Action:
Compare processing terminates.
User Action:
None.
Reason:
The copy of the web file in question found in p1 was compared with the copy found in p3 and they were found to contain different content. The first character in the example shown highlights the difference.
System Action:
Compare processing terminates.
User Action:
None.
Reason:
The Web Server Include Processor $W3DB01U failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $W3DB01U terminates.
User Action:
Report the error to your System Administrator.
Reason:
Informational message that displays the return code and any message produced by the Web Server Include Processor.
System Action:
Procedure $W3DB01U terminates.
User Action:
None.
Reason:
The Web Server Include Processor $W3DB01U tried to process an include directive with the FILE keyword but the value passed either began with a '/' or included '../' within the string.
System Action:
The request is rejected and procedure $W3DB01U terminates.
User Action:
Change the Include directive to specify VIRTUAL= instead of FILE=.
Reason:
The Web Server Include Processor $W3DB01U failed during the processing of the Include parameters. The parameters did not contain a valid FILE or VIRTUAL keyword.
System Action:
The include is rejected and procedure $W3DB01U terminates.
User Action:
Change the include directive to specify FILE= or VIRTUAL=.
Reason:
The Web Server Include Processor $W3DB01U received a directive to include the file P1 and discovered this file is already included at a higher level. Further inclusion would lead to a recursive loop.
System Action:
The include request is rejected and procedure $W3DB01U terminates.
User Action:
Change the include structure so that an included file does not include itself at a lower level. That is, file A cannot include file B which has an include for file A. This would lead to an include loop.
Reason:
Procedure $W3DB12W has finished File Manager initialization processing.
P1 is the completion status. P2 is the error text, if any. A status of 'complete' indicates the initialization was successful. A status of 'in error' indicates the initialization terminated abnormally, because of error condition P2 .
System Action:
If the initialization completed successfully, the Web Server and other procedures may now retrieve data from the File Manager. If the initialization ended in error, processing continues, but file retrieval requests, and general Web access, will not function correctly.
User Action:
If the initialization has ended in error, contact your System Administrator.
Reason:
This message heads a group that lists the order and file names in the File Manager Search path. This is the MODS DD concatenation. Web Files are searched for in the listed files beginning from file 1. The first occurrence of the file is returned to the Web Server.
System Action:
None.
User Action:
None.
Reason:
This message is part of a message group headed by W3DB1202 See that message for details.
System Action:
None
User Action:
None
Reason:
Web Data Request processing is not possible since previous File Manager initialization attempts failed.
System Action:
The request is abandoned and the Web Data Request Manager $W3DB12W terminates. No Web access to SOLVE products is available.
User Action:
Contact your Systems Administrator. Log messages will describe the specific failure of File Manager Initialization. This is an extremely serious error - no Web access will be available until the problem is rectified and the initialization successfully run.
Search the SOLVE Activity log for previous W3DB12* error messages describing the initialization error. These may have occured at some time previous to this failing request - look around the time of region startup and SOLVE product initialization.
Reason:
A call was made to procedure $W3DB12W for File Manager initialization processing, but the initialization lock was already held. Usually, this is a result of another copy of this procedure running at the same time.
System Action:
This request is abandoned. Normally, the original copy of this procedure, ie. the one that already has the lock, will continue processing and complete the initialization.
User Action:
This is usually a 'normal' condition. If any subsequent Web File error messages occur, contact your Systems Administrator.
Reason:
An unrecoverable run time error was encountered by the Web Data Request processing procedure $W3DB12W. This heads a message group consisting of the Web Data GET/POST request parameters and error details in message W3DB1207
System Action:
Server processing of the HTTP GET or POST request is abandoned. Processing continues with the next request.
User Action:
Contact your local System Administrator.
Reason:
This is part of a message group issued for unrecoverable Web Data request errors. It contains the HTTP GET/POST request parameters and run-time error details.
System Action:
The HTTP GET/POST request is abandoned. Processing continues with the next request.
User Action:
Contact your local System Administrator.
Reason:
The Web Data Request Manager $W3DB12W has received a request for File Manager initialization processing from procedure P1 .
System Action:
If initialization has not already been done, it commences. If initialization has already been successfully completed, as a result of a previous call, then this request is ignored and processing continues.
User Action:
None.
Reason:
The Web File Server $W3DB13S failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $W3DB13S terminates.
User Action:
Report the error to your System Administrator.
Reason:
An unrecoverable run time error was encountered by File Server procedure $W3DB13S. This heads a message group consisting of the File Server request parameters and error details in message W3DB1303.
System Action:
The request is abandoned.
User Action:
Contact your local System Administrator.
Reason:
This is part of a message group issued for unrecoverable File Server errors. It contains the File Server request parameters and the run-time error details.
System Action:
The request is abandoned.
User Action:
Contact your local System Administrator.
Reason:
An error was encountered while retrieving the data for file P3
System Action:
The request is abandoned - the file data cannot be retrieved.
User Action:
Contact your local System Administrator.
Reason:
This message is the detail line for the response to a WEB command. "WEB ?" lists the available WEB commands and their parameters.
System Action:
None.
User Action:
None.
Reason:
The SHTML File Type Handler $W3DB20H failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $W3DB20H terminates.
User Action:
Report the error to your System Administrator.
Reason:
The SHTML File Type Handler $W3DB20H could not expand the SHTML file
P1 . The Include Processor $W3DB01U returned code P2 P3
System Action:
The request is rejected and procedure $W3DB20H terminates.
User Action:
Report the error to your System Administrator.
Reason:
The ESP File Type Handler $W3DB30H failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $W3DB30H terminates.
User Action:
Report the error to your System Administrator.
Reason:
The ESP File Type Handler $W3DB30H could not expand the ESP file
P1 . The Include Processor $W3DB01U returned code P2 P3
System Action:
The request is rejected and procedure $W3DB30H terminates.
User Action:
Report the error to your System Administrator.
Reason:
The Web File Cache Manager $W3DB40C failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is rejected and procedure $W3DB40C terminates.
User Action:
Report the error to your System Administrator.
Reason:
The Web File Cache Manager has processed request P1
ENABLE - Web File Caching is now enabled.
DISABLE - Web File Caching is now disabled.
EMPTY - all entries in the Web File Cache have been deleted.
System Action:
As above
User Action:
None
Reason:
This message number refers to a message group issued in response to a 'Query' request to the Web File Cache Manager $W3DB40C These messages contain information about the current status of Web File Caching.
System Action:
None
User Action:
None
Reason:
The Web File Cache Manager $W3DB40C received an error while attempting operation P1 on the Global Cache Vartable. The FDBK code was P2 The key was P3
System Action:
The Web File Cache Manager abandons the current action.
User Action:
Contact your Systems Administrator.
Reason:
The Web File Negative Cache Manager $W3DB41C failed during request processing because it was passed an invalid keyword value. The keyword was P1 and the invalid value was P2 .
System Action:
The request is ignored.
User Action:
Report the error to your System Administrator.
Reason:
The Web File Negative Cache Manager has processed request P1
ENABLE - Web File Negative Caching is now enabled.
DISABLE - Web File negative Caching is now disabled.
EMPTY - all entries in the Web File Negative Cache have been deleted.
System Action:
As above
User Action:
None
Reason:
This message number refers to a message group issued in response to a 'Query' request to the Web File Negative Cache Manager $W3DB41C These messages contain information about the current status of Web File Negative Caching.
System Action:
None
User Action:
None
Reason:
An unrecognized internal request was encountered by the Web File Utility Service Procedure $W3DB90L
System Action:
The request is abandoned.
User Action:
Contact your local System Administrator.
Reason:
This message indicates the completion status of the Web File Utilities Top Level Directory list function.
System Action:
None
User Action:
None
Reason:
An unrecognized internal request was encountered by the Web File Utility Service Procedure $W3DB91L
System Action:
The request is abandoned.
User Action:
Contact your local System Administrator.
Reason:
An unrecoverable run time error was encountered by the Web File Utility service procedure $W3DB91L. This heads a message group consisting of the request parameters and error details in message W3DB9103
System Action:
The request is abandoned.
User Action:
Contact your local System Administrator.
Reason:
This is part of a message group issued for unrecoverable Web File Utility errors. It contains the request parameters and the run-time error details.
System Action:
The request is abandoned.
User Action:
Contact your local System Administrator.
Reason:
This message is part of a message group issued in response to a 'I' line command entered in option /CAS.W (Web File Utilities).
These messages contain information about what MODS files a Web File exists in, plus size and type statistics about the file.
System Action:
None
User Action:
None
Reason:
This message indicates the completion status of the Web File Utilities option that was selected. Depending on the option, this status may contain information such as file counts and CAS Edit results.
System Action:
None
User Action:
None
Reason:
An invalid parameter value was passed to the XML Encode/Decode utility. P1 is the parameter P2 is the value that was supplied
System Action:
The XML document is not processed.
User Action:
Report the error to your System Administrator.
Reason:
An XML document could not be parsed because it contained syntax that is either invalid or not supported. P1 is a description of the problem P2 is the fragment of the XML document containing the error
System Action:
The XML document is not parsed.
User Action:
Report the error to your System Administrator.
Reason:
The DATA keyword parameter was specified in a call to the XML Encode/Decode utility, but the variable did not contain any data. P1 is the variable name that was supplied
System Action:
The XML document is not processed.
User Action:
Report the error to your System Administrator.
Reason:
An invalid OML stem name was specified in the VAR keyword parameter that was passed to the XML Encode/Decode utility. The variable name must conform to OML naming rules, be no longer than 8 characters, and end in a period (.). P1 is the VAR parameter that was supplied.
System Action:
The XML document is not processed.
User Action:
Report the error to your System Administrator.
Reason:
This is a trace message generated by the XML Encode/Decode facility when the TRACE keyword parameter is set to YES.
System Action:
None.
User Action:
None.
Reason:
The XML Decode utility could not parse an XML document because it contained an invalid element name, attribute name or value. P1 contains the name of the element that could not be parsed
System Action:
An error message is returned to the calling procedure.
User Action:
Report the problem to your system administrator.
Reason:
This is an Executable Server Page interpreter trace message.
System Action:
None.
User Action:
None.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The directive end delimiter was not found. Start of the directive being processed is P1.
System Action:
Processing for the file terminates.
User Action:
Ensure that the directive end delimiter %> is present in the source at the end of the directive specification.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The directive indicator character specified is not recognized. P1 is the character found and P2 is the directive being processed.
System Action:
Processing for the file terminates.
User Action:
Specify one of the following directive indicators:
'=' - Equals character for output directives '@'
- At character for processing directives ' '
- blank character for scripting directives
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The processing directive keywords specified were invalid. The message
P1 details the error and P2 is the directive being processed.
System Action:
Processing for the file terminates.
User Action:
Ensure that the processing directive statement has a valid keyword syntax.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The substitution character specified is not allowed. P1 is the character specified and P2 is the permissable set of characters. The directive being processed is P3.
System Action:
Processing for the file terminates.
User Action:
You can only specify one of the characters in P2.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The variable reference specified in the output directive is invalid. The variable is P1 and the directive being processed is P2.
System Action:
Processing for the file terminates.
User Action:
You must specify a valid variable name after the ampersand character.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The package and/or the function name specified in the output directive is invalid. The name is P1 and the directive being processed is P2.
System Action:
Processing for the file terminates.
User Action:
You must specify a valid member name as the package name and a function name that is in the package specified.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The output directive keywords specified were invalid. The message
P1 details the error and P2 is the directive being processed.
System Action:
Processing for the file terminates.
User Action:
Ensure that the PARMnn keywords are correctly specified.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The scripting directive verb specified was invalid. The verb is P1 and the directive being processed is P2.
System Action:
Processing for the file terminates.
User Action:
You must specify a valid scripting verb.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The scripting directive keywords specified were invalid. The message
P1 details the error and P2 is the directive being processed.
System Action:
Processing for the file terminates.
User Action:
Ensure that the keywords are correctly specified.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The package and/or the procedure name specified in the CALL scripting directive is invalid. P1 is the procedure specified and the directive being processed is P2.
System Action:
Processing for the file terminates.
User Action:
You must specify a valid member name for the package, followed by a : (i.e. the colon character), followed by the name of a procedure in the specified package, or specify only the procedure name as a valid member name.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
Variable substitution encountered an error while processing the specifications of directive P1.
System Action:
Processing for the file terminates.
User Action:
Ensure that you specify valid variable names.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
A directive failed a procedure or function call. The procedure or function is P1, the statement line number in error is P2, the error message is P3 and the directive being processed is P4. Depending on the nature of the error it may or may not be possible to display the directive being processed.
System Action:
Processing for the file terminates.
User Action:
Check the error message and correct the problem in the called procedure or function.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
While performing variable substitution an invalid variable was encountered. The variable name is P1 and P2 is additional information about the error.
System Action:
Processing for the file continues, however the data being substituted will remain as is.
User Action:
Ensure that you specify valid variable names.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
An invalid keyword value was specified for a scripting directive. The keyword is P1, the value in error is P2 and the directive being processed is P3.
System Action:
Processing for the file terminates.
User Action:
Specify a valid value for the keyword identified.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
A directive that has mutually exclusive keywords, of which one is required, did not have the correct keyword specification. The mutually exclusive set of keywords are P1 and the number of these keywords that was specified is P2 and the directive being processed is P3.
System Action:
Processing for the file terminates.
User Action:
You MUST specify ONLY one of the keywords listed.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The keyword P1 was specified and it cannot be specified together with any one of the keywords P2. The directive being processed is P3.
System Action:
Processing for the file terminates.
User Action:
Either remove keyword P1 or do not specify one of the keywords in P2.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The set scripting directive failed to set variable/MDO P1. The directive being processed is P2.
System Action:
Processing for the file terminates.
User Action:
Ensure that the variable/MDO names are valid.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The model scripting directive failed to set the variables needed for the next iteration of the loop. The directive being processed is P1.
System Action:
Processing for the file terminates.
User Action:
Ensure that valid variable names are specified and that the prefix is valid.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The model scripting directive failed to access an MDO needed for the next iteration of the loop. The return code is P1, the feedback code is
P2, the MDO component is P3 and the directive being processed is P4.
System Action:
Processing for the file terminates.
User Action:
Ensure that MDO has been correctly mapped, created and referenced.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The stem variable used in a model scripting statement is invalid. The stem must have the .0 variable set to the number of items in the stem. The stem in error is P1 and the directive being processed is P2.
System Action:
Processing for the file terminates.
User Action:
Ensure that the stem is correctly specified and that it has the correct structure for use in a model statement.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
The MDO queued to a model scripting statement is invalid. The MDO must be mapped by $NCL. The queue in error is P1 and the directive being processed is P2.
System Action:
Processing for the file terminates.
User Action:
Ensure that the procedure queueing the data for the model statement is sending an MDO mapped by $NCL.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
Parameters were specified for the P1 scripting statement however this statement does not allow any. The directive being processed is P2.
System Action:
Processing for the file terminates.
User Action:
Remove the parameters for the statement.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
A block scripting directive encountered a block end statement that does not match the currently started block verb. Block style verbs must have their corresponding end statement at the same level as the start statement. The end statement expected is P1 and the end statement encountered is P2. The block scripting directive being processed is P3.
System Action:
Processing for the file terminates.
User Action:
Ensure that start and end statements of block style scripting directives are at the same block nesting level.
Reason:
The Executable Server Page interpreter encountered an error in the source file.
An invalid boolean expression was specified for a conditional verb of a scripting directive. The expression specified is P1 and the error message describing the problem with the condition is P2 and the directive being processed is P3.
System Action:
Processing for the file terminates.
User Action:
Specify a valid boolean expression.
Reason:
The Executable Server Page compiler encountered a fatal error when trying to compile an ESP page.
The reason for the error is P1.
System Action:
Compiling of ESP pages terminates.
User Action:
Determine the reason why the compiler failed, correct the condition, and then action the WEBCENTER parameter group in Customizer.
Reason:
The compiled ESP procedure abended.
System Action:
The page will be delivered as is. Some information may not be displayed.
User Action:
Contact your local support representative.
Reason:
This message follows W3ESP0027, issued as a result of a procedure abending, supplying the error text in P1. The message is followed by other messages adding further details.
System Action:
Refer to message W3ESP0027.
User Action:
Refer to message W3ESP0027.
Reason:
This message follows W3ESP0027 and W3ESP0028 and is issued as a result of a procedure abending, supplying the following specific error details:
LINE= P1 - the line number in the source code
COND= P2 - the error condition
STMT_NAME= P3 - the statement name (verb name)
KEYWORD= P4 - the keyword name (operand name)
NAME= P5 - the name specification
SUBNAME= P6 - the variable name causing the error
VALUE= P7 - the value that caused the error
VALUEOK= P8 - 1 if VALUE= caused the error
VALUE2= P9 - the second value that caused the error
VALUE2OK= P10 - 1 if VALUE2= caused the error
System Action:
Refer to message W3ESP0027.
User Action:
Refer to message W3ESP0027.
Reason:
This message is a performance statistics report message and contains variable information.
System Action:
None.
User Action:
Collect all these messages and send them to the Technical Support representative that requested the report.
Reason:
This message indicates the results of an ESP option request. The option requested is P1 and additional details are P2.
System Action:
None.
User Action:
None.
Reason:
This message presents the lines of help that document the ESPCNTL command syntax used to control ESP options.
System Action:
None.
User Action:
None.
Reason:
This is an Executable Server Page compiler trace message.
System Action:
None.
User Action:
None.
Reason:
The Executable Server Page compiler encountered an error in the source ESP file.
The directive end delimiter was not found. The start of the directive ending process was on line P1 of the ESP source.
System Action:
Processing for the file terminates.
User Action:
Ensure that the directive end delimiter %> is present in the source at the end of the directive specification.
Reason:
The Executable Server Page compiler encountered an error in the source file.
The directive indicator character specified is not recognized. P1 is the line number in the ESP source where the directive started and P2 is the character found.
System Action:
Processing for the file terminates.
User Action:
Specify one of the following directive indicators:
'=' - Equals character for output directives
'@' - At character for processing directives
' ' - blank character for scripting directives
Reason:
The Executable Server Page compiler encountered an error in the source file.
The output directive indicates a function call was requested; however, keyword parameters specified for the function call were in error.
P1 is the line number on which the statement was encountered.
System Action:
Processing for the file terminates.
User Action:
Ensure that you have all the correct keyword spelling and quotes are correctly balanced.
Reason:
The Executable Server Page compiler encountered an error in the source file.
The syntax for the processing directive specified was in error. P1 is the line number on which the error was encountered.
System Action:
Processing for the file terminates.
User Action:
Ensure that you have all the correct keyword spelling and quotes are correctly balanced.
Reason:
The Executable Server Page compiler encountered an error in the source file.
An invalid keyword value was specified for the scripting directive P1 that is located on line number P2. The keyword is P3 and the value in error is P4.
System Action:
Processing for the file terminates.
User Action:
Specify a valid value for the keyword identified.
Reason:
The Executable Server Page compiler encountered an error in the source file.
A directive that has mutually exclusive keywords, of which one is required, did not have the correct keyword specification. The statement was P1 and the statement was on line P2. The mutually exclusive set of keywords are P3.
System Action:
Processing for the file terminates.
User Action:
You must specify one of the keywords listed.
Reason:
The Executable Server Page compiler encountered an error in the source file.
The keyword P1 was specified and it cannot be specified together with any one of the keywords P2. The statement being processed was P3 and it is located on line P4.
System Action:
Processing for the file terminates.
User Action:
Do one of the following:
- Remove keyword P1.
- Do not specify one of the keywords in P2.
Reason:
The Executable Server Page compiler encountered an error in the source file.
An invalid boolean expression was specified for the conditional scripting directive P1 that is located on line P2. The error message for the condition syntax is P3.
System Action:
Processing for the file terminates.
User Action:
Specify a valid boolean expression.
Reason:
The Executable Server Page compiler encountered an error in the source file.
The end of a block style scripting directive was found on line P2 of the source but there is no matching start for the block. The end statement was P1 and the missing start statement is P3.
System Action:
Processing for the file terminates.
User Action:
Specify a matching start statement for the end statement.
Reason:
The Executable Server Page compiler encountered an error in the source file.
The scripting directive statement P2 is not recognized. P1 is the line number in the ESP source where the directive started.
System Action:
Processing for the file terminates.
User Action:
You must specify a valid scripting directive statement.
Reason:
The Executable Server Page compiler encountered an error in the source file.
The scripting directive verb P1 was requested however the keyword parameters specified for the verb were in error. P1 is the verb name and P2 is the line number on which the statement was encountered.
System Action:
Processing for the file terminates.
User Action:
Ensure that you have all the correct keyword spelling and quotes are correctly balanced.
Reason:
The Executable Server Page compiler encountered an error in the source file.
A directive that has mutually exclusive keywords, of which one is required, did not have the correct keyword specification. The verb specified is P1 and it is located on line P2. The mutually exclusive set of keywords are P3.
System Action:
Processing for the file terminates.
User Action:
You MUST specify ONLY one of the keywords listed.
Reason:
The Executable Server Page compiler encountered an error in the source file.
The syntax for verb P1 on line P2 was in error. The keyword P3 was specified and it cannot be specified together with any one of the keywords P4.
System Action:
Processing for the file terminates.
User Action:
Either remove keyword P3 or do not specify one of the keywords in P4.
Reason:
The HTML loader has detected unsupported control statement of type P1 .
System Action:
The statement is ignored.
User Action:
Report the error to your product support representative.
Reason:
The SOLVE WEB FTP Server procedure $W3FTP00 was started but no port number was supplied.
System Action:
The FTP server terminates.
User Action:
Start $W3FTP00 specifying the PORT= parameter with the port number you wish the server to use.
Reason:
The SOLVE WEB FTP Server procedure $W3FTP00 was started but the port number supplied is invalid or out of range.
System Action:
The FTP server terminates.
User Action:
Start $W3FTP00 specifying the PORT= parameter with the port number you wish the server to use. The port number must be an integer from 0 to 65535 inclusive. If PORT=0 is specified, TCP/IP will select a port number and it will be displayed in message W3FT0007 after the server has registered with TCP/IP.
Reason:
The SOLVE WEB FTP Server procedure $W3FTP00 was started but has detected that it is already active.
System Action:
The FTP server terminates.
User Action:
Locate the other instance of the FTP server and use it for your file transfers.
Reason:
The SOLVE FTP Server has issued a SOCKET request but the request has failed. P1 shows the type of request which was issued, and P2 to P5 show the error information.
System Action:
The FTP server terminates.
User Action:
Use the supplied error information to work out why the request failed. This may be indicative of a problem with TCP/IP.
Reason:
The SOLVE FTP Server has received a client connection and has tried to start procedure $W3FTP01 to process the client requests. The attempt to start $W3FTP01 has failed.
System Action:
The client connection is terminated.
User Action:
A message explaining why the procedure didn't start will be in the SOLVE activity log following this message. Use it to determine why the procedure could not be started.
Reason:
The SOLVE FTP Server has received a client connection and has started procedure $W3FTP01 to process the client requests. The attempt to transfer the client connection to $W3FTP01 has failed. The return code and feedback from the SOCKET TRANSFER_REQUEST are shown.
System Action:
The client connection is terminated.
User Action:
Use the return code and feedback to determine why the socket transfer failed.
Reason:
The SOLVE FTP Server has successfully registered with TCP/IP and is now ready to receive client requests on port P1.
System Action:
The FTP server waits for client connections.
User Action:
You may now begin to use FTP.
Reason:
The SOLVE FTP Server has tried to transfer a client connection from the main server process to a subordinate process, but the notification of transfer has not been received.
System Action:
The FTP client connection is terminated.
User Action:
The server allows 30 seconds between the start of the server process and delivery of socket transfer notification - the notification is normally delivered immediately. This problem would indicate a system performance problem which should be investigated.
Reason:
The SOLVE FTP Server has tried to transfer a client connection from the main server process to a subordinate process, but the notification of transfer resulted in an unexpected message being received. The text of the message is shown in P1.
System Action:
The FTP client connection is terminated.
User Action:
The unexpected message should be an error indication - use this message to determine why the transfer failed.
Reason:
The SOLVE FTP Server has received a client connection and has started procedure $W3FTP01 to process the client requests. The attempt to transfer the client connection to $W3FTP01 has failed. The return code and feedback from the SOCKET TRANSFER_ACCEPT are shown.
System Action:
The client connection is terminated.
User Action:
Use the return code and feedback to determine why the socket transfer failed.
Reason:
The SOLVE FTP Server has issued a SOCKET request but the request has failed. P1 shows the type of request which was issued, and P2 to P5 show the error information.
System Action:
The FTP client connection is terminated.
User Action:
Use the supplied error information to work out why the request failed. This may be indicative of a problem with TCP/IP.
Reason:
A WWW SOCKET verb has indicated an error condition. P1 is the verb which failed. P2 , P3 , and P4 indicate the error received. P5 is the vendor-specific error information which further qualifies ERRNO ( p4 ).
P6 and P7 are interpretations of the error codes, indicating the reason for the failure.
System Action:
The WWW Server process is terminated.
User Action:
Use the error information to determine the cause of the error.
Reason:
The Javascript within this web page tried to open a new window but the window failed to open. This is most likely due to security settings within the web browser. The NetMaster web interface requires permission to open unsolicited popup windows in order to function fully.
System Action:
None.
User Action:
Check your web browser's security settings as follows:
For Mozilla:
From the "Edit" menu select "Preferences", and then select "Popup Windows" in the "Privacy & Security" category. Make sure the "Block unrequested popup windows" option is unchecked or click on the "Allowed Sites" button and add this web page's IP address or site name.
Reason:
The web server has detected an internal processing failure. P1 is the error condition detected:
$W3LG20H START FAILED RC=retcode MSG=msg $W3LG20H WRITE FAILED RC=retcode
System Action:
The web server continues processing; however, some applications will not be accessible.
User Action:
Report the error to your product support representative.
Reason:
The web server has detected an internal processing failure. P1 is the error condition detected:
UNABLE TO OBTAIN LOCK, RC=retcode
TRANSFER FAILED: MSG=sysmsg
TRANSFER ACCEPT FAILED: RC=Retcode
MDO ERROR: MDO FDBK=mdofdbk
TIMEOUT ON TRANSFER UNEXPECTED TRANSFER MESSAGE: MSG=sysmsg MDO PACKING ERROR: MDO FDBK=mdofdbk
MDO SIZE ERROR START FAILED: RC=retcode MSG=sysmsg
WRITE FAILED: RC=retcode SETVARS ERROR MSG=sysmsg
LOGIN FAILURE (APPC START) U=userid RC=retcode MSG=sysmsg
System Action:
The web server continues processing.
User Action:
Report the error to your product support representative.
Reason:
The User Name field on the WebCenter login panel was not completed or is invalid. Enter a valid user ID.
System Action:
The login panel appears.
User Action:
Enter a valid user ID and password, and submit the login request again.
Reason:
The Password field on the WebCenter login panel was not completed or is invalid. Enter a valid password.
System Action:
The login panel appears.
User Action:
Enter the correct password for the user ID.
Reason:
The request to log in from WebCenter was rejected by the security exit.
System Action:
The login is rejected and the login panel appears. For more information, see the log.
User Action:
Enter a valid user ID and password, and submit the login request again.
Reason:
The request to log in from WebCenter was rejected by the security exit.
System Action:
The login is rejected and the login panel appears. For more information, see the log.
User Action:
Enter a valid user ID and password, and submit the login request again. Ensure that the SXPARMS member in your hlq.rname.PARMLIB has CHANGEPWD set to YES.
Reason:
The request to log in from WebCenter was rejected because the password is invalid or incorrect.
System Action:
The login is rejected and the login panel appears.
User Action:
Enter the correct password for the user ID and submit the login request again.
Reason:
The request to log in from WebCenter was rejected because the user ID is invalid or unknown.
System Action:
The login is rejected. The login panel appears.
User Action:
Enter a valid user ID and password, and submit the login request again.
Reason:
The web server has detected an internal processing failure. P1 is the error condition detected:
UNABLE TO OBTAIN LOCK, RC=retcode
System Action:
The web server continues processing.
User Action:
Report the error to your product support representative.
Reason:
The OLD PASSWORD field on the Password Change Panel is invalid or was not entered.
System Action:
The Password Change panel appears.
User Action:
Enter the correct old password and the new password.
Reason:
The NEW PASSWORD field on the Password Change Panel is invalid or was not entered.
System Action:
The Password Change panel appears.
User Action:
Enter the correct old password and the new password, and verify passwords.
Reason:
The VERIFY PASSWORD field on the Password Change Panel is invalid or was not entered.
System Action:
The Password Change panel appears.
User Action:
Enter the correct old password and the new password, and verify passwords.
Reason:
The OLD PASSWORD and NEW PASSWORD fields on the Password Change panel have the same value. The new password must be different from the existing (old) password.
System Action:
The Password Change panel appears.
User Action:
Enter the correct old password and the new password, and verify passwords. The New and Verify Password values must be the same.
Reason:
The NEW PASSWORD and VERIFY PASSWORD fields on the Password Change panel are not the same.
System Action:
The Password Change panel appears.
User Action:
Enter the correct old password and the new password, and verify passwords. The New and Verify Password values must be the same.
Reason:
The Password Change function failed. The return code is shown.
System Action:
The Password Change panel appears.
User Action:
Contact your product support organization.
Reason:
The NEW PASSWORD and VERIFY PASSWORD fields on the Password Change panel are not the same.
System Action:
The Password Change panel appears.
User Action:
Enter the correct old password and the new password, and verify passwords. The New and Verify Password values must be the same.
Reason:
The Password Change function failed. The return code is shown.
System Action:
The Password Change panel appears.
User Action:
Contact your product support organization.
Reason:
The procedure $W3MH000:Application_Register has been called to register the Web menus that are in the file P1 for the application
P2 .
System Action:
None.
User Action:
None.
Reason:
The procedure $W3MH000:Application_Register has been called to register the Web menus that are in the file P2 . There was P1 lines of XML in the file.
System Action:
None.
User Action:
None.
Reason:
The procedure $W3MH000:Application_Register has been called to register the Web menus that are in the file P1 but an error occurred reading the file. P2 is the sysmsg returned from $W3DB01U.
System Action:
None.
User Action:
None.
Reason:
The request of type P1 to $W3MH000 failed because the keyword P2 had an invalid value of P3 .
System Action:
None.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
An error occurred while manipulating an NCL VARTABLE in the procedure $W3MH000. P1 is the vartable Identifier, P2 is the function being performed and P3 is the feedback code set by the vartable verb.
System Action:
None.
User Action:
Determine the cause of the error from the return and feedback codes and retry or Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
An error occurred while manipulating an NCL VARTABLE in the procedure $W3MH000. P1 is the vartable Identifier, P2 is the function being performed, P3 is the feedback code set by the vartable verb and P4 is the vartable key being accessed.
System Action:
None.
User Action:
Determine the cause of the error from the return and feedback codes and retry.
Reason:
An unexpected return code of P1 was returned whilst issuing a Lock with a type of P2 . The Lock's Primary Name was P3 and the minor name was
P4 .
System Action:
None.
User Action:
Contact the system administrator. Ensure the installation has been performed as stated in the installation instructions, as the cause of the error may be due to incorrect installation.
Reason:
The Web Menu Manager attempted to call back an application that has registered with the menu manager, but the application returned an error. The application procedure that was called was P1 which in the package P2 . The return code set by the application was P3 .
System Action:
None.
User Action:
Refer to the log for the message that was returned by the application.
Reason:
The Web Menu Manager attempted to call back an application that has registered with the menu manger, but an error was encountered loading the call-back package. The procedure being loaded was P1 which was in the package P2 . The OML error code was P3 . This message is written to the log.
System Action:
None.
User Action:
Determine why the application package is not loading by refering to messages in the log.
Reason:
Whilst the web menu manager was contructing the menu hierarchy it encountered a menu item with the ID P2 in the application P1 that was not found in the list of registered menu items.
System Action:
None.
User Action:
Determine which menu registration file specifies the ID and APP for the menu item that is not found and check that the ID and APP are correct.
Reason:
The Web Server National Language Support javascript generate utility has created/updated P1 javascript files.
System Action:
Generate processing ends normally.
User Action:
None.
Reason:
The Web Server National Language Support path registration utility has added the path P1.
System Action:
Path registration processing ends normally.
User Action:
None.
Reason:
The Web Server National Language Support path deregistration utility has deregistered all previously registered paths.
System Action:
Path deregistration processing ends normally.
User Action:
None.
Reason:
The Web Server National Language Support update utility has updated P1 NLS files.
System Action:
Update processing ends normally.
User Action:
None.
Reason:
The Web Server National Language Support restore utility has restored
P1 NLS files from their respective backups.
System Action:
Restore processing ends normally.
User Action:
None.
Reason:
The Web Server National Language Support delete utility has deleted P1 BAK backup files.
System Action:
Delete processing ends normally.
User Action:
None.
Reason:
The Request Broker procedure encountered an error when attempting an operation on a TCP/IP socket. P1 is the action that was attempted P2 is the port number P3 is the failure reason P4 is the error name P5 is the TCP/IP stack error code
System Action:
The Request Broker terminates.
User Action:
Report the error to your system administrator.
Reason:
This is a trace message generated by the Request Broker procedure when the TRACE keyword parameter is set to YES.
System Action:
None.
User Action:
None.
Reason:
The Request Broker procedure received an invalid request from a remote client. P1 is the name of paramenter P2 is the supplied value
System Action:
The Request Broker sends an error message to the client and continues processing.
User Action:
Report the error to your system administrator.
Reason:
The Request Broker procedure could not start the requested service procedure. P1 is the name of the service P2 is the message generated when the service was started
System Action:
The Request Broker sends an error message to the client and continues processing.
User Action:
Report the error to your system administrator.
Reason:
The Request Broker started the service procedure indicated in a request from a client, but could not then contact the service procedure. P1 is the name of the service procedure
System Action:
The Request Broker sends an error message to the client and continues processing.
User Action:
Review the Activity Log for more detailed error information and report the error to your system administrator.
Reason:
A remote application requested a persistent connection to a Web application, but the requested protocol or character set is not supported on this server. P1 is the protocol or character set that was requested.
System Action:
The request is rejected.
User Action:
Use a version of the remote application that is compatible with the server.
Reason:
A procedure call did not include the required keyword parameter P1.
System Action:
Process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
A procedure call had an invalid Class-Action combination.
System Action:
Process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
A procedure call was made requesting RSS Channel P1 but the channel is not currently registered.
System Action:
Process terminates.
User Action:
This is an internal error. Contact Technical Support.
Reason:
An RSS client issued a get request for RSS channel P1.
These messages are informational and only appear if the &glbl$W3RSLOG global variable is set to Y.
System Action:
Processing continues.
User Action:
None.
Reason:
The web server has detected an internal processing failure. P1 is the error condition detected:
UNABLE TO OBTAIN LOCK, RC=retcode
TRANSFER FAILED: MSG=sysmsg
MDO ERROR: MDO FDBK=mdofdbk
TIMEOUT ON TRANSFER UNEXPECTED TRANSFER MESSAGE: MSG=sysmsg START FAILED: RC=retcode MSG=sysmsg
TRANSFER FAILED: RC=retcode MSG=sysmsg
WRITE FAILED: RC=retcode
SETVARS ERROR MSG=sysmsg
System Action:
The web server continues processing.
User Action:
Report the error to your product support representative.
Reason:
The OLD PASSWORD field on the Password Change Panel is invalid or was not entered.
System Action:
The Password Change panel appears.
User Action:
Enter the correct old password and the new password.
Reason:
The NEW PASSWORD field on the Password Change Panel is invalid or was not entered.
System Action:
The Password Change panel appears.
User Action:
Enter the correct old password and the new password, and verify passwords.
Reason:
The VERIFY PASSWORD field on the Password Change Panel is invalid or was not entered.
System Action:
The Password Change panel appears.
User Action:
Enter the correct old password and the new password, and verify passwords.
Reason:
The OLD PASSWORD and NEW PASSWORD fields on the Password Change panel have the same value. The new password must be different from the existing (old) password.
System Action:
The Password Change panel appears.
User Action:
Enter the correct old password and the new password, and verify passwords. The New and Verify Password values must be the same.
Reason:
The NEW PASSWORD and VERIFY PASSWORD fields on the Password Change panel have different values. These must be the same to ensure that the correct new password is stored.
System Action:
The Password Change panel appears.
User Action:
Enter the correct old password and the new password, and verify passwords. The New and Verify Password values must be the same.
Reason:
The password update failed. The return code from the SECCALL CHANGE operation appears.
System Action:
The Password Change panel appears.
User Action:
Enter the correct old password and the new password, and verify passwords. The New and Verify Password values must be the same.
If this problem persists, contact your product support office.
Reason:
The web server has detected an internal processing failure. P1 is the error condition detected:
TRANSFER FAILED: MSG=sysmsg
MDO ERROR: MDO FDBK=mdofdbk
TIMEOUT ON TRANSFER UNEXPECTED TRANSFER MESSAGE: MSG=sysmsg
System Action:
The web server will continue processing.
User Action:
Report the error to your product support representative.
Reason:
The web server is not configured to process the URL (Uniform Request Locator) as indicated by P1 .
System Action:
HTTP response 404 indicating 'Not Found' is returned to the client.
User Action:
Report the error to your system administrator. Check that the requested URL is correctly formatted and that the requested application has registered for web access.
Reason:
The web server is not configured to process SOAP requests to the URL indicated by P1.
System Action:
HTTP response 404 indicating 'Not Found' is returned to the client.
User Action:
Report the error to your system administrator.
Check that the requested URL is correctly formatted and whether a SOAP request was intended.
Reason:
The web server SOAP handler only supports the HTTP GET and POST methods. The inbound HTTP request specified an invalid method, P1.
System Action:
HTTP response 405 indicating 'Method Not Allowed' is returned to the client.
User Action:
Report the error to your system administrator.
Ensure that the application specifies either the POST or GET HTTP methods.
Reason:
The web server SOAP handler received a SOAP request, which failed to specify the service name. SOAP requests received using HTTP GET must specify the service name in the URL. SOAP requests received using HTTP POST must specify the service name in the inbound SOAP XML based on the service schema.
System Action:
HTTP response 400 indicating 'Bad Request' is returned to the client.
User Action:
Report the error to your system administrator.
Correct the URL for the HTTP GET requests or the inbound SOAP XML.
Reason:
The web server SOAP handler received a SOAP request for the GetMetric service. However, the metric name, P1 , was either invalid or unknown.
System Action:
HTTP response 400 indicating 'Bad Request' is returned to the client.
User Action:
Report the error to your system administrator.
Correct the metric name as specified by the client.
Reason:
The web server SOAP handler received a SOAP request for an unknown service.
System Action:
HTTP response 400 indicating 'Bad Request' is returned to the client.
User Action:
Report the error to your system administrator.
Correct the client to specify a valid service name supported by the SOAP handler.
Reason:
A web server has been started when one is already active. P1 is the process ID of the active server.
System Action:
None.
User Action:
None.
Reason:
The web server has detected an internal processing failure. P1 is the error condition detected:
VARTABLE ERROR ACCESSING KEY key-value
SERVICE PROCEDURE UNDEFINED port application
START FAILED: RC=retcode MSG=sysmsg
TRANSFER FAILED: RC=retcode MSG=sysmsg
PROFILE EDS FAILED: MSG=sysmsg
System Action:
The web server will continue processing. However, some applications will not be accessible.
User Action:
Report the error to your product support representative.
Reason:
A web server request for the named port, P1 ,has failed. P2 is the request failure reason. P3 is the error name. P4 is the TCP/IP stack error code.
System Action:
SOCKET ACCEPT is retried. If it fails again the port is closed and reopened. SOCKET REGISTER is not retried.
User Action:
Report the error to your system administrator. Use the error information to determine the cause of the failure. If necessary use TCPIP STOP followed by TCPIP START to restart TCP/IP commmunications.
Reason:
The web server has been terminated by a command.
System Action:
The web server terminates.
User Action:
None.
Reason:
The web server caches have been reset.
System Action:
The web server cache has been cleared.
User Action:
None.
Reason:
The web server trace option is set to YES or NO.
System Action:
The web server starts or stops tracing activity to the SOLVE log.
User Action:
None.
Reason:
The web server received an unrecognised control command.
System Action:
The command is ignored.
User Action:
Correct the command and resubmit it.
Reason:
The web server received an invalid command string.
System Action:
The command is ignored.
User Action:
Correct the command and resubmit it.
Reason:
WebCenter, procedure $W3SV10Z, has completed initialization and is active.
System Action:
None.
User Action:
You can now access a web-enabled product by entering its URL in your web browser.
Reason:
WebCenter is not active because of P1 , which can indicate one of the following reasons:
The TCP/IP interface has become inactive.
A socket error occurred for the WebCenter interface port.
System Action:
WebCenter waits until the TCP/IP interface becomes active. For a socket error, WebCenter automatically retries to open the interface port.
User Action:
Review the activity log to determine the cause.
To display the log, enter $LOG .
Reason:
The web server has accepted a client connection.
System Action:
The web server waits for the client request.
User Action:
None.
Reason:
The web server has detected an internal processing failure. P1 is the error condition detected:
TRANSFER FAILED: MSG=sysmsg
MDO ERROR: MDO FDBK=mdofdbk
TIMEOUT ON TRANSFER UNEXPECTED TRANSFER MESSAGE: MSG=sysmsg PROFILE EDS FAILED: MSG=sysmsg
SOCKET NOT CLOSED: url
UNDEFINED RETCODE: rc
RECURSION ERROR: URL=url
MDO PACKING ERROR: MDO FDBK=mdofdbk
MDO SIZE ERROR START FAILED: RC=retcode MSG=sysmsg
WRITE FAILED: RC=retcode
System Action:
The web server will continue processing. However, some applications will not be accessible.
User Action:
Report the error to your product support representative.
Reason:
The web server has received an incorrectly formatted HTTP request. P1 is the data received.
System Action:
Processing continues.
User Action:
Report the error to your system administrator. Check that the web browser client is using the HTTP protocol.
Reason:
The web server is not configured to process the URL (Uniform Request Locator) as indicated by P1 .
System Action:
HTTP response 404 indicating 'Not Found' is returned to the client.
User Action:
Report the error to your system administrator. Check that the requested URL is correctly formatted and that the requested application has registered for web access.
Reason:
The web server is not configured to process the URL (Uniform Request Locator) as indicated by P1 .
System Action:
HTTP response 400 indicating 'Invalid Request' is returned to the client.
User Action:
Report the error to your system administrator. Check that the requested URL is correctly formatted. If necessary, contact your product support representative.
Reason:
Access to the URL as indicated by P1 has been denied.
System Action:
HTTP response 403 indicating 'Forbidden' is returned to the client.
User Action:
If access is required, contact your system administrator.
Reason:
The web server has detected an error in processing an authorized HTTP request. The conditions detected:
NO AUTHORIZATION HEADER PRESENT NON-BASIC AUTHORIZATION ATTEMPTED PASSWORD OMITTED
System Action:
HTTP response 401 indicating 'Authorization Required' is returned to the client.
User Action:
Retry your signon using a valid SOLVE userID and password.
Reason:
The web server has received a MODS request that specifies an unsupported type of P1 .
System Action:
HTTP response 404 indicating 'Not Found' is returned to the client.
User Action:
Report the error to your system administrator. Check that the URL is correctly formatted and specifies a supported MODS type of 'HM' or 'MS'.
Reason:
Report output has been deleted for the indicated report run. All report output files and the run subdirectory have been deleted from HFS.
System Action:
None.
User Action:
None.
Reason:
The P2 schedule for the P1 report has been deleted.
Note that this does not delete any report output produced by this schedule. Such report output will expire naturally or may be deleted by a seperate request.
System Action:
None.
User Action:
None.
Reason:
A request was made for a list of report names. The ReportCenter application interface has attempted to list all report definitions from their HFS directory, but this has failed because of the reason, P1 . This is caused most frequently by incorrect or incomplete product installation, region initialization failure, or incorrect HFS file permissions.
System Action:
No NetMaster Reports or Sample Reports functions are available.
User Action:
Contact your system administrator. Additional problem information may appear in the activity log. Use standard OMVS functions to list the attributes of the report definition directory.
This message can be caused by a variety of conditions as follows:
HFS directory error The report definition directory path may not exist or its file system may not be mounted.
Ensure that the OMVS UID of the NetMaster region has at least read access to the report definition directory.
No directory entries The ReportCenter files, including the distributed report definition files, must be correctly installed in HFS.
The exact path name prefixes of the distributed Reporter files must be entered into the REPORTCENTER parameter group in the ReportCenter control region. If necessary, update and reapply the parameter group.
Reason:
The P1 function was attempted but encountered an HFS error.
System Action:
The operation requiring this function cannot be completed.
User Action:
Contact your system administrator. Additional problem information may appear in the activity log. Run the ReportCenter function test for additional information.
In general, these problems are caused by environmental HFS conditions, or incorrect installation or initialization.
Ensure that the HFS file or directory permissions are adequate for the function being attempted.
Ensure that ReportCenter files have been installed correctly in HFS.
Ensure that the distributed and working directory names have been entered correctly into the REPORTCENTER parameter group in the ReportCenter control region. If necessary, update and reapply the group.
Reason:
A request was made for a list of all report runs, but no runs have been completed yet.
System Action:
None.
User Action:
For information about how to schedule a report to be run regularly or how to run a report on demand, see the online help and the ReportCenter Guide.
Reason:
The ReportCenter control region attempted to issue a command to the ReportCenter Java Task, but an unexpected condition or response was encountered.
System Action:
The command is not processed.
User Action:
Retry the operation. If the problem recurs, contact your system administrator.
Additional error detail may be available from:
- NetMaster activity log - ReportCenter Java Task log - ReportCenter function test output
Specific error conditions include:
Unknown Server The name of the data warehouse server is unknown. This indicates an error in region initialization. Ensure that the data warehouse server details in the REPORTCENTER parameter group are correct. If necessary, update and reapply this group.
Connection Error The region could not establish a socket connection with the NetMaster ReportCenter Java Task. This could indicate network or socket errors.
Timeout The ReportCenter Java Task took an excessive amount of time to respond to the command. This could indicate network congestion, or network or socket errors. The Java Task may also have been just started, and has not finished its own initialization.
Unexpected response ID No SHOWHEADER keywords SHOWELEMENT SETVARS error Unknown response keyword These are internal errors. Contact Technical Support.
Reason:
An attempt to retrieve the prompt values for report P1 failed with error
P2 . The prompt criteria file names cannot be extracted from the report definition file.
System Action:
No criteria values can be retrieved. This report cannot be scheduled or run on demand.
User Action:
The ReportCenter application interface could access the report definition file but could not extract any prompt names from it. This may indicate a problem with the report definition file.
Report definition files are distributed as text files named ?reportname.xml, and are installed into the .../nm/reporter/?version/reports/definitions HFS directory.
In general, these files should not be altered after installation. New report definition files must conform to the standard specified in the DTD file, also present in the same directory.
Error conditions include:
Empty XML file This could result from a product installation problem, or manual interference with the file
XML prompt extract problem This could result from incorrect contents of the file
Use standard OMVS functions to examine the file. It should be in text format, and complete according to the DTD. Ensure that the SMP installation of the report definition files completed without error.
Use OCS tracing command REPCALLS and repeat the operation. Contact Technical Support, providibg them the activity log.
Reason:
The ReportCenter control region attempted to issue a command to the Report Service, but an unexpected condition or response was encountered.
System Action:
The command is not processed.
User Action:
Retry the operation. If the problem recurs, contact your database administrator.
Common error conditions are:
Possible database connection error A command to display database or report generator details failed. These commands require a successful JDBC database connection. A common cause of this situation is when the ReportCenter Java Task started task cannot establish a connection with the database, or when there has been a database connection but it has been interrupted.
Do the following:
- Ensure that the DBMS is active
- Restart the ReportCenter Java Task
Database connection failures can be caused by many environmental factors such as security, RRS, JDBC issues, and so on.
Java SQL Exception This indicates that a database connection is active, but a specific database-related command failed with an SQL Exception.
Further details of the exception should be available from the Java Task Log.
Full STDERR text is logged to the .../nm/reporter/usr/adaptor/stderr.txt file and may be accessed with standard IBM OMVS facilities such as OBROWSE.
Additional error detail may be available from:
- ReportCenter Java Task log
- ReportCenter function test output, particularly the Java Framework (JAVAFW) and database (DB) tests
- ReportCenter Java Task STDERR output - Your database log files
Reason:
An attempt to retrieve the definition file for this report failed. Detailed file errors have been written to the NetMaster Activity Log.
System Action:
This report cannot be scheduled or run on demand.
User Action:
The ReportCenter application interface could not access the report definition file for this report.
Report definition files are distributed as text files named ?reportfilename.xml, and are installed into the .../nm/reporter/?version/reports/definitions HFS directory.
Causes of this error include:
File Permissions of the HFS file or directory do not allow this NetMaster region to read the report definition file. This is the most common and likely cause.
Directory is empty. ReportCenter SMP installation did not complete. This directory is an SMP Target Library.
Incorrect directory name. The directory pathname of the ReportCenter distributed code is not correct. Could be caused by region setup errors, SMP maintenance errors, or incorrect manual intervention.
For further information:
- See related messages on the NetMaster Activity Log
- Use standard OMVS functions to list the HFS directory contents
- Use OCS commands REPTEST CODE and REPTEST HFS
Verify that the RACF/ACF2 user id associated with this NetMaster region has READ access to the directory and all files.
Ensure that the SMP installation of the ReportCenter feature completed without error. Ensure that this NetMaster region has been correctly set up by the installation and setup utility.
Ensure that the directory pathnames in the REPORTCENTER parameter group have been correctly entered, and that this group has been successfully actioned.
Reason:
The ReportCenter application interface attempted to read the prompt value file for the specified criteria, but the operation failed. A frequent cause of this problem is insufficient HFS file permissions for the ReportCenter control region.
System Action:
Functions requiring lists of prompt values, such as Run Report on Demand or Add to Schedule, will not work for this report.
User Action:
Review the NetMaster activity log for additional detail of the HFS file errors. Ensure that the file exists at the specified path - file names are case sensitive.
If the file does not exist, the Prompt Generator Service may not have run successfully. Check the ReportCenter Java Task log for any error messages at the time of the last scheduled Prompt Generator timer.
Ensure that UNIX file permissions allow at least read access to the UID associated with the OMVS segment of the NetMaster started task's RACF or ACF2 user ID.
If the file has been deleted, wait until the ReportCenter Java Task Prompt Generator Service runs again and it should be recreated.
Reason:
A mkdir UNIX command was issued to add the directory for a new schedule, but the command failed. A frequent cause of this error is insufficient UNIX file or directory permissions.
System Action:
The report schedule is not added.
User Action:
See the NetMater activity log for details of the HFS error. Ensure that the Report Center region's OMVS UID has write access to the schedules directory.
Reason:
The ReportCenter application interface attempted to read the ReportCenter installation parameters but encountered an error.
The ReportCenter parameter data set member is not accessible. This indicates either a failure in the region setup or subsequent manual interference with the data set. It could also mean that ACF2 or RACF read permissions are set incorrectly for the data set.
One of the following errors was found:
- The PARMLIB data set for this region does not exist.
- The data set exists but does not contain the WRPARMS member.
- The WRPARMS member exists but does not contain the correct parameters.
- Data set security prevented the data set from being read.
The WRPARMS member is used to communicate common Reportcenter parameters that are entered during installation and the subsequent setup of regions that include ReportCenter.
System Action:
The ReportCenter parameters are not available. ReportCenter region initialization may fail.
User Action:
Contact your system administrator. Ensure that:
- The parameter data set exists. It is named dsnpref.rname.PARMLIB, where: dsnpref is the data set prefix used during installation rname is the name of the region
- The WRPARMS member exists.
- Your security system allows NetMaster to read this data set.
- The member contains the following lines:
STC=java-task-name HFS1=hfs-path-prefix
where: java-task-name is the name of the ReportCenter Java Task started task. hfs-path- prefix is the prefix of the directory path that contains the distributed code for ReportCenter.
These values were entered during installation and region setup. Additional error information may appear in the NetMaster activity log.
Reason:
A REPORTRUN command was sent to the ReportCenter Java Task Control Service. The Java Task responded, but the response indicated that the Report service is not available. This occurs when there is no active database connection between the Java Task and the DBMS.
System Action:
The on demand report request was not processed.
User Action:
Ensure that your ReportCenter mainframe SQL database is running, and that a connection has been established between the database and the ReportCenter Java Task.
Database connections will fail under the following conditions:
Due to environmental factors, database connections may not be reestablished immediately. In general, we recommend that you stop and restart the ReportCenter Java Task after every restart of your database system.
(If you are using CA Datacom/AD, be aware that the CA Datacom Server JDBC job must always be active, in addition to the MUF job.)
If the database is active, the Java Task has been restarted, and the problem persists, contact Technical Support. You must have the following documentation available:
Reason:
A REPORTRUN command was sent to the ReportCenter Java Task Control Service, but no response was received.
System Action:
The on demand report request was not processed.
User Action:
Retry the operation. If the problem recurs, contact your system administrator.
Timeout conditions usually indicate network congestion, or errors with the IP stack or socket communications. They can also occur in excessively busy NetMaster regions.
Timeouts may occur if the ReportCenter Java Task is started and has not yet finished its own intialization. In this case, retry the request when the initialization has completed.
See the NetMaster activity log and the ReportCenter Java Task log at the time of the error for any abnormal network conditions.
Reason:
A REPORTRUN command was sent to the ReportCenter Java Task Control Service by using the OML to Java Task interface. This interface returned a response that is not for the calling process.
System Action:
The on demand report request was not processed.
User Action:
Retry the request. Stop and restart the ReportCenter Java Task started task. If the problem recurs, contact Technical Support.
You must have the following documentation available:
- NetMaster Activity log at the time of the failure
- Java Task log at the time of the failure
- ReportCenter Function Test output from the time of the failure (Type REPTEST in OCS)
Reason:
The user, P2 , has confirmed a request to stop the P3 ReportCenter Java Task on the P1 system.
System Action:
The ReportCenter Java Task will terminate.
Termination may be delayed while report scheduler cleanup processing is done and all Java threads are allowed to stop in an orderly way.
Under normal operation, the Java task should run continuously. It should only be restarted when the database has been restarted.
ReportCenter functions will be unavailable until the started task is restarted. No reports can be run, and no data will be added to the database. Subsequent function tests will not be performed or will fail.
User Action:
Ensure that your system operator restarts the NetMaster Java Task as soon as possible.
Reason:
A request to run or schedule this report could not be accepted. There is currently no record of any P1 resources that have had data collected for any of the attributes needed for this report.
System Action:
The requested report will not be run or scheduled.
User Action:
Contact your report administrator.
Ensure that the required resources and attributes are being correctly monitored, and that the data collected by the ReportCenter data regions is being forwarded to the ReportCenter Java Task Data Warehouse Service.
Ensure that you are selecting a time frame for which there is data. Data for a specific report may be available for some time frames but not others, depending on how long you have been collecting data and what your data retention periods are.
Run the DataWarehouseStatus report to get a general idea of the data in your database.
Ensure that the ReportCenter Java Task Prompt Generator Service is running regularly and terminating normally.
Ensure that you are licensed for the product that collects the data.
Reason:
The ReportCenter PARMLIB(WRPARMS) parameter data set member does not contain one or both of the following ReportCenter parameters: - STC - HFS1 You are prompted for these during the ReportCenter installation and region setup processes. This indicates an error in product installation or region setup.
System Action:
ReportCenter functions may work incorrectly or incompletely with unpredictable results.
User Action:
Contact your system administrator.
Verify that the member contains the following lines:
STC=reportcenter-java-task HFS1=hfs-path-prefix
where: reportcenter- is the name of the ReportCenter Java Task java-task started task. hfs-path-prefix is the prefix of the directory path that contains the distributed code for ReportCenter.
Reason:
This message reports the results of a request to start the ReportCenter Java Task. Possible results are:
- The started task is already active. No action was taken.
If you have made initialization parameter changes, the started task must be explicitly stopped and then restarted to pick up these changes. Beware that stopping the task will disrupt any data feeds and report generation.
- The task is not already active - an MVS Start command was issued
- The task is not active and an attempted start command failed. Additional information may be available on the Activity Log.
System Action:
If it is not already active, an attempt will be made to start the Java Framework started task.
User Action:
If a START system command was attempted and failed, contact your systems programmer. Additional details may be available on the Activity Log.
Reason:
A request was made for p1 status information but the ReportCenter Java Task, which provides this information, is not currently active.
The ReportCenter Java Task is set up at NetMaster product installation time. It runs as an MVS started task named P2 on the P3 system.
Under normal operation, the ReportCenter Java Task should run continuously. It should only be restarted when the database has been restarted or database connections have been otherwise interrupted.
System Action:
The command cannot be processed. ReportCenter functions will be unavailable until the started task is started. No reports will be run, no data will be added to the database, and no commands will be processed.
User Action:
Contact your system operator to investigate why the task is not active. Start the ReportCenter Java Task started task on the system where the ReportCenter control region is running.
Reason:
An attempt was made to perform a ReportCenter function remotely, by sending a request over the APPC link to the ReportCenter control region.
An APPC failure has occurred between this local ReportCenter data region and the remote ReportCenter control region. This indicates that the APPC link between the two regions is not defined correctly, not active, or in a status that does not support communications.
System Action:
The requested function cannot be performed.
User Action:
Check that the ReportCenter control region is active. Activate the APPC link between this region and the ReportCenter control region, and retry the operation. Issue the OCS command, SHOW LINKS TYPE=APPC, to see the status of the link. Additional APPC error messages may appear in the activity log.
Reason:
A request was made to run an on-demand report, but the ReportCenter Java Task is not active. The ReportCenter Java Task consists of Java code that runs in the OS/390 (z/OS) UNIX system services environment. It runs as an MVS started task named P2 on the P3 system.
Under normal operation, this task should run continuously.
System Action:
The on demand report cannot be run. ReportCenter functions will be unavailable until the started task is started. No reports will be run, no data will be added to the database, and no commands will be processed.
User Action:
Contact your system operator to investigate why the task is not active. Start the ReportCenter Java Task on the system indicated. Your DBMS that supports the ReportCenter mainframe database must also be running and accepting connections.
After the ReportCenter Java Task is active and has finished its initialization, retry the on- demand report request.
If the report request fails, contact your systems programmer.
Reason:
This message is produced as a result of checking the status of the ReportCenter Java Task (z/OS Started Task name P1).
The message indicates one of the following:
The started task is active, is communicating with this region, and has an active connection to the specified database.
Under normal operation, this started task should run continually. While it is inactive, most ReportCenter functions are unavailable.
The started task did not respond to commands from this region. This can result from a variety of conditions, such as the task may be busy doing database work, or there may be socket problems with the connection.
This message displays memory statistics obtained directly from the z/OS Java Virtual Machine.
Total Memory: The total amount of memory currently available for current and future objects, measured in bytes.
Free memory: An approximation to the total amount of memory currently available for future allocated objects, measure in bytes.
System Action:
If the started task is not active, ReportCenter functions are unavailable until it is started. No reports are run and no data is be added to the database.
User Action:
No action is required. This should be the normal state.
When possible, a reason is provided. Reasons include:
If there is no reason provided, investigate why this started task is not active. Before restarting P1, ensure the requisite database tasks are active. For DB2, this means the DB2 subsystem, and RRS. For CA Datacom, this means the Datacom MUF and Datacom Server.
If this task stops immediately when started, examine the ReportCenter Java Task log file. Under some circumstances, most commonly the unavailability of the database, the ReportCenter Java task terminates.
For other failures, examine the JCL output of the started task.
The started task runs the IBM BPXBATCH facility, which writes output to the stdout and stderr files in the .../nm/reporter/usr/adaptor directory. Examine these files for any error messages.
Common causes of job failure during initial implementation include the following:
If required, update the parameters in the REPORTCENTER Customizer parameter group and if necessary, regenerate the initialization file by actioning this group. Stop and start the task to read the updated initialization file.
Check the activity log and the ReportCenter Java Task log. Use the OCS command REPTEST STC to list extracts from the STDOUT and STDERR files.
Other causes can be region space/workload/timeout problems, IP network problems preventing a socket connection to P1, delays in database processing, or the task may be in the process of shutting down.
This is an informational message only. These figures may be useful to your USS Administration, and tuning and performance groups.
The JVM heap size plays an important role in overall Java application performance. Implementation of Java garbage collection is JVM-specific: see the appropriate IBM mainframe Java documentation for details.
Reason:
You attempted to display the public ReportCenter page, but the report run list for this page could not be retrieved.
System Action:
None. The web page is displayed with an error message.
User Action:
Additional error information will appear before or after this message on the activity log. Rectify the condition and retry the ReportCenter page.
Some common causes of this conditon include:
- The ReportCenter web page has been disabled. This is a web page that requires no NetMaster logon. Some sites disable all access to this page, for security reasons. This is set in the REPORTCENTER parameter group.
- The link between this NetMaster region and the ReportCenter control region is not active.
- The ReportCenter control region is not running.
- HFS file or directory errors prevented retrieval of the report run list. These could include file permission errors, or file system mounting errors.
Reason:
The pathname of the HFS directory that contains the ReportCenter distributed HFS code could not be determined.
This HFS directory pathname is normally set as follows:
- When the ReportCenter feature is selected for installation, the installation utility prompts you to enter the pathname of an HFS directory. This directory is the SMP/E Target Library for ReportCenter's distributed HFS files.
- JCL generated by the installation utility creates this HFS directory, and does an SMP/E APPLY of the ReportCenter code into this directory.
- When the ReportCenter feature is selected for setup in a region, the installation utility writes this directory pathname to the ...PARMLIB(IIAPARMS) parameter dataset that it creates for that region.
- When the region is started, initialization processing reads the parameter dataset, retrieves the HFS pathname value, and makes it available to ReportCenter.
This error condition indicates a failure in ReportCenter installation, region setup, or region initialization.
System Action:
ReportCenter functions will work incorrectly or incompletely with unpredictable results.
User Action:
Do not proceed with any ReportCenter functions until this error is rectified.
Ensure that both ReportCenter feature installation and NetMaster region setup were completed correctly and without errors. Review the region initialization log for any related error details.
Verify that the PDS member contains the following line:
WRHFS1=hfs-path-prefix
where: hfs-path-prefix is the directory pathname that contains the distributed code for the ReportCenter feature.
Reason:
An attempt was made to send a REPORTRUN command to the ReportCenter Java Task Control Service, but a reponse was received from the link manager on this NetMaster region indicating that there was a problem with the IP connection that the command was sent over.
The most common problems are Socket Send and Socket Receive errors. More detailed error messages should be written to the NetMaster log.
System Action:
The on-demand report request was not processed.
User Action:
The causes of some socket failure conditions can be transitory. Retry the operation. If the problem recurs, contact your system administrator.
If no socket connections can be established between this region and the Java Task, ensure that the REPORTCENTER parameter group initialized successfully. Go to option /DWS and verify that the correct IP address and port are being used to communicate with the Java Task.
See the NetMaster activity log and the ReportCenter Java Task log at the time of the error for any abnormal network conditions. Display the current connections and socket allocations.
Reason:
Trace information produced by the ReportCenter application interface is written to the NetMaster activity log as message WRCALL99; HFS file access trace data is written as message UTUSS099. Under normal circumstances, call tracing is not enabled.
To activate ReportCenter application interface call tracing when requested by your support staff, enter the following OCS command:
REPCALLS
This will produce a large number of trace messages to the activity log, and should be left enabled only as long as necessary.
The same REPCALLS command must then be used to turn the tracing off.
System Action:
None.
User Action:
Provide this information to your product support staff, when requested.
Reason:
A data feed destination has has been added with the displayed IP address and port number.
A data feed destination refers to a ReportCenter Java Task. This is the Java component of ReportCenter, which runs as an MVS started task under the z/OS Unix System Services environment.
Data that you select to be sent to ReportCenter is sent from this region to the Java task. The Java task will add the data to your mainframe SQL database.
System Action:
None.
Data can be sent to ReportCenter. This is controlled at a specific resource level by the 'Send to ReportCenter' flag.
In order for a data feed to work correctly, there must be IP connectivity between this region, and the IP address and port specified for the data feed. Any related IP socket or network errors are in the activity log.
User Action:
None.
Reason:
No IP host details are specified.
In order for a data feed to work correctly, there must be IP connectivity between this region, and the IP host and port specified for the data feed. Any related IP socket or network errors are in the activity log.
System Action:
None.
User Action:
To enable the ReportCenter data feed from this region, specify the following values:
To disable the ReportCenter data feed from this region, enter blanks in both the IP Host and Port Number fields.
Reason:
You specified a value for the link blackout start time; however, the value must be numeric and in the range 0 to 59.
The link blackout start time specifies the beginning of a period where data is not sent to the ReportCenter Java Task from the region. Data samples are collected during this period, but remain in the Data Warehouse Server queue.
System Action:
None.
User Action:
Enter a numeric value in the range 0 to 59.
Reason:
You specified a value for the link blackout stop time; however, the value must be numeric and in the range 0 to 59.
The link blackout stop time specifies the end of a period where data is not sent to the ReportCenter Java Task from the region. Data samples collected during the blackout period are sent to the ReportCenter Java Task.
System Action:
None.
User Action:
Enter a numeric value in the range 0 to 59.
Reason:
A blackout period is specified during each hour for the period defined by P1 and P2.
System Action:
During a blackout period, data sampling continues, but all records are stored in the Data Warehouse Server queue. At the end of the blackout period, the queued records are automatically sent to the ReportCenter Java Task. Use the shortcut /DWS to view the Data Warehouse server and scroll right to view the queue.
User Action:
None.
Reason:
This region includes the capability to send data to ReportCenter, but this capability is not activated. All initialization related to ReportCenter is bypassed.
This message appears if the REPORTDATA parameter group is never updated. It is normal in regions that do not produce report data.
System Action:
None. This region is not yet able to send data to ReportCenter.
User Action:
If you want to enable this region to send data to ReportCenter, you must update and action the REPORTDATA parameter group. Ensure that the ReportCenter control region implementation is completed first.
For more information, see the ReportCenter Guide.
If you do not want to enable this region to send data to ReportCenter, no action is required.
Reason:
You have specified a blackout start minute and end minute of equal value. This is not a valid blackout period. The Link Blackout Start Time is the beginning of the blackout during the hour and should be specified as a minute value. The Link Blackout Stop Time is the end of the blackout period and should also be specified as a minute value.
A blackout period allows for the processing load to be spread over the hour. Data sampling continues, but all records are placed in the Data Warehouse Server's queue. At the end of the blackout period, data records are sent to the ReportCenter Java Task.
System Action:
None.
User Action:
Enter a correct value and try again.
Reason:
The port number used by the ReportCenter Java task is not specified.
In order for a data feed to work correctly, there must be IP connectivity between this region, and the IP host and port specified for the data feed. Any related IP socket or network errors are in the activity log.
System Action:
None.
User Action:
To enable the ReportCenter data feed from this region, specify the following values:
To disable the ReportCenter data feed from this region, specify blanks in both the IP Host and Port Number fields.
Reason:
The specified IP host name could not be resolved to an IP address.
The IP host name identifies the LPAR where the ReportCenter Java task is running. You can specify either an IP address for this host or its host name as known by your DNS environment.
If you specify a host name, a socket GetHostByName operation is done to map the host name to its IP address. This operation has failed.
System Action:
None.
User Action:
Specify the correct IP host name of the ReportCenter Java task LPAR:
Alternatively, specify an equivalent IP address.
To identify the host information, you can, in the ReportCenter control region (which runs on the same LPAR as the ReportCenter Java task), use /IPTEST to display region IP configuration details.
Note: There may be different IP addresses that you can use to access the same LPAR, depending on its multiple stack, VIPA, or interface setup.)
Reason:
If either the Start Time or the Stop Time for the Data Feed Link Blackout is specified, then both values must be specified in order to ensure proper validation and correct blackout times.
System Action:
None. The null value is not accepted.
User Action:
Correct the null value by entering a correct value between 0 - 59. Alternately, null values are accepted for both fields, indicating that no link blackout time is declared.
Reason:
A data feed destination has has been added successfully with the IP Address and Port Number specified.
A data feed destination refers to a ReportCenter Java Task. This is the Java component of ReportCenter, which runs as an MVS started task under the z/OS Unix System Services environment.
Data that you select to be sent to ReportCenter will be sent directly from this NetMaster region to the Java task. The Java Task will add the data to your mainframe SQL database.
A ReportCenter control region such as this region can also function as a data feed region. Data feeds to ReportCenter from a control region work exactly as they do from a data region - data is sent over an IP socket connection between this region and the Java Task.
The control region uses the data feed destination IP address and port to set up additional socket connections to the Java Task when it needs to issue commands to the Java Task. Such commands include status queries, requests to run on demand reports, and so on.
In normal operation, there will be these IP connections between this region and the Java task:
- A permanent connection, to send the collected report data over. In between sending data, this connection waits for data.
- Temporary connections are set up for every command issued. After the command response is received, these connections are closed.
- Permanent connections are also set up between the Java Task and all other data feed regions. These do not involve this region.
System Action:
None. Data can now be sent to ReportCenter if required. This is controlled at a specific resource level by the 'Send to ReportCenter' flag.
In order for a data feed to work correctly, there must be IP connectivity between this NetMaster region and the IP address/port specified for the data feed. Any related IP socket or network errors will appear in the NetMaster activity log.
User Action:
None.
Reason:
This is an informational message only.
System Action:
None.
User Action:
If your ReportCenter implementation is in production, ensure that the requisite database and related tasks are active, then start the started task for the ReportCenter Java task.
If you are still in the middle of implementing ReportCenter, leave the started task inactive.
When all external requisite ReportCenter implementation steps are completed, including all JVM installation tasks, database-related tasks and security tasks, and this parameter group has actioned successfully, then start the Java task.
Note: For more implementation information, see the ReportCenter Guide.
Reason:
The ReportCenter Java Task Adaptor.ini file has been updated with the HFS directory pathnames for the Distributed Code, Schedules and Prompts, Log Files and Report HTML Output.
System Action:
HFS File Adaptor.ini has been updated.
User Action:
None.
Reason:
The HFS pathname either does not exist, or can not be accessed by this NetMaster region.
System Action:
None.
User Action:
Correct the pathname.
Ensure that all HFS filesystems required by ReportCenter are allocated and correctly and permanently mounted.
The RACF/ACF2 userid that owns this NetMaster region's started task must have update access to the ReportCenter user directories.
Reason:
The specified zip file cannot be found.
System Action:
None.
User Action:
Correct HFS Path for the DB2 JDBC Classes zip file.
Reason:
ReportCenter supports the following z/OS mainframe SQL Databases:
System Action:
None.
User Action:
Correct the database type.
Reason:
The ReportCenter Java Task Adaptor.ini file has been updated with a start time for housekeeping services, such as the AGGREGATE, SCHEDULER, PROMPTGENERATOR and REPORTEXPIRY services.
System Action:
HFS File Adaptor.ini has been updated.
User Action:
None.
Reason:
This message contains information about the JCL generated to run the ReportCenter Java Task.
The ReportCenter Java Task is the Java component of ReportCenter. It runs as an MVS started task, under the control of z/OS Unix System Services. It communicates with NetMaster regions over IP socket connections.
The RACF/ACF2 user ID associated with this started task must be set up to access OMVS (ie. have an OMVS segment) and must have at least read access to the distributed code directory, and write access to the user directories.
System Action:
None.
User Action:
If required, copy the generated JCL to your MVS proclib dataset. Under normal operation this only needs to be done once when the group is first updated and actioned. This JCL only changes if you change your user directory pathnames.
Reason:
The ReportCenter Java Task Started Task Name field is required. The ReportCenter Java Task is the Java component of ReportCenter. It runs as an MVS started task, under the control of z/OS Unix System Services. It communicates with NetMaster regions over IP socket connections.
System Action:
None.
User Action:
Enter a valid MVS started task name.
When you action this group, the JCL for this started task will be generated and written to the NetMaster activity log, and also placed in an HFS file. Copy this file to your MVS JCL PROCLIB.
Reason:
When ReportCenter is installed, a PARMLIB library for your product region is created with a WRPARMS member. This member must contain a value for STC. This STC value was not found.
System Action:
The Adaptor.ini file is not updated with the ReportCenter Java Task name.
User Action:
Ensure that ReportCenter has been installed correctly.
Reason:
The ReportCenter Java Task Adaptor.ini file has been updated with the Port Number that listens for connections from the NetMaster regions.
System Action:
HFS File Adaptor.ini has been updated.
User Action:
None.
Reason:
The ReportCenter Java task Adaptor.ini file is updated with the JDBC URL, which is used to establish JDBC connectivity.
The DB2 LEGACY driver always uses a constant URL of jdbc:db2os390:
With the DB2 UNIVERSAL driver, the URL format determines whether the Universal driver operates with Type 2 Connectivity or Type 4 Connectivity.
Type 2 Connectivity has a URL similar to the following:
Type 4 Connectivity has a URL similar to the following:
jdbc:db2://?ipaddr:port/?LOCATION (for example, .jdbc:db2://171.202.65.31:5056/D91APTIB)
?LOCATION is the DB2 subsystem location name
?ipaddr:port is the DB2 subsystem IP host address and port
In addition, Type 4 Connectivity requires the DB2 user ID and password to be provided with the connection string.
System Action:
Generated HFS file .../usr.adaptor/Adaptor.ini is updated.
User Action:
None.
For more information about the z/OS DB2 JDBC drivers and their URL requirements, and the differences between Universal Driver Type 2 and Type 4 connectivity, see the IBM DB2 and Java programming documentation.
Reason:
The shell script file Adaptor.bat, which controls initiation of the ReportCenter Java Task has been created successfully.
Use the OMVS facilities OBROWSE or ISHELL to browse this file.
System Action:
The shell script file Adaptor.bat has been created.
User Action:
None.
Reason:
The Adaptor.ini file is updated with the name of the started task that runs the ReportCenter Java task.
System Action:
The Adaptor.ini HFS file is updated.
User Action:
None.
Reason:
The ReportCenter Java Task started task name is not a valid MVS started task name.
System Action:
None. The REPORTCENTER parameter group fails.
User Action:
Enter a valid MVS started task name.
Note than when this started task is started, OMVS processing may result in multiple active tasks with the same or suffixed task names.
Reason:
You have updated the parameters for the ReportCenter Java Task; however, you must restart the STC to activate the changes.
System Action:
None.
User Action:
Stop and restart the ReportCenter Java Task started task.
Reason:
This message contains details of the USS environmental variable values that will be used by the ReportCenter Java Task.
These variables are explicitly set in the generated batch file Adaptor.bat
They override any values inherited from .profile files and so on.
Note that the USS environment of the ReportCenter Java Task may therefore differ from that of the NetMaster region, or any other user.
System Action:
None.
User Action:
None.
Reason:
This region includes ReportCenter, but the required parameters have not been specified. Initialization of ReportCenter is bypassed.
This occurs when this region starts for the first time and the REPORTCENTER parameter group has not been updated.
System Action:
ReportCenter functions are not available from this region.
User Action:
To enable ReportCenter functions in this region, you must update and successfully action the REPORTCENTER parameter group.
In addition to setting up this region as a ReportCenter control region, complete ReportCenter implementation requires additional external tasks such as database setup. Complete all of these tasks before updating and actioning this parameter group.
Note: For detailed information about ReportCenter implementation, see the ReportCenter Guide.
Reason:
The HFS pathname contains an invalid character. Valid characters are: A-Z, a-z, 0-9, and period(.) underscore(_) and dash(-)
System Action:
None.
User Action:
Correct the pathname and retry the operation.
Valid characters for HFS pathnames are:
A-Z, a-z, 0-9, and period(.) underscore(_) and dash(-)
Also, note that before this group can be actioned, the specified directories must have been defined, correctly mounted if required, and be given appropriate UNIX file permissions.
Reason:
An attempted P2 operation on HFS file P3 failed with error condition P1.
HFS file errors may have a variety of environmental causes. A common one is when the HFS file system is not mounted. Other possibilities include:
File permission error.
The NetMaster started task UID does not have the required authority to access the file
File does not exist
The path name may be wrong, or the file may have been deleted
No such device exists.
Not enough space is available.
No space is left on the device, or no space is available to create the IPC member ID.
Not a directory.
HFS encountered a system error.
System Action:
None. The requested operation cannot be performed.
User Action:
Contact your Systems Programmer or UNIX Administrator.
Provide them with the full error details from this message and any related messages. In some cases, there may be additional error details on the NetMaster Activity Log, in messages WRINWI20 or N1AM99.
Ensure that the HFS file system has been defined with sufficient space and is correctly and permanently mounted. Ensure that NetMaster features such as ReportCenter have been installed with the name of a correct and available file system.
File permissions are a frequent cause of HFS file errors.
Verify that the OMVS UID attempting the file operation has sufficient authority to do so. In general, all distributed HFS product files should allow at least read access to all users. Refer to the specific product installation and user manuals for additional file permission requirements for their specific working data.
A complete list of USS HFS return codes is provided in the IBM manual z/OS Unix System Services Messages and Codes, in a chapter titled 'Return Codes (Errnos) Listed by Value'
Additional information about z/OS HFS implementation is available from the IBM Redbook publication Hierarchical File System Usage Guide.
Reason:
This message follows message WRINWI20 and provides details of the return code, reason codes, and messages returned from NetMaster's HFS file interface.
System Action:
The requested HFS file operation cannot be performed.
User Action:
Ensure that the HFS file system has been defined with sufficient space and is correctly and permanently mounted. Ensure that NetMaster features such as ReportCenter have been installed with the name of a correct and available file system.
File permissions are a frequent cause of HFS file errors.
Verify that the OMVS UID attempting the file operation has sufficient authority to do so. In general, all distributed HFS product files should allow at least read access to all users. Refer to the specific product installation and user manuals for additional file permission requirements for their specific working data.
A complete list of HFS reason codes is available in the IBM publication UNIX System Services Messages and Codes for your operating system level.
Additional information about OS/390 and z/OS HFS implementation is available from the IBM Redbook publication Hierarchical File System Usage Guide.
Reason:
This message displays the status of an HFS 'user' directory required by ReportCenter.
If the directory already exists it is reused and the contents retained.
If it does not exist, it is created.
In normal operation, the user directories are created the very first time this parameter group is updated and actioned, and are reused thereafter.
System Action:
None.
User Action:
None.
Reason:
The ReportCenter Home Page provides a quick and easy way for users to look at report output. It links to the report output from all successfully completed report runs.
No user ID, password or logon is required to view reports from the home page.
For convenient access, the ReportCenter Home Page URL can be bookmarked, or linked to from intranet web pages.
System Action:
None.
User Action:
None.
Reason:
The field Public Home Page Access in the REPORTCENTER parameter group is set to NO.
System Action:
Users will not be able to view report output without logging on to the NetMaster region.
User Action:
None.
Reason:
No DB2 load library dataset names were entered. DB2 JDBC requires these names for the STEPLIB environmental variable.
System Action:
None.
User Action:
Enter the dataset names of your DB2 load libraries. For the DB2 Version 7 JDBC Driver Version 2.0, JDBC requires the SDSNEXIT, SDSNLOAD and SDSNLOD2 load libraries.
Refer to the IBM publication, 'DB2 Application Programming Guide and Reference for Java' for your version of DB2 and JDBC driver.
Reason:
The ReportCenter Java task Adaptor.ini file is updated with the name of the JDBC driver, which is used to establish JDBC connectivity.
System Action:
Generated HFS file .../usr/adaptor/Adaptor.ini is updated.
User Action:
None.
Reason:
The pathname entered of the z/OS mainframe Java command directory is not correct.
This directory contains the Java commands. It is created as part of the installation of your z/OS mainframe Java product. Mainframe Java must be installed before you can proceed with ReportCenter implementation.
One of the follow errors was detected:
- The pathname could not be found on this LPAR.
Ensure the pathname is typed correctly. Names are case-sensitive. Ensure the associated HFS filesystem is correctly allocated and mounted, and there are no underlying HFS space or other problems. Ensure that all user IDs have READ access to this directory.
- The pathname refers to a file, not a directory.
The pathname exists on this LPAR but it refers to a file, not a directory. Correct the pathname to refer to the .../bin directory.
You may need to contact your MVS systems programmer and/or USS Unix administrator for help with locating the correct Java directory.
This directory pathname is used in the value of the PATH USS environment variable set for the ReportCenter Java Task.
System Action:
Actioning of the parameter group fails
User Action:
Correct the pathname of the IBM z/OS Java Command Directory. Contact your systems programmer for the correct direactory pathname. This directory was created as part of the installation of your z/OS mainframe Java product.
Reason:
The zip file cadcjava.zip cannot be found.
System Action:
None.
User Action:
Correct HFS Path for the DB2 JDBC Classes zip file.
Reason:
The day specified must be either MON,TUE,WED,THU,FRI,SAT or SUN.
System Action:
None.
User Action:
Ensure that a correct day is specified.
Reason:
The ReportCenter Java Task Adaptor.ini file has been updated with a start day, and time to initiate the Database Expiry Service. This service deletes expired records from the database.
System Action:
HFS File Adaptor.ini has been updated.
User Action:
None.
Reason:
Customization of the Prompts.ini file is in progress. This file is input to the Java Task PROMPTGENERATOR service, which generates the prompt value files. These are displayed in the Criteria section when using the ReportCenter 'Run Report On Demand' or 'Schedule Report' functions.
The file is customized with your database table qualifier name, in the following situations:
- a customized file does not exist
- the database table qualifier name is changed
- a customized file exists, but the skeleton prompt file has been updated since then (usually by an APAR) (The skeleton file is in directory .../nm/reporter/wrNN/cntl
System Action:
A new Prompts.ini file is being generated into directory ?pathname2/nm/reporter/usr/prompts Your database table qualifier is prefixed to all table names in all SQL statements.
User Action:
None.
Reason:
The HFS path name entered for one of the ReportCenter user HFS directories cannot be accessed for the reason stated.
ReportCenter uses the following user HFS directories:
- Runtime control files including generated scripts and JCL, generated prompt files, and user-specified report schedules
- Log files produced by the ReportCenter Java Task
- Report output files including HTML and graphics files
ReportCenter user HFS directories, if they do not already exist, are created when the REPORTCENTER Customizer parameter group is actioned for the first time.
In addition, ReportCenter uses various system HFS directories provided by IBM for Java and JDBC components. ReportCenter Distributed code is created and populated by SMP/E when the product is installed. The directory name is passed to this NetMaster region, which cannot change it.
System Action:
None.
User Action:
Review and correct the HFS directory name.
Most common causes of this error include:
- A non-existent HFS path name has been entered.
- A relative HFS path name has been entered. ReportCenter uses only absolute path names (starting with a /).
- The entered HFS path name exists, but is not a directory name. (A file name is not valid here - it must be a directory name).
- This NetMaster region does not have permission to open the directory. Write access is required for ReportCenter administration.
Ensure that all HFS file systems required by ReportCenter are allocated and correctly and permanently mounted.
Check the HFS file permission settings. The RACF/ACF2 user ID that owns this NetMaster region's started task must have write access to this HFS directory.
For more specific details about HFS directory access errors, see the NetMaster Activity Log.
Reason:
Correct installation of any of IBM's z/OS mainframe Java products creates a number of standard product subdirectories including .../lib .../bin .../include and so on.
These directories are often confused, particularly by users unfamiliar with these products.
Java commands are distributed in Java's .../bin directory. This directory pathname is used in the value of the PATH USS environment variable for the ReportCenter Java Task.
System Action:
None.
User Action:
Correct the IBM z/OS Java JDK Command Directory pathname. If you cannot locate the correct directory, contact your MVS Systems Programmer and/or your USS Administrator.
Reason:
Correct installation of the z/OS DB2 JDBC/SQLJ component creates a number of standard product subdirectories such as .../lib, .../bin, .../classes, and so on.
These directories are often confused, particularly by users unfamiliar with z/OS DB2 JDBC implementation.
DLLs and shared objects are distributed in the DB2 JDBC/SQLJ .../lib directory.
This directory pathname is used in the value of the LIBPATH and LD_LIBRARY_PATH USS environment variables for the ReportCenter Java Task.
System Action:
None.
User Action:
Correct the DB2 JDBC DLL directory pathname.
If you cannot locate the correct directory, contact your DB2 Systems Programmer or Database Administrator.
Reason:
The pathname entered of the z/OS DB2 JDBC DLL directory is not correct.
This directory contains the DB2 JDBC DLLs and shared objects. It is created as part of the installation of the z/OS DB2 JDBC/SQLJ component. This component must be installed before you can proceed with ReportCenter implementation.
One of the follow errors was detected:
- The pathname could not be found on this LPAR.
Ensure the pathname is typed correctly. Names are case-sensitive. Ensure the associated HFS filesystem is correctly allocated and mounted, and there are no underlying HFS space or other problems. Ensure that all user IDs have READ access to this directory.
- The pathname refers to a file, not a directory.
The pathname exists on this LPAR but it refers to a file, not a directory. Correct the pathname to refer to the .../lib directory.
You may need to contact your DB2 systems programmer for help with locating the correct DB2 JDBC DLL directory.
This directory pathname is used in the value of the LIBPATH and LD_LIBRARY_PATH USS environment variables set for the ReportCenter Java Task.
System Action:
Actioning of the parameter group fails.
User Action:
Correct the pathname of the DB2 JDBC DLL Directory.
Reason:
A DB2 JDBC driver type of Legacy was specified; however, the path name of the JDBC class file is not correct.
This file contains the DB2 JDBC Legacy Driver Java classes. It is created as part of the installation of the z/OS DB2 JDBC/SQLJ component. This component must be installed before you can proceed with ReportCenter implementation.
One of the following errors was detected:
db2j2classes.zip (JDBC 2.0, DB2 V7 onwards)
db2sqljclasses.zip (JDBC 1.2)
db2sqljruntime.zip (JDBC 1.2)
db2jdbcclasses.zip (JDBC 1.2)
The path name exists on this LPAR, but it refers to a directory. For the JDBC Legacy Driver, the classes are distributed in a single zip file. You must specify the full path including the file name (for example, /usr/lpp/db2/v7/classes/db2j2classes.zip).
Path name must be absolute (that is, start with /), not relative.
You may need to contact your DB2 systems programmer for help with locating the correct DB2 JDBC Legacy Driver class file.
Note: The DB2 JDBC Legacy Driver is supported only for compatibility with older versions of DB2 for z/OS and z/OS Java.
IBM has the following restrictions on the Legacy Driver:
DB2 Version 9 only works with the Universal JDBC Driver. DB2 Version 7 and 8 work with both the Legacy Driver and the Universal Driver.
For details, see IBM's DB2 for z/OS JDBC documentation.
This file path name is included in the value of the CLASSPATH -cp specification generated for the ReportCenter Java task.
System Action:
Actioning of the REPORTCENTER parameter group fails.
User Action:
Correct the path and file name of the DB2 JDBC Legacy Driver class file.
Reason:
The DB2 JDBC class file name you have entered is for the JDBC 1.2 driver. If you are using DB2 Version 6, this is the only driver available, and you should disregard this message.
If you are using DB2 Version 7 or greater, a JDBC 2.0 driver was also distributed with the DB2 JDBC/SQLJ component. The JDBC 2.0 driver has superior performance characteristics over the older JDBC 1.2 driver, and it is recommended that you use this newer driver where possible.
For the class file names of the JDBC drivers provided with your version of DB2, see IBM's 'Application Programming Guide and Reference for Java' manual.
System Action:
None.
User Action:
Disregard this message if you are running DB2 for z/OS Version 6. If you are running DB2 for z/OS Version 7 or 8, use the JDBC 2.0 driver.
Reason:
The pathname entered of the z/OS DB2 JDBC properties file is incorrect.
This file contains the DB2 JDBC run-time properties to be used by the ReportCenter Java application.
It is created as part of the setup of the z/OS DB2 JDBC/SQLJ component. This component must be implemented before you can proceed with ReportCenter implementation.
Your site may have multiple DB2 JDBC properties files, for different DB2 JDBC applications. The default file is called db2sqljjdbc.properties but this can be changed.
Refer to IBM manual 'DB2 Application Programming Guide and Reference for Java' for information on implementing z/OS DB2 JDBC.
One of the follow errors was detected:
- The pathname could not be found on this LPAR.
Ensure the pathname is typed correctly. Names are case-sensitive. Ensure the associated HFS filesystem is correctly allocated and mounted, and there are no underlying HFS space or other problems. Ensure that all user IDs have READ access to this file.
- The pathname refers to a directory, not a file.
The pathname exists on this LPAR but it refers to a directory.
You may need to contact your DB2 systems programmer for help with locating the correct DB2 JDBC properties file.
This file pathname is used as the value of the DB2SQLJPROPERTIES USS environment variables used by the ReportCenter Java Task.
System Action:
None.
User Action:
Correct the file pathname of the DB2 JDBC properties file.
Reason:
The pathname entered of the CA Datacom JDBC DLL directory is not correct.
This HFS directory contains the CA Datacom Server JDBC DLLs and shared objects. It is created and populated by SMP/E as part of the installation of the NetMaster ReportCenter additional feature.
Note: It is not created by the CA Datacom/AD installation.
The NetMaster ReportCenter feature must be installed before you can proceed with ReportCenter implementation on any NetMaster regions. This feature contains all of ReportCenter's HFS elements.
One of the follow errors was detected:
Ensure the pathname is typed correctly. Names are case-sensitive. Ensure the associated HFS filesystem is correctly allocated and mounted, and there are no underlying HFS space or other problems. Ensure that all user IDs have READ access to this directory.
The pathname exists on this LPAR but it refers to a file, not a directory. Correct the pathname to refer to the .../wr63/datacom directory.
You may need to contact the systems programmer who installed your NetMaster software for help in locating the correct Datacom JDBC DLL directory.
This directory pathname is used in the value of the LIBPATH USS environment variable set for the ReportCenter Java Task.
System Action:
Actioning of the parameter group fails.
User Action:
Correct the pathname of the Datacom JDBC DLL Directory.
Reason:
The pathname entered of the CA Datacom JDBC class file is not correct.
This file contains the CA Datacom Server Java classes. It is created by SMP/E as part of the installation of the NetMaster ReportCenter additional feature.
Note: It is not created by the CA Datacom/AD installation.
The NetMaster ReportCenter feature must be installed before you can proceed with ReportCenter implementation on any NetMaster regions.
One of the follow errors was detected:
Supported file names are:
cadcjava.zip (CA Datacom Server Version 5.0)
Ensure the pathname is typed correctly. Names are case-sensitive. Ensure the associated HFS filesystem is correctly allocated and mounted, and there are no underlying HFS space or other problems. Ensure that all user IDs have READ access to this directory.
The pathname exists on this LPAR but it refers to a directory.
While directories can contain Java classes, in this case the Datacom JDBC classes are distributed as a zip file.
You may need to contact the systems programmer who installed your NetMaster software for help in locating the correct Datacom JDBC class file.
This file pathname is included in the value of the CLASSPATH specification used by the ReportCenter Java Task.
System Action:
None.
User Action:
Correct the pathname of the Datacom JDBC class file.
Reason:
The HFS pathname provided for the ReportCenter distributed code HFS directory cannot be accessed by this NetMaster region. The specific reason is given in P1.
The ReportCenter distributed code HFS directory is an SMP/E Target Library. It is created and populated by SMP/E, when the ReportCenter feature is installed.
The directory pathname is passed to this NetMaster region by the installation utility.
(In addition, ReportCenter uses various system HFS directories provided by IBM for Java and JDBC components.)
System Action:
None.
User Action:
The ReportCenter distributed code HFS pathname cannot be changed from this parameter group. It is passed to this NetMaster region in the PARMLIB dataset created by the install utility.
Contact the systems programmer who installed the product and ask them to review the installation of the ReportCenter feature.
Some causes of this error include:
Ensure that all HFS filesystems required by ReportCenter are correctly and permanently mounted on this LPAR.
Check the HFS file permission settings. The RACF/ACF2 userid that owns this NetMaster region's started task must have Read/Execute access to this HFS directory.
See the NetMaster Activity Log for more specific HFS directory access error details.
Reason:
You specified a value for the link blackout; however, the value must be numeric and in the range 0 to 59.
The blackout start time specifies the beginning of a period where data is not sent to the ReportCenter Java Task from the region. Data samples are collected during this period, but remain in the Data Warehouse Server queue.
System Action:
None.
User Action:
Enter a numeric value in the range 0 to 59.
Reason:
You specified a value for the link blackout stop time; however, it must be numeric and in the range 0 to 59.
The link blackout stop time specifies the end of a period where data is not sent to the ReportCenter Java Task from the region. Data samples collected during the blackout period are sent to the Java Task.
System Action:
None.
User Action:
Enter a numeric value in the range 0 to 59.
Reason:
A blackout period is specified during each hour for the period defined by P1 and P2.
System Action:
During this period, data sampling continues, but all records are stored in the Data Warehouse Server queue. At the end of the blackout period, the queued records are sent automatically to the ReportCenter Java Task. Use the shortcut /DWS to view the Data Warehouse server and scroll right to view the queue.
User Action:
None.
Reason:
You have specified a blackout start minute and end minute of equal value. This is not a valid blackout period. The Link Blackout Start Time is the beginning of the blackout during the hour and should be specified as a minute value. The Link Blackout Stop Time is the end of the blackout period and should also be specified as a minute value.
A blackout period allows for the processing load to be spread over the hour. Data sampling continues but all records are placed in the Data Warehouse Server's queue. At the conclusion of the blackout period, data records are sent to the ReportCenter Java Task.
System Action:
None.
User Action:
Enter a valid blackout period and try again.
Reason:
IBM provides a Universal JDBC Driver for access to DB2 for z/OS, and in some cases also continues to support the older Legacy JDBC Driver.
Universal JDBC Driver for DB2 for z/OS
If you are using DB2 for z/OS Version 9, you must use the Universal Driver. The Legacy Driver is not supported by DB2 Version 9.
The internal name of the Universal Driver is com.ibm.db2.jcc.DB2Driver
It supports two modes:
IBM recommends Universal Driver Type 2 connectivity for greater efficiency when the application is on the same LPAR as the DB2 subsystem. Therefore, ReportCenter uses Type 2 connectivity.
The Legacy JDBC Driver for DB2 for z/OS
If you are using DB2 for z/OS Version 8 or Version 7, you can choose the Universal Driver or the Legacy Driver. Contact your DB2 database administrator to find out which driver is installed.
The internal name of the Legacy Driver is ibm.sql.DB2Driver
The Legacy JDBC Driver has the following IBM compatibility restrictions:
System Action:
Actioning of the parameter group fails.
User Action:
Correct the type of the DB2 JDBC Driver.
Get this value from your DB2 database administrator. They need to ensure that the appropriate type of driver is installed and implemented.
Reason:
A DB2 JDBC driver type of Universal was specified; however, the path name of the JDBC class directory does not end with /classes.
Correct installation of the z/OS DB2 JDBC/SQLJ component creates a number of standard product subdirectories such as .../lib, .../bin, ../classes, and so on. The JDBC driver Java class files are distributed in the DB2 JDBC/SQLJ .../classes directory.
This directory path name is used to generate the -cp (classpath) specification used by the ReportCenter Java task.
Note: The DB2 Universal Driver, unlike earlier drivers, uses more than one class file. All its class files are distributed in the same ../classes directory.
All you need to specify here is the name of the directory; the individual class file names will be automatically generated.
For example, if you specify /usr/lpp/db2/v8/classes, the Adaptor.bat file is generated to include the following files in the -cp specification:
/usr/lpp/db2/v8/classes/db2jcc.jar
/usr/lpp/db2/v8/classes/db2jcc_javax.jar
/usr/lpp/db2/v8/classes/db2jcc_license_cisuz.jar
/usr/lpp/db2/v8/classes/sqlj.zip
System Action:
Actioning of the REPORTCENTER parameter group fails.
User Action:
Specify the path name to the directory that contains the class files for the DB2 JDBC Universal Driver (for example, /usr/lpp/db2/v8/classes).
If you cannot locate the correct directory, contact your DB2 systems programmer or database administrator.
Reason:
A DB2 JDBC Driver type of Universal was specified; however, the path name of the JDBC class directory is not correct.
This directory contains the DB2 JDBC Universal Driver Java class files. It is created as part of the installation of the z/OS DB2 JDBC/SQLJ component, and typically has a minor directory level name of ../classes. This component must be installed before you can proceed with ReportCenter implementation.
One of the following errors was detected:
The path name exists on this LPAR, but it refers to a file. This JDBC driver needs more than one class file. You must specify the directory name only to include all files.
Path name must be absolute (that is, start with /), not relative.
This directory path name is used to generate the -cp (classpath) specification used by the ReportCenter Java task.
Note: The DB2 Universal Driver, unlike earlier drivers, uses more than one class file. All its class files are distributed in the same ../classes directory.
All you need to specify here is the name of the directory; the individual class file names will be automatically generated.
For example, if you specify /usr/lpp/db2/v8/classes, the Adaptor.bat file is generated to include the following files in the -cp specification:
/usr/lpp/db2/v8/classes/db2jcc.jar
/usr/lpp/db2/v8/classes/db2jcc_javax.jar
/usr/lpp/db2/v8/classes/db2jcc_license_cisuz.jar
/usr/lpp/db2/v8/classes/sqlj.zip
System Action:
Actioning of the REPORTCENTER parameter group fails.
User Action:
Specify the path name to the directory that contains the class files for the DB2 JDBC Universal Driver (for example, /usr/lpp/db2/v8/classes). Do not specify an individual file name.
If you cannot locate the correct directory, contact your DB2 systems programmer or database administrator.
Reason:
A DB2 JDBC driver type of Universal was specified; however, the specified JDBC class directory, while it exists, does not contain all of the following required class files:
db2jcc.jar
db2jcc_javax.jar
db2jcc_license_cisuz.jar
sqlj.zip
The JDBC class file directory is created as part of the installation of the z/OS DB2 JDBC/SQLJ component and typically has a minor directory level name of .../classes. This component must be implemented before you can proceed with ReportCenter implementation.
This directory name is used to generate the -cp (classpath) specification used by the ReportCenter Java task.
Note: The DB2 Universal Driver, unlike earlier drivers, uses more than one class file. All its class files are distributed in the same ../classes directory.
All you need to specify here is the name of the directory; the individual class file names will be automatically generated.
For example, if you specify /usr/lpp/db2/v8/classes, the Adaptor.bat file is generated to include the following files in the -cp specification:
/usr/lpp/db2/v8/classes/db2jcc.jar
/usr/lpp/db2/v8/classes/db2jcc_javax.jar
/usr/lpp/db2/v8/classes/db2jcc_license_cisuz.jar
/usr/lpp/db2/v8/classes/sqlj.zip
System Action:
Actioning of the REPORTCENTER parameter group fails.
User Action:
To correct the problem, perform one or more of the following actions:
Check that all four required class files exist in this directory, and grant general read access.
If you cannot locate the correct directory, contact your DB2 systems programmer or database administrator.
For more information, see IBM's DB2 JDBC documentation.
Reason:
One of the following problems was detected:
The default values of Initial=4 and Maximum=256 are adequate for the majority of typical ReportCenter implementations.
z/OS Java storage usage and garbage collection are complex areas, and are very environment-specific. Do not change the default values unless you are clearly experiencing related storage problems, and you have advice from the systems programmers and tuning experts who understand your environment.
System Action:
Actioning of the REPORTCENTER parameter group fails.
User Action:
Correct your heap size specification.
To ensure that you specify correctly, you may want to take further actions:
Reason:
The day specified must be MON, TUE, WED, THU, FRI, SAT, or SUN.
System Action:
Actioning or saving of the ReportCenter parameter group fails.
User Action:
Correct the value in the Weekly Database Expiry Run Day field.
Reason:
If either the Start Time or the Stop Time for the Data Feed Link Blackout is specified, then both values must be specified in order to ensure proper validation and correct blackout times.
System Action:
None. The null value is not accepted.
User Action:
Correct the null value by entering a correct value between 0 - 59. Alternately, null values are accepted for both fields, indicating that no link blackout time is declared.
Reason:
The ReportCenter Java Started Task P1 P3 deliberately shut down at P2 because it encountered an unrecoverable external error condition during processing.
System Action:
ReportCenter functions are unavailable until the error condition that caused the automatic shut down is fixed and the Java Task is restarted.
User Action:
Examine the latest log file messages in the HFS file ../nm/reporter/usr/logs/AdaptorNNN.log for information about the problem. This may include associated SQL error codes or feedback codes from other components.
Many conditions that prevent ReportCenter startup are not serious. They may refer to components other than ReportCenter. Frequent conditions causing deliberate termination include the following:
DB2
CA Datacom/AD
Common
You may need to contact your DB2 DBA or MVS systems programmer for help. When the error condition is fixed, restart the ReportCenter Java Task.
Reason:
The ReportCenter Java Started Task P1 stopped with an orderly shut down. This was in response to an operator JFSTOP OCS command issued at P2.
System Action:
None. Most ReportCenter functions do not work until the task restarts.
User Action:
Restart the task as soon as possible.
Reason:
The ReportCenter Java Task Aggregation service started at P1 with the scheduled daily housekeeping, but did not finish successfully.
Reason: P2
The Aggregation service aggregates all hourly data into daily data. The first run in a calender month also aggregates daily data into monthly data.
The Aggregation service should run once a day, after the scheduled daily housekeeping time. You can set this time in the REPORTCENTER parameter group (/PARMS).
System Action:
The latest daily and monthly data is not available for reporting.
Repeated failures of this service can lead to hourly data expiring and being deleted before it gets aggregated into daily data.
User Action:
Examine the Java Task log at the time of the failure for additional error details.
Database problems are often the cause of Aggregation Service failures, for example:
- Database access, authorization, and permission problems
- Database resource or space shortages
- Database connection problems (including JDBC errors)
The Aggregation Service runs automatically after the next daily housekeeping time.
Reason:
The ReportCenter Java Task Scheduler service started at P1 with the scheduled daily housekeeping, but did not finish successfully.
Reason: P2
The Scheduler service examines all schedules, for every report. If a report is due to be run now, the Scheduler service queues a run request to the Report Generator service.
The Scheduler service should run once a day, after the scheduled daily housekeeping time. You can set this time in the REPORTCENTER parameter group (/PARMS).
System Action:
Reports scheduled for this day are not run.
User Action:
Examine the Java Task log at the time of the failure for additional error details.
The Scheduler service does not access the ReportCenter database. HFS problems can cause Scheduler Service failures. The user ID associated with the ReportCenter Java Task must have write access to the ?prefix/usr/schedules directory and contents. The Scheduler service runs automatically after the next daily housekeeping time. If a report is urgent, run it on demand.
Note: If an individual report scheduled by this service fails to generate, this is not considered a failure of the Scheduler service.
Reason:
The ReportCenter Java Task Prompt Generator service started at P1 with the scheduled daily housekeeping, but did not finish successfully.
Reason: P2
The Prompt Generator service should run once a day, after the scheduled daily housekeeping time. You can set this time in the REPORTCENTER parameter group (/PARMS). It also runs immediately after Java Task initialization. The Prompt Generator service issues a series of SQL Select queries to retrieve the lists of resource names that are used as criteria when you run or schedule a report.
System Action:
Resources that have been added to the database since the last successful Prompt Generator run do not appear in the criteria lists and cannot be selected to be reported on.
User Action:
Examine the Java Task log at the time of the failure for additional error details.
Database problems are often the cause of Prompt Generator failures, for example:
- Database access, authorization, and permission problems
- Database resource or space shortages
- Database connection problems (including JDBC errors) Ensure that the REPORTCENTER parameter group initialized successfully when this control region was last started. This creates the Prompts.ini file, which contains the SQL statements run by this service. The Prompt Generator service runs automatically after the next daily housekeeping time. It also runs when the Java Task starts.
Reason:
The ReportCenter Java Task Timeframe service started at P1 with the scheduled daily housekeeping, but did not finish successfully.
Reason: P2
The Timeframe service should run at midnight every day. It also runs immediately after Java Task initialization. The Timeframe service updates the relative day values in the database timeframe table with today's correct values.
System Action:
Reports are run against incorrect relative days. While the absolute date of a reported fact is always correct, the timeframe is not accurate.
User Action:
Examine the Java Task log at the time of the failure for more information.
Database problems are often the cause of Timeframe service failures, for example:
- Database access, authorization, and permission problems
- Database resource or space shortages
- Database connection problems (including JDBC errors) The Timeframe service runs automatically at midnight and when the Java Task starts.
Reason:
The ReportCenter Java Task Report Expiry service started at P1 with the scheduled weekly housekeeping, but did not finish successfully.
Reason: P2
The Report Expiry service should run once a day, after the scheduled daily housekeeping time. You can set this time in the REPORTCENTER parameter group (/PARMS). The Report Expiry service deletes report output that has expired. Report output is stored as HFS files in the ?prefix/nm/reporter/usr/output HFS directory and this service deletes subdirectories and files from this directory. You control how long report output is kept using the Output Expires After n Days field when you schedule a report.
System Action:
Expired report output is not deleted.
Repeated failures of this service can lead to increased HFS file space usage.
User Action:
Examine the Java Task log at the time of the failure for additional error details.
The Report Expiry service does not access the ReportCenter database. HFS problems can cause Report Expiry Service failures, for example, the user ID associated with the ReportCenter Java Task must have write access to the ?prefix/usr/output directory and contents. The Report Expiry service runs automatically after the next daily housekeeping time.
Reason:
The ReportCenter Java task Expiry Service started at P1 with the scheduled daily housekeeping but did not finish successfully.
Reason: P2
The Expiry Service should run once a week at the scheduled weekly database expiry run day and time. You can set this in the REPORTCENTER parameter group (/PARMS).
The Expiry Service runs a series of SQL DELETE statements to delete expired data from your ReportCenter database.
You control how long you want data to be retained by modifying the Expiry Service data retention rules.
System Action:
Expired database data is not deleted.
Repeated failure of this service can lead to increased database storage usage.
User Action:
Examine the Java task log at the time of the failure for additional error details.
Database problems are often the cause of Expiry Service failures, for example:
The SQL DELETE statements run by this service can delete many rows each, and require supporting DB2 buffer pools and other resources. This is the only service that deletes database data.
The Expiry Service runs automatically after the next weekly database expiry time.
Unwanted database data can be deleted using other methods. For more information, see the ReportCenter Guide.
Reason:
These error messages are produced by a ReportCenter service failure or ReportCenter Java Task deliberate shut down.
System Action:
None.
User Action:
Additional error messages may be available from the Java Task log.
Examine the latest log file messages in the HFS file ../nm/reporter/usr/logs/AdaptorNNN.log. Details may include associated SQL error codes or feedback codes from other components.
Frequent failure conditions include the following:
DB2
CA Datacom/AD
Common
You may need to contact your DB2 DBA or MVS systems programmer for help.
Reason:
The ReportCenter Java Started Task P1 unexpectedly terminated and was unable to record a reason. Possible causes include:
- A CANCEL, PURGE, or FORCE command was issued against the started task from the MVS system console.
- An MVS abend or USS error occurred in a component used by the task.
- An unrecoverable Java exception occurred. Environmental problems such as LE or Java storage shortages can cause this situation.
System Action:
None. Most ReportCenter functions do not work until the task restarts.
User Action:
Restart the task as soon as possible.
If the task was not deliberately cancelled by an operator, investigate why it failed.
Look at the following for diagnostic information:
- The JOBLOG of the started task
- The MVS SYSLOG at the time the task ended
- The latest log file messages in the Java Task Log (HFS file .../nm/reporter/usr/logs/AdaptorNNN.log )
Reason:
The ReportCenter Java Started Task P1 is not active on P2.
The task may have:
System Action:
None. Most ReportCenter functions do not work until the task restarts.
User Action:
Restart the task as soon as possible.
Investigate why this started task was not active.
Before restarting P1 , ensure the requisite database tasks are active. For DB2, this means the DB2 subsystem, and RRS. For CA Datacom, this means the Datacom MUF and Datacom Server.
If this task stops immediately upon starting, examine the
ReportCenter Java Task log file. Under some circumstances, most commonly the unavailability of the database, the ReportCenter Java task terminates.
For other failures, examine the JCL output of the started task.
The started task runs the IBM BPXBATCH facility, which writes output to the stdout and stderr files in the .../nm/reporter/usr/adaptor directory. Examine these files for any error messages.
Use the REPTEST SERV or REPTEST STC commands from OCS.
Common causes of job failure during initial implementation include the following:
If required, update the parameters in the REPORTCENTER Customizer parameter group and if necessary, regenerate the initialization file by actioning this group.
Reason:
A status command was sent to ReportCenter started task P1 on system P2 , but although the task is active, no response was received.
System Action:
If the started task is shutting down, ReportCenter functions are unavailable until it is restarted.
User Action:
Check the activity log and the ReportCenter Java Task log.
Some possible causes of this condition include the following:
- Region space, workload, or timeout problems
- IP network problems interfering with socket connections between this region and the Java Task
- Task performing intensive database processing, causing database delays
- Task is shutting down
Reason:
The diagnostic test for ReportCenter is starting. P2 indicates the ReportCenter status of this region:
Blank value indicates that no ReportCenter activity is currently enabled in this region.
Data Feed Region indicates this region is capable of sending data to ReportCenter.
Dormant Control Region indicates that this region has been set up to function as a ReportCenter control region, but this implementation is not yet completed.
Active Control Region indicates that this region is capable of actively functioning as a ReportCenter control region.
System Action:
Testing of ReportCenter functions commences.
User Action:
None.
Reason:
This region is not currently configured to send data to ReportCenter.
This message is normal in regions where the ReportCenter feature is not implemented.
System Action:
None.
User Action:
None.
If you want this region to be able to send data to ReportCenter if requested, you need to update the REPORTDATA parameter group.
Note: For information about how to implement the ReportCenter feature, see the ReportCenter Guide.
Reason:
This region has been set up to function as a ReportCenter control region, but the ReportCenter implementation is not yet complete.
System Action:
None.
User Action:
None.
Reason:
The ReportCenter Function Test has completed with the total number of warnings and errors indicated. Generally, the following severities are allocated:
Errors affect all or a large number of ReportCenter functions. Do not attempt to use any ReportCenter functions until all error conditions are fixed.
Warnings affect at least one function, but other functions may be unaffected. Warnings should always be investigated.
Notes are informational only, and may not affect any processing.
System Action:
None.
User Action:
If errors or warnings occur, review the detailed messages produced for the specific errors. In some cases, additional information may be written to the NetMaster Activity Log.
Reason:
This message summarizes the locations of any errors detected.
Detailed error information is produced for each test category.
Notes are informational only, and may not affect any processing.
System Action:
None.
User Action:
None.
Reason:
The region configuration testing is started.
System Action:
The following things are tested:
- What products in this region can collect data for ReportCenter?
Note that this does not mean that data is actually being collected, only that it is possible to collect it. ReportCenter data colleciton is controlled at an individual resource level, and must be explicitly started for each required resource.
- Is the IP socket interface active?
- Is there an active HTTP port for WebCenter?
User Action:
None.
Reason:
Testing of the ReportCenter HFS SMP/E Target Library directory has started.
System Action:
The following is checked:
These two files are created when the REPORTCENTER parameter group is updated and actioned.
User Action:
None.
Reason:
This is an informational messages about code.
Information about an individual file may include a PTF/APAR number. This is the number of the latest SMP/E APAR applied to the file. PTF=base means that no SMP/E maintenance is applied.
All code supplied with ReportCenter is maintained with SMP/E. SMP/E code includes the following:
System Action:
None.
User Action:
None.
Reason:
An error occurred while attempting to list an SMP/E Target Library HFS directory.
This directory and its subdirectories are defined during installation, using the HFS direct pathname that you specify.
The most probable causes of this condition include the following:
System Action:
ReportCenter features do not function correctly.
User Action:
Further error information may appear in the activity log. Verify that the named directory exists and that the region user ID and the ReportCenter Java Task user ID have at least read access to it.
Ensure that the ReportCenter feature installation allocation and SMP/E jobs completed correctly, and that all HFS file systems used by ReportCenter are correctly defined and mounted.
Reason:
The HFS SMP/E Target Library directory, P1 has been defined, but contains no files.
The most probable cause of this is failure of SMP/E processing during the installation of ReportCenter.
System Action:
Many ReportCenter functions do not work correctly.
User Action:
Verify that the specified directory contains SMP/E-installed files.
This directory should be defined and populated by SMP/E APPLY processing during the installation of ReportCenter. Contact your systems programmer if installation appears incomplete.
Reason:
This message contains information about one of the Java Task files.
The Adaptor.bat file is generated by the REPORTCENTER parameter group. This file issues the OMVS java command to run the ReportCenter Java Task code. This file is run by the ReportCenter Java Task MVS started task. It sets all USS environmental variables required by JDBC, from the values that you enter in the parameter group.
The Adaptor.ini file is generated by the REPORTCENTER parameter group. This file contains control options and initialization parameters for the ReportCenter Java Task, customized with the values that you enter in the parameter group. It can be browsed using the TSO ISHELL or OBROWSE commands.
System Action:
None.
User Action:
None.
Reason:
File information about the generated P1 file could not be accessed. This file is generated by the REPORTCENTER parameter group in the ReportCenter control region. The file exists but cannot be accessed.
Probable causes of this condition include:
- UNIX file permissions do not give the NetMaster region read access to the file. Since this NetMaster region creates this file, this situation can only result if the file permissions have been manually modified since then.
- The file system is full or not mounted, or other HFS error conditions occurred.
System Action:
If this file is not accessible by the ReportCenter Java Task, then this task will fail. No ReportCenter functions will be available.
User Action:
See the NetMaster activity log for further error messages. Update and action the REPORTCENTER parameter group, and retry the command.
Reason:
The P1 file was not found in the .../nm/reporter/usr/adaptor directory. This file is generated by the REPORTCENTER parameter group.
This message is normal if this region is a dormant control region, i.e., the REPORTCENTER group has never been updated and actioned.
System Action:
The ReportCenter Java Task will fail if started. No ReportCenter functions will be available.
User Action:
Update and action the REPORTCENTER parameter group, and ensure the action is successful, examining the Initialization Log for any error messages. Retry the command.
Reason:
Testing of the JDBC connection between the ReportCenter Java Task and the ReportCenter database has started.
Note that no NetMaster region connects directly to the database. The ReportCenter Java Task started task connects to the database on behalf of the ReportCenter control region and all data regions.
System Action:
The test is started. The following items are checked:
* A database connection must have been established. * Information is requested from the database. The information available depends on the specific DBMS.
User Action:
None.
Reason:
This is a database test informational message.
The data retrieved depends on the database management system (DBMS). Consult the JDBC programming guide for your specific DBMS for details.
System Action:
None.
User Action:
None.
Reason:
A command was sent to the Java Task to display the current database status, but the Report Service did not respond as expected.
The most probable causes of this condition are:
- No current active database connection. The Report Service may have failed to initialize due to database connection failures. This occurs if your DBMS is down, or your JDBC interface is not available. The database connection may have been interrupted due to database or environmental conditions.
- The ReportCenter Java Task is not active.
- The ReportCenter Java Task is still active, but is initializing and cannot accept commands.
- Network conditions are preventing a socket connection from being established between the ReportCenter region and the Java Task.
- The IP port defined for the data warehouse server does not match the port used by the Java Task.
- The data feed destination definition in the NetMaster region is in a hung status.
- The Report Service is busy.
System Action:
None.
User Action:
Do the following:
- For database-related errors, verify that your DBMS is running and can support connections from the ReportCenter Java Task. If your DBMS is not active or not supporting connections, the Report Service will not intialize and database information will not be available.
This condition also occurs if your DBMS has been restarted or the database connection otherwise interrupted. If this has happened, restart the ReportCenter Java Task.
- Ensure that the ReportCenter Java Task is active and has initialized completely.
- Look for error details in the NetMaster activity log.
- Look for error details in the Java Task log.
- Verify that the data feed destination definition in the ReportCenter region is active.
- Verify that the Report Generator Service is active.
Reason:
A command was sent to the Java Task to display the current database status, but the Java Task Report Service did not respond as expected. Previous commands to the Java Task control service have succeeded.
This indicates that the Java Task itself is functioning normally, but the Report Service may have failed during processing or initialization.
System Action:
None.
User Action:
Check the ReportCenter Java Task log for errors that may have led to the failure.
This condition is most commonly caused by database connection failures. Connection failures can happen because:
- The DBMS is not active or not supporting JDBC connections currently.
- The ReportCenter database has not been defined correctly to the DBMS.
- The ReportCenter Java Task does not have the required authority to connect to the database.
Contact your database administrator for further assistance. When all DBMS and database problems are rectified, restart the ReportCenter Java Task.
Reason:
A command was sent to the ReportCenter Java Task to display the current database status. The Report Service responded with DBMS details, but indicated that there is no current active connection.
This indicates that the Report Service initialized normally and connected to the database at initialization, but the connection has subsequently been interrupted. This is commonly caused by the database system itself being stopped.
System Action:
None.
User Action:
This condition is most commonly caused by an active database connection being interrupted. This will happen if the DBMS is stopped while the ReportCenter Java Task is still active.
Contact your database administrator for further assistance. When all DBMS and database problems are rectified, restart the ReportCenter Java Task to re-establish the database connection.
Note: If you are using CA Datacom/AD, this requires the Datacom Server job to be active as well as the Datacom MUF job. If the Datacom Server job is stopped, this condition will result. In this case, restart both the Datacom Server job and the ReportCenter Java Task.
Reason:
The Data Feed Destination testing is started.
A Data Feed Destination controls where report data collected by this region will be sent. The destination is the IP address and port of a ReportCenter Java Task. Report data is sent over a socket connection between this NetMaster regions, and the ReportCenter Java Task.
In normal operation, data feed destinations are defined at region startup, when the REPORTDATA or REPORTCENTER parameter groups are actioned.
Data feed destinations can be browsed using option /DWS.
System Action:
The following things are tested:
- Is the data feed destination defined?
- Is the data feed destination (i.e., IP socket connection) active?
User Action:
None.
Reason:
This is a data feed destination informational message.
System Action:
None.
User Action:
None.
Reason:
An error occured while attempting to retrieve details of the data feed destination in a NetMaster region. This indicates a probable error in region initialization.
P1 is the name of the data feed destination.
P2 is the name of the region.
The data feed destination resides within the ReportCenter Java Task (the Data Warehouse Service). It communicates with NetMaster regions by using TCP/IP socket connections and must be defined to the regions.
System Action:
Several ReportCenter functions will not work:
- No data from this region can be sent to ReportCenter.
- On-demand reports may not be available.
- Status commands to the ReportCenter Java Task may not be available
User Action:
Examine the NetMaster activity log for additional error details.
Verify the IP address and port details in the REPORTCENTER or REPORTDATA parameter group.
Action this parameter group to redefine the data feed, and retry the command.
Use the /DWS option to examine the data feed definitions.
Reason:
The P1 data feed destination is in the P2 status.
Possible causes include:
- The ReportCenter Java Task may not be running.
- A socket or network error has occurred. IP connectivity is required between the NetMaster region, and the ReportCenter Java Task pointed to by the data feed IP address and port.
- The data feed destination definition in this region may have been inactivated manually.
System Action:
No data can be sent to the ReportCenter.
Data will accumulate in the queue until this destination is activated. This is an undesirable situation, as data will be discarded if the maximum queue size is exceeded.
User Action:
Enter the /DWS panel shortcut and activate the data feed definition.
Reason:
Testing has started of this region's access to the ReportCenter distributed and user directories. This step is to ensure that there is sufficient access to perform all ReportCenter administration tasks from this region.
System Action:
The following things are checked:
- Can this region read the distributed report definitions?
- Can this region read the generated report output directory?
- Can this region read the schedule directory?
- Can this region update the schedule directory?
If HFS user security is not requested (HFSSECURITY parameter group), then this region performs these accesses on behalf of all requesting users.
If HFS user security is requested, then the fact that this region is permitted all of these accesses does not imply that they will also work for any specific requesting user. In this case, HFS accesses are done through the ID of each individual user, not through the NetMaster region's user ID.
If you are using HFS user security, you must set the file permissions for the above directories by taking into account the security requirements of each individual user. You should not attempt this unless you have UNIX staff familiar with the concepts and practice of UNIX file security.
User Action:
None.
Reason:
This is an HFS access test informational message.
System Action:
None.
User Action:
None.
Reason:
HFS user security has not been specified. This is the default.
System Action:
All HFS access done by this region will be done under the RACF/ACF2 user ID associated with this NetMaster region.
This region requires access to ReportCenter HFS directories and files in order to perform ReportCenter administration tasks such as scheduling, running, and deleting reports.
User Action:
None.
Reason:
The ReportCenter control region is running with HFS user security enabled. All HFS accesses for ReportCenter files will be done by the user ID of the requesting user and not by the user ID of the NetMaster region.
WARNING! This means that although the subsequent HFS access tests may succeed, this only means that this individual user has the required authorities and will be able to use the ReportCenter web interface. Other users may have different OMVS or file permission setup, and may not be able to do the same functions.
System Action:
All HFS file access requests are issued on behalf of the requesting user. If a specific user does not have correct OMVS segment setup or insufficient file permission levels, their HFS file requests will fail.
User Action:
HFS User Security requires significant analysis of the security requirements of individual users, definition of appropriate OMVS segments for all users, and setting of appropriate permissions for all ReportCenter HFS files and directories.
Do not attempt to use this option without systems programming and UNIX administration support. If you are unfamiliar with the z/OS Unix Systems Services environment and with Unix administration generally, it is recommended to use the default option of region-level security.
Reason:
This message contains information about the ReportCenter report definition directory. It indicates that this user has the required level of access to this directory.
Report definitions are stored in this directory as XML files. They can be browsed with TSO commands ISHELL or OBROWSE.
This NetMaster region reads these file definitions when you use the WebCenter ReportCenter options to run or schedule reports, and also to build the ReportCenter menu bar.
System Action:
None.
User Action:
None.
Reason:
No definitions could be retrieved from the report definition directory. This directory is defined and populated during installation.
Probable causes of this condition include:
- Installation problems: Directory or files may not exist.
- File permission problem when reading directory: If HFS user security is in force, each individual user must have read access to this directory.
- Directory or files have been interfered with manually.
- HFS general storage or mount problems occurred.
System Action:
If HFS user security is disabled (the default), all users will be unable to use the ReportCenter option of WebCenter to run and schedule reports.
If HFS user security is enabled, then depending on the exact error, only this user or all users will be unable to use the ReportCenter functions.
User Action:
See the NetMaster activity log for more error messages. Confirm that the report definition directory exists and contains the distributed report definitions. Change the directory file permissions if required.
Reason:
This message shows the number of reports runs that have output available for viewing.
The number may be zero if no reports have been run, or if all generated reports have expired and been deleted.
To view report output from within WebCenter, click the
List Report Runs tab or the List Runs for All Report Names button. Click the date and time hyperlink of a report in the list. The report opens in a new browser window.
You can also view reports from the public ReportCenter Home Page. This does not require any user ID or logon to NetMaster. Simply bookmark the home page URL, or hyperlink to it from your intranet pages. Use the REPTEST CON command from OCS to list this URL.
System Action:
None.
User Action:
Go to the ReportCenter Home Page URL, and look at the report output.
Reason:
No report runs could be retrieved from the report output directory. This directory is defined by the REPORTCENTER parameter group. Report run details and report output are placed in this directory by the ReportCenter Java Task Report Generator.
Report run details are accessed from WebCenter. Report output is accessed by the NetMaster web server in response to HTTP requests when a user views a report.
Probable causes of this condition include:
- REPORTCENTER parameter group initialization problems: The directory may not have been created correctly.
- File permission problem when reading directory: If HFS user security is in force, individual users must have read access to this directory.
- Manual interference with directory or files.
- HFS general storage or mount problems.
System Action:
Users will be unable to list report runs or browse reports.
User Action:
See the NetMaster activity log for more error messages. Confirm that the P1 report output directory exists. Change the directory file permissions if required.
Reason:
This message contains information about the report schedules directory. It indicates that the user has the required read access to the directory. Report schedule details are stored in this directory. They are added when users schedule reports by using the web interface. They are read by the ReportCenter Java Task Scheduler Service.
The number of schedules may validly be 0 if no reports have been scheduled yet.
System Action:
None.
User Action:
None.
Reason:
No schedules could be retrieved from the report schedules directory. This directory is defined by the REPORTCENTER parameter group. Schedule request details are placed in this directory when a user adds a schedule. Schedule run details are placed in this directory by the ReportCenter Java Task Scheduler Service.
Probable causes of this condition include:
- REPORTCENTER parameter group initialization problems: The directory may not have been created correctly.
- File permission problem when reading directory: If HFS user security is in force, individual users must have read access to this directory.
- Manual interference with directory or files.
- HFS general storage or mount problems.
System Action:
Users will be unable to list report schedules.
User Action:
See the NetMaster activity log for more error messages. Confirm that the P1 report schedule directory exists. Change the directory file permissions if required.
Reason:
A test to add to the report schedules directory was successful.
If HFS Report Center security is in force, all users have the necessary file permissions to schedule reports.
If HFS user security is in force, the requesting user has the necessary file permissions to schedule reports.
Note that this implies the users can also delete schedules.
System Action:
A dummy test schedule is added.
User Action:
None.
Reason:
An attempt to add to the report schedules directory failed.
Probable causes of this condition include:
- File permission problem when updating the directory: If HFS user security is in force, individual users need to have write access to this directory. Otherwise, this region's user ID needs this access.
- REPORTCENTER parameter group initialization problems: The directory may not have been created correctly.
- HFS general storage or mount problems.
System Action:
Users will be unable to schedule reports.
User Action:
See the NetMaster activity log for more error messages. Confirm that the P1 report schedules directory exists. Change the directory file permissions if required.
Reason:
A test to delete a schedule from the report schedules directory was successful.
If HFS Report Center security is in force, all users have the necessary file permissions to delete report schedules.
If HFS user security is in force, the requesting user has the necessary file permissions to delete report schedules.
Note that adding and deleting schedules are both controlled by the write permission.
System Action:
The dummy schedule is deleted.
User Action:
None.
Reason:
An attempt to delete a schedule from the report schedules directory failed.
Probable causes of this condition include:
- File permission problem when updating the directory: If HFS user security is in force, individual users need to have write access to this directory.
- HFS general storage or mount problems
System Action:
Users will be unable to delete report schedules. Schedules that have reached the specified run limit are deleted by the ReportCenter Java Task Scheduler Service.
User Action:
See the NetMaster activity log for more error messages. Confirm that the P1 schedules directory exists. Change the directory file permissions if required - be aware of the different permission requirement if HFS user security is in force.
Reason:
HFS directory pathname testing starts.
System Action:
The following is checked:
User Action:
None.
Reason:
This is a data set and HFS directory informational message.
System Action:
None.
User Action:
None.
Reason:
This message indicates a failure in the region setup or subsequent manual alteration of the parameter data set.
One of the following errors was found:
The IIAPARMS member is used to pass parameters entered during region setup.
System Action:
ReportCenter functions may work incorrectly or incompletely, with unpredictable results.
User Action:
Ensure that the following apply:
dsnpref is the data set prefix used during installation.
rname is the name of the region.
This path name is entered when CA NetMaster is installed.
Additional error information may appear in the activity log.
Reason:
A mandatory HFS directory name is unknown to the ReportCenter region. This occurs if you have not actioned the REPORTCENTER parameter group in a ReportCenter region.
This may also indicate a failure in product installation, region setup, or region initialization.
ReportCenter requires four directories. According to your requirements, they can all share the same prefix, but all four must be specified.
The following directories are required:
This directory is specified and populated by SMP/E when ReportCenter is installed. After installation, this directory must not be changed.
The working data, Java task logs, and HTML report output directories are specified when you activate ReportCenter functions in the ReportCenter region. To do this, update and activate the REPORTCENTER parameter group (shortcut /PARMS). After these directories are specified, they are written to and read from the ReportCenter region and the ReportCenter Java task.
System Action:
None. ReportCenter functions will work incorrectly or incompletely.
User Action:
Update the REPORTCENTER parameter group (shortcut /PARMS) in the ReportCenter region.
Complete the three HFS Pathname fields.
Action the parameter group changes. Ensure that the action completes with no errors. This updates the ReportCenter Java task initialization file with the updated directory names. You must then stop and start the started task for the ReportCenter Java task.
Before updating the parameter group, all HFS directories specified must be defined, mounted, and have UNIX file permissions that grant write access to the following:
If you are using HFS user-level security, individual OMVS users must be granted permissions to the various directories according to your security requirements.
Reason:
Testing of the ReportCenter Java Task has started.
This is an MVS started task, that invokes the ReportCenter Java code. It executes under the control of the USS environment.
This started task communicates with NetMaster regions through IP socket connections.
JCL for this started task is generated when the REPORTCENTER parameter group is actioned. It is written to the NetMaster Activity Log and also an HFS file. It should be copied to your MVS PROCLIB data set.
If the Java Task is not active, no ReportCenter functions will work. Under normal operation, a regular timer will check the task status and raise a NetMaster alert if it is not active or appears hung.
System Action:
The test does the following:
- Checks that the started task is active on this system.
- Checks for any abnormal STDOUT or STDERR output.
- Checks that all required ReportCenter Java Task services are active
- Checks that all defined timers are active
- Lists connection and start time details
- Displays curernt JVM heap storage statistics
User Action:
None.
Reason:
This is a ReportCenter Java Task informational message.
System Action:
None.
User Action:
None.
Reason:
The ReportCenter Java Task named P1 does not appear to be currently running on system P2 . Under normal operation, this task should run continually. It is started with an MVS START command from the MVS system console.
System Action:
ReportCenter functions will be unavailable until the started task is started. No reports can be run, and no data will be added to the database. Subsequent feature tests will not be performed, or will fail.
User Action:
Contact your system operator to start the ReportCenter Java Task immediately. Investigate whether the task may have been running but failed. Examine the JCL output for the started task.
The started task runs the IBM BPXBATCH facility, which writes output to the stdout and stderr files in the .../nm/reporter/usr/adaptor directory. Examine these files for any error messages.
Also examine the latest log file messages, in .../nm/reporter/usr/logs.
Common causes of job failure include:
- Incorrect installation of the mainframe Java product.
- Incorrect setup of the Java Task user ID's RACF/ACF2 OMVS segment.
- Incorrect specification of REPORTCENTER parameters.
- HFS problems with file permissions, space, sharing/mounting, etc. All required file systems must be correctly allocated & mounted.
- System USS/OMVS problems.
Carefully review all parameters in the REPORTCENTER parameter group. In particular, the following parameter values are used to set USS Environment variables, and can cause Java Task failures if incorrect:
- IBM z/OS Java JDK Command Directory (PATH)
- DB2/DATACOM JDBC Class File (CLASSPATH)
- DB2/DATACOM JDBC DLL Directory (LIBPATH)
Regenerate the initialization and batch files by actioning the REPORTCENTER parameter group.
Stop and start the task to read the updated files.
Reason:
This message displays a line of UNIX STDOUT output produced by the ReportCenter Java Task.
STDOUT output is influenced by UNIX environmental factors and may vary between installations. In general, it has no effect on product functions.
The complete STDOUT file is in directory .../nm/reporter/usr/adaptor and can be accessed with TSO OBROWSE, ISHELL, or OMVS commands.
System Action:
None.
User Action:
Usually none, depending on STDOUT content.
If the ReportCenter Java Task is functioning normally, these STDOUT messages can be ignored.
Reason:
The P1 output file produced by the ReportCenter Java Task could not be read. Additional details of the read failure may appear on the activity log.
System Action:
None.
User Action:
If the ReportCenter Java Task is active and working correctly, then this warning can be disregarded.
If the ReportCenter Java Task has never started, then this file will not yet exist. This is normal.
If the ReportCenter Java Task is failing to start or is not performing correctly, then this file may contain details of the error condition which may be essential to problem determination.
Common causes of the NetMaster region being unable to access this file include HFS file permission settings.
You should examine the contents of both the STDERR and STDOUT files using other OMVS facilities such as OBROWSE or the CAT command. For more information, see the IBM UNIX System Services publications.
Provide the file output to Technical Support, if requested.
Reason:
A command was sent to the Java Task to display the current P1 status, but the Java Task did not respond as expected.
The most probable causes of this condition are:
- The ReportCenterJava Task started task is not active.
- The ReportCenter Java Task started task is active, but is still initializing and cannot yet accept commands.
- The ReportCenter Java Task started task is active, but may be in the middle of a lengthy database query.
- Network conditions may be preventing a socket connection from being established between the ReportCenter region and the Java Task.
- The IP port defined for the Data Warehouse Server may not match the port used by the ReportCenter Java Task.
- The Data Feed Destination definition on the NetMaster region may be in a hung status.
- The NetMaster region is processing slowly and the command attempt has timed out.
System Action:
None.
User Action:
Ensure that the ReportCenter Java Task is active and has completely initialized.
Look for further error details in the NetMaster activity log and the Java Task log.
Verify that the Data Feed Destination definition on the ReportCenter region is active.
Reason:
A command was sent to the ReportCenter Java Task to retrieve service details. The task responded that there are no services registered.
System Action:
None.
No ReportCenter features will be available until the problem is rectified and the ReportCenter Java Task is restarted with all services.
User Action:
This indicates either problems with the actual Java Task code or, more likely, a problem with the Java Task initialization file.
The initialization file is generated when the REPORTCENTER /PARMS parameter group is actioned on the ReportCenter region. In general, the file should not need manual modification. The initialization file name is .../reporter/usr/adaptor/Adaptor.ini. You can look at this file using OMVS features such as OBROWSE.
Look at the initialization file and ensure that it contains definitions for all ReportCenter services. A sample template of a complete initialization file is distributed in path .../nm/reporter/wr22/cntl/Adaptor.ini
Regenerate the file by actioning the REPORTCENTER parameter group. Check the NetMaster initialization and activity logs to ensure that the file has been successfully created. Environmental conditions such as file system space problems may contribute to an incomplete file.
Stop and restart the ReportCenter Java Task. If the problem recurs, contact product support and supply the following:
- NetMaster activity log at $WR REPORTCENTER group processing time
- ReportCenter Java Task initialization file - ReportCenter Java Task log file
Reason:
A command was sent to the Java Task to retrieve timer details. The Java Task responded, but no timers were defined. (Timers that fail should still be listed as defined.)
Timers are defined in the ReportCenter Java Task Initialization file. They are placed there by actioning the REPORTCENTER parameter group in the ReportCenter control region, based on the specified 'daily housekeeping time'.
The most probable cause of this condition is an incorrect initialization file.
System Action:
Timer-based services will not be run.
User Action:
Verify that the Adaptor.ini file contains the correct timer definitions. If necessary, regenerate this file by actioning the REPORTCENTER parameter group in the ReportCenter control region, then stop and restart the ReportCenter Java Task.
Reason:
A command was sent to the Java Task to retrieve connection details. The Java Task responded that there are no current connections.
System Action:
None.
User Action:
Use the /DWS menu shortcut to check and if necessary activate the data feed connection between this region and the Java Task.
Data feed connections from other NetMaster regions will, under normal processing conditions, re-establish themselves over time. You can also check these by using the /DWS shortcut on these remote regions.
Reason:
Java Task Service P1 is not active. The service may have failed to initialize, or may have failed during processing.
System Action:
The functions of the specified service are not available.
User Action:
Stop and restart the ReportCenter Java Task. If the service repeatedly fails to initialize or fails during processing, examine the Java Task log for additional error information.
The most likely cause of service failure is database connection problems.
If the DBMS was not active when the ReportCenter Java Task was started, or if the DBMS is stopped while the ReportCenter Java Task is running, the database connection between the two will not be established. Whenever the DBMS is started or restarted, you must also restart the ReportCenter Java Task.
Connection problems can also result from incorrect database security access setup. Ensure that the Java Task started task user ID is granted appropriate authority to the correct database schema.
Note: For more information, see the ReportCenter Guide.
Reason:
The ReportCenter Java Task requires the following services to be defined:
- WAREHOUSE
- TIMEFRAME
- EXPIRE
- AGGREGATE
- SCHEDULER
- PROMPTGENERATOR
- REPORTS
- REPORTEXPIRY
The services must also be active. An inactive service must still appear in the list of services.
Services are defined in the Adaptor.ini initialization file, which is generated by actioning the REPORTCENTER parameter group. Probable causes of this condition are problems with this initialization file. It may be incomplete, incorrectly generated, or have been manually modified.
System Action:
The functions of the missing service(s) are not available.
User Action:
Stop and restart the ReportCenter Java Task. If any services are still missing, ensure that they are present in the Adaptor.ini file. If they are not, regenerate the file.
Examine the ReportCenter Java Task log for further error messages about the missing services.
Ensure that service definitions in the initialization file have not been manually modified.
Reason:
This message displays an error message issued by the ReportCenter Java Task resulting from a failed service, timer pop, or connection.
System Action:
The functions provided by a failed service are not available.
User Action:
Determine why the service, timer, or connection failed. The Java Task log may contain additional error details.
For services that fail as a result of database connection failures, ensure that the DBMS is running and can accept connections. Consult your DBA if database problems persist.
Reason:
A timer was defined in the ReportCenter Java Task initialization file, but a check of all timers shows it to be inactive. This most commonly happens as a consequence of database unavailability or failures.
Timers are added to the initialization file when the REPORTCENTER parameter group is actioned in the ReportCenter control region.
System Action:
The functions of the services started by this timer are not available.
User Action:
See the ReportCenter Java Task log for more error information.
Check the timer manager messages at Java Task initialization time, and see if the timer was ever successfully created. If so, check the service messages at timer pop time to see why the service failed when it ran. A failing service will deactivate its controlling timer.
If the timer was never created, this is probably because the initialization of one or more of its controlled services did not complete.
Services that use the database will not complete initialization if they cannot get a connection to the database. This is the most common cause of timer failures.
After the database is restarted, or whatever was preventing the database connections is fixed, you should stop and restart the ReportCenter Java Task to re-establish the connections.
Note that the Java Task web interface will, for performance reasons, only display the most recent Java Task log records. To access the records from the last initialization, you may need to look at your log files directly. They are written to directory .../nm/reporter/usr/logs and may be accessed using any OMVS features, such as OBROWSE.
Reason:
This message displays a line of the UNIX STDERR output produced by the ReportCenter Java Task. This started task runs the BPXBATCH utility, which executes a batch file that invokes the ReportCenter Java application by using the OMVS Java command. STDERR output results from a failure in executing the batch file.
Some STDERR information, such as the java version, is produced deliberately by ReportCenter for informational purposes.
Unexpected STDERR output usually indicates that the Java Task has failed to start, and displays reasons for the failure. An exception is when the STDERR file is used to report JDK version information.
Probable causes of this condition include the following:
System Action:
The ReportCenter Java Task may have failed - no ReportCenter functions will be available.
User Action:
Review the error messages. Consult the IBM UNIX System Services publications, if required.
Ensure that the Adaptor.bat and Adaptor.ini files have been correctly generated into the .../nm/reporter/usr/adaptor directory and that they reflect the values entered into the REPORTCENTER parameter group in the ReportCenter control region.
If necessary, correct and action this group, then stop and restart the task.
Ensure that the .../nm/reporter/wr22/classes directory contains the distributed .jar files. These should have been placed there by the SMP installation job generated by the Install Utility. The started task user ID must have READ access to these.
Verify that the JDK and the DB2 JDBC software have been installed correctly. Verify that the environment variables, particularly PATH, which control the task's USS environment have been properly set up.
Reason:
The ReportCenter Java Task is currently active.
The ReportCenter Java Task is an application that provides a common infrastructure for application-specific services.
ReportCenter includes a number of services that are dedicated to tasks such as generating reports and adding report data to the database.
System Action:
None.
User Action:
Under normal operation, the ReportCenter Java Task should run continuously. It does not need to be stopped just because the NetMaster region is stopped - they will re-establish connection when the region restarts. Only stop the ReportCenter Java Task if you need to close all database connections, or if the database is unavailable.
Reason:
This message displays details about a current connection to the ReportCenter Java Task.
Only the ReportCenter control region connects to send commands.
ReportCenter data regions connect to send performance data to the Data Warehouse server, which adds it to the database. The ReportCenter control region can also be a data region, although it need not be.
Regions that can connect to the Java Task are defined as valid clients in the initialization file, and can be displayed using the WebCenter Java Task Status Authorized Clients tab.
System Action:
None.
User Action:
If a region is connected to send data, then you can define resources and attributes to be monitored for reporting.
Note: For information about how to collect report data, see the ReportCenter Guide.
Reason:
This message displays memory statistics from the Java Virtual Machine.
Total Memory: the total amount of memory currently available for current and future objects, measured in bytes.
Free memory: an approximation to the total amount of memory currently available for future allocated objects, measured in bytes.
System Action:
None.
User Action:
This information may be of interest to your USS administration and/or tuning and performance groups.
The JVM heap size plays an important role in overall Java application performance. Implementation of Java garbage collection is JVM-specific: see the appropriate IBM mainframe Java documentation for details.
Reason:
This message indicates the products present in this NetMaster region which are capable of sending their collected performance data to ReportCenter.
Note: Just the presence of such a ReportCenter-enabled product does not, on its own, mean that any data is actually being sent to ReportCenter.
Sending data is controlled on an individual resource basis, using the Send to ReportCenter? field. This is set by updating performance monitoring using the UM command against a resource in the IP Resource Monitor (/IPMON).
You should only send to ReportCenter data for the resources you explicitly want to report on. Sending unnecessary data will cause extra network traffic, waste database space, and possibly impact database response times.
System Action:
None.
User Action:
None.
Reason:
CA NetMaster File Transfer Management and CA NetMaster Network Management for TCP/IP provide data and support for ReportCenter. To use ReportCenter, you must have at least one of these products enabled in this region.
System Action:
None.
User Action:
For information about installing and implementing ReportCenter, see the following publications:
Reason:
Testing is commencing of this NetMaster region's OMVS access.
This test verifies that the user ID associated with this region is correctly set up to access OMVS.
This requires an OMVS segment to be set up for the region's RACF/ACF2 user ID. This is done by your RACF/ACF2 Security Administrator.
System Action:
The test is started.
User Action:
None.
Reason:
This is an OMVS informational message.
System Action:
None.
User Action:
None.
Reason:
An error occurred attempting to retrieve UNIX System Services environmental information for the NetMaster region. P1 is the error condition returned from the HFS interface.
System Action:
None. ReportCenter functions may work incorrectly or incompletely. This region may be unable to access ReportCenter HFS pathnames.
User Action:
Examine the NetMaster activity log for additional messages associated with this error. Message UTUSS011 provides more detail.
Some likely causes of this error include:
- The user ID associated with this NetMaster region does not have an OMVS segment defined in its RACF/ACF2/Top Secret security profile.
- One of the objects in this user ID's OMVS segment is incorrect. For example, the specified home directory may not exist or may be defined with inappropriate file permissions.
- General problems with the UNIX System Services environment on this system. Use the TSO OMVS command to see if OMVS is available.
Reason:
Testing commences of the last known status logged by each ReportCenter scheduled service.
At startup and completion, each service writes the time and date to an HFS file in the ?prefix/nm/reporter/usr/logs directory, called ?SERVICENAME.log This file contains the most recent status logged by the service.
System Action:
The test starts.
User Action:
None.
Reason:
The P1 service started by a timer completed successfully at the date and time shown.
If available, the length of time that the service took to complete its processing is also shown.
Example:
PROMPTGENERATOR OK 2006-09-02 03:00:00-03:06:49 (duration 00.06.49)
Indicates that the PROMPTGENERATOR service was started by its timer at 2006-09-02 03:00:00, completed successfully at 03:06:49, actively processed for a total of 6 minutes and 49 seconds.
System Action:
None. The service is waiting to run when its timer expires.
User Action:
None.
Reason:
The most recent status in the service status log for service P1 is P2 .
System Action:
None.
User Action:
None.
Reason:
The last run status for this service cannot be obtained. This is always the case when the ReportCenter Java Task is newly-installed and the service has not run for the first time.
In other cases, problems reading the service status log HFS files can cause this error. The region must have at least read access to this directory and all required file systems must be mounted.
System Action:
None.
User Action:
Run REPTEST HFS to check HFS availability and file permissions.
Reason:
This message contains informations about what URLs can be used to access ReportCenter live and example report output.
Copy a URL and paste it into your browser address bar.
You may want to bookmark these URLs, or link to them from intranet pages
System Action:
None.
User Action:
None.
Reason:
NetView Emulation is defining command verb P1 to the command characteristics definition table (CCDEF).
System Action:
Processing continues.
User Action:
None.
Reason:
A member name must be specified.
System Action:
The command is not processed.
User Action:
Specify a member name.
Reason:
Command was entered with an invalid operand - null string.
System Action:
The command is not processed.
User Action:
Correct the operand and try the command again.
Reason:
The maximum number of data streams defined exceeded the Pipe stage limit. P1 specifies the stream direction, which can be input or output.
System Action:
The command is not processed.
User Action:
Define the correct amount of streams for the Pipe stage.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
The number of input data streams defined was less than required by the Pipe stage command.
System Action:
The command is not processed.
User Action:
Specify a valid number of input data streams to the Pipe stage command.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
A label has been used in a Pipe stage that is not defined. P1 specifies the label name.
System Action:
The command is not processed.
User Action:
Define the label and retry the Pipe command.
Reason:
A label has been defined that has already been defined within the Pipe command.
System Action:
The command is not processed.
User Action:
Correct the label usage within the Pipe stage command.
Reason:
A deadlock condition has occurred between two or more stages.
P1 is the pipeline name.
P2 is the reason.
System Action:
The command is not processed.
User Action:
Correct the label usage in the pipe stage command.
Reason:
The keyword specified in P1 is a conversion order or output order. You must specify an input order before using a conversion order or output order.
System Action:
The command is not processed.
User Action:
Correct the Pipe Stage Edit script by specifying an input edit order earlier in the script.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
An input order has been used to start an edit phrase. The keyword was specified after an input order and is a global or input order. An output order must be used to end the phrase after a global or input order is specified. P1 specifies the keyword in error.
System Action:
The command is not processed.
User Action:
Specify an output order to end the edit phrase or a global order prior to the input order to correct the phrase.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
Netview NCCF-like console was activated.
P1 is the PFKey terminating the session.
System Action:
None.
User Action:
None.
Reason:
Netview NCCF-like console was terminated.
System Action:
None.
User Action:
None.
Reason:
NetView NCCF-like console was not started. P1 is the reason:
NEST An attempt to start NCCF was made from a nested OCS session.
FEATURE An attempt to start NCCF in a region without either REXX or REXX NetView support.
LOCK An attempt to start NCCF in the OCS window while a lock for it is already held (other session may be diconnected).
P2 provides the lock identifier consisting of the following information:
NCCFL2 text User ID Terminal name Window number
NTRM An attempt to start NCCF in the region whilst a previous copy of NCCF has not completed termination.
P2 provides process identifier (NCLID) and the time the lock was obtained.
System Action:
None.
User Action:
For NTRM, use NCLID to purge stalled NCCF session or try later. If the NTRM problem persists, contact Technical Support.
Reason:
Emulated NetView command was not executed. P1 is the reason:
FEATURE - an attempt to execute an emulated NetView command on the region without either REXX or REXX NetView support.
System Action:
None.
User Action:
None.
Reason:
NetMaster NetView emulation NM command specifies an invalid procedure name.
The requested procedure name P1 name is longer than eight characters or it contains invalid characters.
System Action:
The command is not processed.
User Action:
Specify a valid procedure name.
Reason:
NetMaster NetView emulation NM command specifies a procedure name that does not exist in the procedure library.
System Action:
The command is not processed.
User Action:
Correct the procedure name. If the procedure name is correct, ensure that it exists in the procedure library specified for use by this user ID. To do this, use the SHOW EXEC command or the LIST command to display the procedure without execution.
Reason:
NetMaster NetView emulation NM command operand is prefixed by NV. The NM command is already in the NetView emulation environment.
System Action:
The command is not processed.
User Action:
Remove the NV prefix to execute a CA NetMaster command or procedure.
If you are executing a NetView REXX procedure from:
Reason:
The SUBMIT command attempted to submit a DSIPARM member when no DSIPARM DD exists with allocated data sets.
System Action:
Submit command is not processed.
User Action:
Allocate a partitioned data set with DDname DSIPARM, and populate this with members that must be submitted. Alternatively, the SUBMIT command can be executed passing a data set from which to submit the required batch job. SUBMIT dataset_name where dataset_name can be sequential or a partitioned data set specified with a member.
Reason:
Days (ddd) was specified with the AFTER command. This is not currently supported. Please use the interval as the first command argument: - 11 (two digit value = minutes) - :11 (two digits preceded by a colon - seconds) - 1 (one digit value = hours - 1:1:1 (h:m:s) - 11:11:11 (hh:mm:ss)
System Action:
NCCF AFTER command is not processed.
User Action:
Retry the NCCF AFTER command without using (ddd) days.
Reason:
SAVE was specified with the AFTER command. This is not currently supported.
System Action:
AFTER command is not processed.
User Action:
Retry the NCCF AFTER command without using SAVE.
Reason:
TIMEFMSG was specified with the AFTER command. This is not currently fully supported. TIMEFMSG is always set to NO.
System Action:
The AFTER command is processed with TIMEFMSG=NO.
User Action:
None.
Reason:
GMT was specified with the AFTER command. This is not currently supported.
System Action:
The AFTER command is not processed.
User Action:
Retry the NCCF AFTER command without using GMT.
Reason:
Days (ddd) and/or date were specified in the AT command. This is not currently supported. Please use the time as the first parameter: - 11:11:11 (hh:mm:ss)
System Action:
AT command is not processed.
User Action:
Retry the NCCF AT command using time(hh.mm.ss).
Reason:
SAVE was specified with the AT command. This is not currently supported.
System Action:
AT command is not processed.
User Action:
Retry the NCCF AT command without using SAVE.
Reason:
TIMEFMSG was specified with the AT command. This is not currently fully supported. TIMEFMSG is always set to NO.
System Action:
AT command is processed with TIMEFMSG=NO.
User Action:
None.
Reason:
GMT was specified with the AT command. This is not currently supported.
System Action:
AT command is not processed.
User Action:
Retry the NCCF AT command without using GMT.
Reason:
Days (ddd) was specified with the EVERY command. This is not currently supported. Please use the interval as the first command argument:
- 11 (two digit value = minutes)
- :11 (two digits preceded by a colon - seconds)
- 1 (one digit value = hours
- 1:1:1 (h:m:s)
- 11:11:11 (hh:mm:ss)
System Action:
EVERY command is not processed.
User Action:
Retry the NCCF EVERY command without using (ddd) days.
Reason:
SAVE was specified with the EVERY command. This is not currently supported.
System Action:
EVERY command is not processed.
User Action:
Retry the NCCF EVERY command without using SAVE.
Reason:
TIMEFMSG was specified with the EVERY command. This is not currently fully supported. TIMEFMSG is always set to NO.
System Action:
EVERY command is processed with TIMEFMSG=NO.
User Action:
None.
Reason:
GMT was specified with the EVERY command. This is not currently supported.
System Action:
EVERY command is not processed.
User Action:
Retry the NCCF EVERY command without using GMT.
Reason:
A VTAM P1 command was submitted but no response was received. Check the activity log for messages relating to the VTAM command and the VTAM Node being actioned.
System Action:
None.
User Action:
This condition may occur when attempting to perform a VARY command against a Node that does not exist. Check that you specified the correct Node in your command.
Reason:
NetMaster NetView emulation does not support keyword argument(s) P1 for allocation of an existing data set. The arguments have been ignored.
System Action:
The command continues processing.
User Action:
None.
Reason:
NCCF CALC emulation failed to obtain an exclusive lock identified by P1.
System Action:
CALC command is not processed.
User Action:
From an OCS window, issue a "SH LOCK PNAME=NCCFP* command and capture the output. Contact Technical Support with the diagnostic data provided.
Reason:
NCCF CALC emulation failed to free an exclusive lock identified by P1.
System Action:
CALC command processing fails.
User Action:
From an OCS window, issue a "SH LOCK PNAME=NCCFP*" command and capture the output. Contact Technical Support with the diagnostic data provided.
Reason:
The ID parameter was specified with an invalid value. The ID parameter must be a numeric value that is the NCLID of an NCL process.
System Action:
GO command terminates.
User Action:
Correct the parameter and run the command.
Reason:
Invalid operands were used with the NetMaster emulation of the NCCF LIST command. Valid operands are:
- TIMER=ALL OP=ALL (display all timers).
- TIMER=ALL (display all of this users timers).
- TIMER=tid (display a specified timer).
- STATUS=OPS (display all logged on users).
- CLIST=member (display a specified member).
- DSILOG (display log information).
System Action:
LIST command is not processed.
User Action:
Retry the NCCF LIST command with supported operand(s).
Reason:
Invalid value specified with OP= operand. NetMaster emulation of the NCCF OP operand only supports the value ALL.
System Action:
LIST command is not processed.
User Action:
Retry the NCCF LIST command with OP=ALL.
Reason:
Invalid operands were used with the NetMaster emulation of the NCCF PURGE command. Valid operand is: - TIMER
System Action:
PURGE command is not processed.
User Action:
Retry the NCCF PURGE command with supported operand(s).
Reason:
Invalid operands were used with the emulation of the NCCF RMTCMD command.
Supported operands are:
System Action:
RMTCMD command is not processed.
User Action:
Retry the NCCF RMTCMD command with supported operands.
Reason:
An emulated NCCF Close command has been entered. Enter either of the following: - Go YES to continue with Close command processing. - Go NO to terminate Close command processing.
System Action:
If Go YES is specified Close command processing continues and the region indicated by P2 is shut down. If Go NO is specified Close command processing terminates.
User Action:
Specify either Go YES or Go NO .
Reason:
Go YES was not entered to a Close command confirmation request.
System Action:
Close command processing terminates.
User Action:
None.
Reason:
NetView command/pipe stages usage statisctics file was saved.
P1 is the Data Set name of the file.
System Action:
None.
User Action:
None.
Reason:
NetView command/pipe usage statisctics program was called with an invalid argument.
P1 is the argument detected. Supported arguments are: - Command table names, see XNCMPK101. - SORT= sort argument specification.
System Action:
None.
User Action:
Correct the argument specification.
Reason:
NetView command/pipe usage statisctics program was called with an unsupported table name.
P1 is the table name symbolic name. Supported tables specification (minimum 3 characters) are:
CMD - NetView Emulation commands.
PIP - NetView Emulation Pipe Stages.
STA - NetView Emulation Pipe Stages.
System Action:
None.
User Action:
Correct the table name specification.
Reason:
NetView command/pipe usage statisctics program was called with an unsupported/invalid sort key.
P1 is the sort key value specified. Supported sort keys (4-6 characters as shown suffice) are:
- ALIAS - Show Commands/Stages aliases first.
- FAIL - Command/Stage failure count.
- FAILED - Command/Stage failure count.
- FLCNT - Command/Stage failure count.
- NAME - Command/Stage name (default).
- PROC - Command/Stage supporting procedure name.
- SUPP - Show supported Commands/Stages first.
- USAGE - Command/Stage usage count.
- USCNT - Command/Stage usage count.
System Action:
None.
User Action:
Correct the sort key specification.
Reason:
NetView command/pipe usage statistics program failed to access the Commands/Stages vartable.
P1 is the vartable name. Normally, it indicates that NetView emulation has not yet started.
System Action:
None.
User Action:
Correct the sort key specification.
Reason:
NetView command/pipe usage statisctics program failed executing internal function.
P1 is the internal function failing.
P2 is the error/feedback.
System Action:
None.
User Action:
None.
Reason:
NetView command/pipe usage statistics program failed to allocate the output data set.
P1 is the message received on alllocation.
System Action:
None.
User Action:
None.
Reason:
NetView command/pipe usage statistics program failed to open the output data set.
P1 is RC received.
P2 is the feedback received.
System Action:
None.
User Action:
None.
Reason:
NetView command/pipe usage statistics program failed to write to the output data set.
P1 is RC received.
P2 is the feedback received.
System Action:
None.
User Action:
None.
Reason:
NetView command/pipe usage statistics program failed to close the output data set.
P1 is RC received.
P2 is the feedback received.
System Action:
None.
User Action:
None.
Reason:
NetView command/pipe usage statistics program failed to free the output data set.
P1 is RC received.
P2 is the feedback received.
System Action:
None.
User Action:
None.
Reason:
In-storage NetView command emulation table has been rebuilt. All the counters were reset to 0 and flags to defaults.
System Action:
None.
User Action:
None.
Reason:
In-storage NetView emulation table builder was called with invalid parameter.
P1 is the parameter.
System Action:
None.
User Action:
None.
Reason:
NetView emulation command table builder failed to add the command table alias command entry.
P1 - Feedback
P2 - Key
System Action:
None.
User Action:
None.
Reason:
NetView emulation command table builder failed to add the command table primary command entry.
P1 - Feedback
P2 - Key
System Action:
None.
User Action:
None.
Reason:
The DD name is incorrect. P1 specifies the DD name in error.
System Action:
The command is not processed.
User Action:
Use a previously defined DD name. See the ALLOCATE command online help for information about defining a DD name.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
An ALLOCATE or FREE command has completed successfully.
P1 specifies the DD Name.
P2 specifies whether the file has been allocated or unallocated.
System Action:
None.
User Action:
None.
Reason:
The member specified in P1 was not found.
System Action:
The command is not processed.
User Action:
Ensure the member specified was correct or review the member to help determine the cause of the problem.
Reason:
The data set containing the JCL for submission contains an invalid statement.
System Action:
The command is not processed.
User Action:
Correct the JCL statement.
Reason:
The data set specified in P1 could not be found.
System Action:
The command is not processed.
User Action:
Specify a valid data set name.
Reason:
The data set specified in P1 could not be allocated because it is already allocated to another job.
System Action:
The command is not processed.
User Action:
Determine why the data set is allocated and either wait for the data set to become available or use another data set.
Reason:
The SUBMIT command ended successfully.
P1 specifies the job name.
P2 specifies the job ID.
System Action:
The SUBMIT command ends.
User Action:
None.
Reason:
A value has been specified twice where only one is expected.
System Action:
The command is not processed.
User Action:
Correct the command syntax.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
This multi line message lists information about the allocated data set, including:
- Message ID
- Message header information
- The DD Name of the file
- The name of the data set
- The member name
- The status of the file:
NEW
OLD
MOD
SHR
- The disposition of the file:
SYSOUT
KEEP
DELETE
System Action:
None.
User Action:
None.
Reason:
The Pipe stage command has been passed values larger than can be processed:
P1 specifies the value.
P2 specifies the limit.
System Action:
The command is not processed.
User Action:
Ensure the data length does not exceed the limit specified in P2 .
Reason:
The numeric value of P1 is ouside of the range specified by P2 and P3 .
System Action:
The command is not processed.
User Action:
Ensure the numeric value is in the specified values.
Reason:
The DELAY command can specify seconds only when the second argument (command text) is omitted.
System Action:
The command is not processed.
User Action:
Specify the time delay period in seconds only.
Reason:
The VIEW command was issued to display panel P1 but it is not in the allocated NVPANELS dataset.
System Action:
The command is not processed.
User Action:
Ensure that the panel P1 exists in one of the datasets allocated to the NVPANELS DD.
Reason:
The panel definition is invalid. It does not contain valid panel lines.
System Action:
The panel is not displayed.
User Action:
Correct the panel and retry.
Reason:
The syntax for the VIEW command is:
VIEW name1 name2 INPUT|NOINPUT MSG|NOMSG
where: name1 Specifies the internal name used by NetView. It is specified here for compatability.
name2 Specifies the name of the panel to display.
INPUT Specifies that input values and AID information may be returned to the procedure that invokes the VIEW command. INPUT also specifies that cursor location may be received from and returned to the procedure that invokes the VIEW command.
NOINPUT Specifies that the VIEW command does not return any information to the procedure that invoked it. If the panel defines a command line, all input is treated as a command. This is the default.
MSG|NOMSG This option has no effect and is supported for compatability only.
System Action:
The command is not processed.
User Action:
Correct the syntax and retry.
Reason:
Specifies that the calculator is active and also provides an ID. The ID displays the NCL ID of the process that is providing the CALC command function. If there is more than one NCCF CALC environment running, you will need to specify ID= with the GO command. For example, you may need to issue GO ID=1234 1 * 2
System Action:
Processing continues.
User Action:
None.
Reason:
Specifies that the calculator is running in decimal mode.
System Action:
Processing continues.
User Action:
Enter GO followed by a decimal calculation.
Reason:
Specifies the calculator is running in hexadecimal mode.
System Action:
Processing continues.
User Action:
Enter GO followed by a hexadecimal calculation.
Reason:
Specifies the system time and date.
P1 specifies the time.
P2 specifies the date.
System Action:
The actual date and time is displayed.
User Action:
None.
Reason:
The panel definition is invalid. It contains too many options or the required text indicator line cannot be found.
System Action:
The panel is not displayed.
User Action:
Correct the panel and retry.
Reason:
The command could not be processed because an error occurred or a time out expired.
P1 specifies the name of the REXX procedure.
P2 specifies the name of the command.
P3 specifies the timeout value in seconds.
P4 specifies the associated message text.
System Action:
The command is not processed.
User Action:
Review the REXX procedure to determine the cause of the error.
Reason:
An invalid value was specified in a command keyword.
P1 specifies the invalid value.
P2 specifies the keyword.
P3 specifies the command.
System Action:
The command is not processed.
User Action:
Correct the value specified in P1.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
An invalid MVS command was specified. P1 specifies the command.
System Action:
The command is not processed.
User Action:
Specify a valid MVS command.
Reason:
Specifies that the calculator is ending.
System Action:
Calculator processing ends.
User Action:
None.
Reason:
Displays the result of a decimal calculation.
System Action:
Calculator results are displayed.
User Action:
None.
Reason:
The specified calculation is invalid.
System Action:
The command is not processed.
User Action:
Specify a valid calculation.
Reason:
The values specified in the calculation are too large to be processed by the calculator.
System Action:
Calculation is not processed.
User Action:
Specify smaller values in the calculation.
Reason:
Displays a hexadecimal calculation.
System Action:
Calculator results are displayed.
User Action:
None.
Reason:
The argument is not numeric.
System Action:
The command is not processed.
User Action:
Specify the numeric value.
Reason:
The panel named P1 is not in the NVPANELS dataset concatenation.
System Action:
None.
User Action:
Ensure that you have entered the correct panel name and that the panel exists in a dataset allocated to the NVPANELS DD.
Reason:
Data entered on the command line is not recognized as a valid command or the name of a REXX procedure.
System Action:
The command is not processed.
User Action:
Correct the command and retry.
Reason:
The VIEW command attempted to display a panel named P1 ;however, the panel contained a definition error and cannot be displayed.
System Action:
The panel is not displayed.
User Action:
Check the log for the specific message text that relates to the error.
Reason:
You pressed F8 on a panel that does not have a continuation panel.
System Action:
None.
User Action:
None.
Reason:
You pressed F7 (Backward) on the first panel of a sequence.
System Action:
None.
User Action:
None.
Reason:
NetMaster Netview Command emulation procedure was called to perform command P1 which is not supported yet.
System Action:
None.
User Action:
None.
Reason:
REXX NetView emulation detected that the positional argument P1 is invalid.
P2 may indicate one of the reasons listed above or provide another explanation.
Action - action specified is invalid to the command emulated.
List - list variable invalid, missing ending bracket.
Label - command labels are not supported yet.
Length - text variable(name) is longer than allowed for its type:
- max 8 characters for procedure name.
- max 12 characters for global variable name.
- max 12 characters for vartable name.
- max 256 characters for variable name.
- other argument-specific length limitations.
Text - invalid text variable.
Txtype - text variable(name) contains characters invalid for its type.
System Action:
None.
User Action:
Verify the syntax and correct arguments.
Reason:
NetMaster NetView emulation detected errors while decoding argument.
P1 is the message detailing errors encountered.
System Action:
None.
User Action:
Verify the syntax and correct the arguments.
Reason:
NetMaster NetView emulation detected that the value of the keyword argument specified is invalid.
P1 - keyword value in error.
P2 - describes the reason (see XNEM001 for explanations).
System Action:
None.
User Action:
Verify the syntax and correct the arguments.
Reason:
NetMaster NetView emulation detected that the positional argument P1 is not supported at the current emulation level.
System Action:
None.
User Action:
None.
Reason:
NetMaster NetView emulation detected that the keyword argument P1 is not supported at the current emulation level.
System Action:
None.
User Action:
None.
Reason:
NetMaster NetView emulation detected that the number of arguments specified is less than required.
System Action:
None.
User Action:
Verify the syntax and add required arguments.
Reason:
NetMaster NetView emulation detected that the required positional argument was not specified.
P1 is the name of the missing keyword argument.
System Action:
None.
User Action:
Verify the syntax and add required arguments.
Reason:
NetMaster NetView emulation detected that the required keyword argument was not specified.
P1 is the name of the missing keyword argument.
System Action:
None.
User Action:
Verify the syntax and add the required arguments.
Reason:
NetMaster NetView emulation detected that the co-requisite positional argument was not specified.
P1 is the name of the missing argument.
System Action:
None.
User Action:
Verify the syntax and add the required arguments.
Reason:
NetMaster NetView emulation detected that the co-requisite keyword argument was not specified. P1 is the name of the missing argument.
System Action:
None.
User Action:
Verify the syntax and add the required arguments.
Reason:
NetMaster NetView emulation detected that the co-requisite keyword argument value is not specified or the specification is shorter than expected.
P1 is the keyword name.
System Action:
None.
User Action:
Verify the syntax and specify the required values.
Reason:
NetMaster NetView emulation detected that the text provided as REXX variable name is not a valid REXX variable name.
P1 is the variable name.
System Action:
None.
User Action:
Verify the syntax and correct the arguments specification.
Reason:
NetMaster NetView emulation detected the conflict in positional arguments.
P1 is the first argument.
P2 is the second argument.
System Action:
None.
User Action:
Verify the syntax and correct the arguments specification.
Reason:
REXX NetMaster emulation detected the conflict in keyword arguments.
P1 is the first argument.
P2 is the second argument.
System Action:
None.
User Action:
Verify the syntax and correct the arguments specification.
Reason:
NetMaster NetView emulation detected that the keyword argument specified was excessive for the action selected.
P1 is the name of the argument.
System Action:
None.
User Action:
Verify the syntax and correct the arguments specification.
Reason:
NetMaster NetView emulation detected that the specified argument values are incompatible with their meaning, or two arguments specified are not compatible with each other.
P1 is the first or only argument.
P2 is the second argument.
System Action:
None.
User Action:
Verify the syntax and correct the arguments specification.
Reason:
NetMaster procedure P1 called by REXX program failed compilation stage.
P2 - Error code indicated by the language compiler.
System Action:
None.
User Action:
If the procedure is in-house, run a direct compile, analyze errors, and fix the code. It the procedure is a part of NetMaster distribution, contact Technical Support with diagnostic data provided.
Reason:
This is a continuation of message XNEM041 providing further details:
P1 - Error text.
System Action:
None.
User Action:
See message XNEM041.
Reason:
This is a continuation of the XNEM041 message, providing further details:
P1 Name of the file or member that contains the failing procedure
P2 Source line number in the file
P3 Failing statement name
P4 If present, failing keyword name
System Action:
None.
User Action:
See the XNEM041 message.
Reason:
NetMaster NetView Command helper procedure detected that it was called with the empty command line specified.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
NetMaster NetView Command helper was called to process the command but the originating environment is either not specified or not supported.
P1 is the environment name, if specified.
System Action:
None.
User Action:
Ensure that the command is issued in the correct environment. Supported environments are: NCCF, REXX, PIPE and RCMD.
Reason:
NetMaster Netview Command helper procedure detected that command
P1 was marked as 'Not Supported'.
System Action:
None.
User Action:
None,
Reason:
NetMaster Netview Command helper did not find emulation definition or REXX procedure for P1 command.
System Action:
None.
User Action:
None.
Reason:
NetMaster Netview Command helper failed to load handler procedure P2 supporting command P1 .
P3 is the OML compiler error code.
System Action:
None.
User Action:
None.
Reason:
NetMaster NetView nccf-like full screen command entry facility was cancelled by the user. If the command buffer was already created/updated in the previous command editing session, it is preserved without changes.
System Action:
None.
User Action:
None.
Reason:
NetMaster NetView Command helper encountered internal error processing command P1 .
P2 is the internal function failing.
P3 is the error/feedback. This situation indicates problems encountered calling internal functions of the Product.
System Action:
None.
User Action:
Try again, contact Technical Support if the problem persists.
Reason:
NetMaster Netview Command helper reports that the emulated command executed. The message is intended to be only sent while in intcmd environment.
P1 is the executed command.
P2 is the &SYS.RETCODE value.
P3 is the internal return code.
System Action:
None.
User Action:
None.
Reason:
This trace record is written to the activity log when the NetView emulation #DEBUG option is activated.
Command P1 is rerouted to a remote region through the INMC link P2. The response timeout is P3.
System Action:
None.
User Action:
None.
Reason:
This trace record is written to the activity log when the NetView emulation #DEBUG option is activated.
P2 is the first message in the response to a rerouted NetView emulation command.
System Action:
None.
User Action:
None.
Reason:
This trace record is written to the activity log when the NetView emulation #DEBUG option is activated.
This trace message is issued when the remote command terminates.
P2 is the reason for the termination.
System Action:
None.
User Action:
None.
Reason:
The specified NetView emulation command P1 can execute in the local environment only and cannot be rerouted to a remote region.
System Action:
None.
User Action:
Verify the syntax and correct the command specification.
Reason:
The label P2 on the NetView emulation command P1 has an invalid value.
System Action:
None.
User Action:
Verify the syntax and correct the command specification.
Reason:
A NetView Emulation command is being rerouted to a remote region. The NetView Emulation command string contains character P1 in position P2 in the command string. This character is used as a control character when rerouting a NetView Emulation command and cannot be used in the command string.
System Action:
The NetView Emulation command is not sent to the remote system.
User Action:
Remove (or replace) the escape characters from the command string.
Reason:
A NetView Emulation command is being rerouted to a remote region. The NetView Emulation command string has a length of P1 bytes. The NetView Emulation supports a maximum of P2 bytes.
System Action:
The NetView Emulation command is not sent to the remote system.
User Action:
Review the command string and shorten it if possible. Alternatively, copy the NetView Emulation command to a REXX procedure on the remote system and then request its execution from the local system.
Reason:
A message was sent to the user specified in P1 .
System Action:
None.
User Action:
None.
Reason:
An invalid command was entered.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
The destination was not specified in the MSG command.
System Action:
The command is not processed.
User Action:
Specify a destination in the MSG command.
Reason:
Command text was invalid or omitted from a command.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
The destination specified in P1 is not active or not available.
System Action:
The command is not processed.
User Action:
Specify a valid destination.
Reason:
Invalid operand data was specified.
System Action:
The command is not processed.
User Action:
Correct the operand data specified with the command.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
An invalid operand was specified.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
The GO command was issued, however, no processes were in a PAUSE or WAIT status.
System Action:
The command is not processed.
User Action:
When you issue the GO command, ensure that you correctly identify the NCL process, which must have a status of PAUSE or WAIT.
Reason:
A CLOSE command has been issued and accepted.
System Action:
Shutdown of the NetMaster region is initiated.
User Action:
None.
Reason:
You entered a command without an expected operand.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
You specified an invalid name in P1.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1.
Reason:
An AT/EVERY or AFTER command has been entered. P1 specifies the command to be issued when the timer triggers.
System Action:
The command is scheduled for execution.
User Action:
None.
Reason:
A message has been received.
P1 specifies the sender of the message.
P2 specifies the message text.
System Action:
None.
User Action:
None.
Reason:
You entered a command incorrectly.
Note: For some error conditions, Tivoli NetView emulation may supplement this message with additional explanation text ( P1 ).
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
An invalid VTAM command has been entered.
System Action:
The command is not processed.
User Action:
Enter a valid VTAM command.
Reason:
Message failed to reach active user, identified by P1.
Receipt of broadcast type messages may be controlled by the PROFILE of the target environment. An environment set with PROFILE MSG=N or PROFILE UNSOL=N cannot receive messages unless directed to the individual user.
Depending on the type of message, P2 either quotes the NetMaster message number received by the emulation or gives a reason for the message failure: OCS WINDOW CLOSED - recipient's OCS session was closed
NOT IN OCS MODE - recipient's terminal is not in OCS mode
System Action:
None.
User Action:
Use the reason provided by P2 to determine the cause of the error.
Consider changing MSG and UNSOL parameters in your profile to allow the messages to be received.
Reason:
The identifier specified in P1 is not known to NetMaster.
System Action:
The command is not processed.
User Action:
Specify a valid identifier.
Reason:
The data set specified in P1 cannot be read.
System Action:
The command is not processed.
User Action:
Specify a valid data set name.
Reason:
A CLOSE Normal command has been entered. No other logons are permitted and NetMaster will shutdown when all users have logged off.
P1 specifies the shutdown mode.
P2 specifies the user who issued the command.
System Action:
NetMaster stops any further users logging on and once all users are logged off NetMaster shuts down.
User Action:
None.
Reason:
An error occurred while processing a Pipe command.
P1 specifies the position the error occurred within the command.
P2 specifies some of the preceding Pipe command text.
System Action:
The command is not processed.
User Action:
Correct the Pipe command syntax.
Reason:
An AT/EVERY or AFTER command has been issued and P1 specifies the NetMaster generated identifier.
System Action:
The command is scheduled for execution.
User Action:
None.
Reason:
A timer request cannot be scheduled.
System Action:
The command is not processed.
User Action:
Check the activity log for related messages to determine the reason for the error.
Reason:
The time parameter is invalid.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
The number of timer elements specified in P1 have been purged by the user specified in P2 .
System Action:
None.
User Action:
None.
Reason:
The command specified in P1 failed because the invalid parameter specified in P2 was entered.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
Specifies that the command has been issued.
System Action:
None.
User Action:
None.
Reason:
A command specified in P1 has been issued in an invalid environment by the user specified in P2 . For example, the command might be intended to be:
- Issued only from a REXX procedure
- Issued only as a native command
System Action:
The command is not processed.
User Action:
Check the command usage, correct and resubmit.
Reason:
An attempt has been made to allocate a file that is already in use.
System Action:
The command is not processed.
User Action:
Determine why the data set is allocated and either wait for the data set to become available or use another data set.
Reason:
A FREE command failed because the data set specified in P1 is not allocated.
System Action:
The command is not processed.
User Action:
Specify the name of an allocated data set or determine why the specified data set is not currently allocated.
Reason:
You entered an invalid operand or keyword in P1.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
The command P1 has completed successfully.
System Action:
None.
User Action:
None.
Reason:
The keyword specified in P1 is invalid.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
The keyword specified in P1 has been entered more than once.
System Action:
The command is not processed.
User Action:
Specify the keyword once in the command.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
There is a conflict between the keyword specified in P1 and the keyword specified in P2.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
The keyword specified in P1 has been assigned an invalid value specified in P2.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
A command specified in P1 has been entered incorrectly.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
An expected keyword specified in P1 is missing.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
A keyword specified in P1 has been specified without a value.
System Action:
The command is not processed.
User Action:
Specify a value for the keyword.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
The member name specified in P1 on dataset P2 was not found or was empty.
System Action:
The command is not processed.
User Action:
Review the member specified in P1 or specify a valid member name.
Reason:
The stem variable record count specified in P1 must be zero or a positive number that does not exceed 10000000. If the REXX environment has a limit of less than 10000000 then that is the maximum stem count that can be passed to the Stem Pipe stage command.
System Action:
The command is not processed.
User Action:
Ensure the stem variable count does not exceed a count of 10000000 or the maximum supported in the REXX environment in which it is running.
Reason:
Command P1 was deleted from the P2 definitions.
System Action:
The command is removed.
User Action:
None.
Reason:
Command P1 failed. P2 is empty or has comment statements only.
System Action:
The command is not processed.
User Action:
Check the source definitions. Correct any syntax error and add the missing definition statements.
Reason:
An invalid option was specified in a Pipe stage command.
P1 specifies the invalid option.
P2 specifies the command that rejected the option.
System Action:
The command is not processed.
User Action:
Specify a valid option.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
Specifies that a Pipe command has failed.
P1 specifies the number of the pipe stage that failed.
P2 specifies the name of the pipe.
P3 specifies the stage text.
System Action:
The command is not processed.
User Action:
Correct the Pipe command syntax.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
A Pipe command was entered without any Pipe stage commands.
System Action:
The command is not processed.
User Action:
Specify Pipe stage commands with the Pipe command.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
Unrecognized Pipe stage name P1 was found in the Pipe command.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
A positional keyword specified in P1 has been specified but is in the wrong position.
System Action:
The command is not processed.
User Action:
Place the keyword in the correct position.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
An out of range numeric value P1 was specified.
System Action:
The command is not processed.
User Action:
Correct the specified value.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
An invalid delimiter character or an invalid option value has been specified.
System Action:
The command is not processed.
User Action:
Specify a valid delimiter character or option value.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
(MOE) option was specified on P1 stage command. The stage command encountered an error.
P2 is the number of the stage command that reported the error.
P3 is the return code for the error.
System Action:
The Pipe stage command terminates.
User Action:
For more information about the return code, see the online help for the stage command.
To view online help, enter NCCF at the Console (OCS) and press F1.
Reason:
No matching end delimiter was found for the string specified in P1 .
System Action:
The command is not processed.
User Action:
Specify a matching end delimiter.
Reason:
The Pipe stage command specified in P1 cannot not be the first stage command in a Pipe command.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
A Pipe stage command that can only be the first stage of a Pipe command has been specified in a later stage.
System Action:
The command is not processed.
User Action:
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
A string specified in P1 is greater in length than the maximum length specified in P2 . The length of the erroneous string is P3 .
System Action:
The command is not processed.
User Action:
Limit the specified string to the value specified in P2 .
Reason:
A position.length string has been specified with either a position or length value equal to zero. P1 specifies the POS.LEN string.
System Action:
The command is not processed.
User Action:
Correct the POS.LEN string.
Reason:
A remote session could not be established with a remote NetMaster luname specified in P1 .
System Action:
The command is not processed.
User Action:
Ensure that there is an INMC link between this NetMaster region and the remote. See NetMaster's online help for the Link command.
To view online help, enter "Help Link" at the NetMaster Console (OCS).
Reason:
Command text was not present in the command specified in P1.
System Action:
The command is not processed.
User Action:
Specify command text.
For more information about supported commands and operands, see the online help and the NetMaster REXX Guide.
To view online help, enter NCCF at the NetMaster Console (OCS) and then press F1 (Help).
Reason:
The highlighted data set name is already specified.
System Action:
The name is not accepted, and the field is set in error.
User Action:
Remove the duplicate name.
Reason:
The DSIPARM or NVPANELS dataset must be specified as a partitioned Dataset (PDS). Individual PDS member specification is also invalid.
System Action:
Field is set in error.
User Action:
Specify a PDS name without member specification.
Reason:
A previously-concatenated set of partitioned datasets assigned to the DDname given by P1 was deconcatenated. This process is normal when the new definitions for DSIPARM or Netview panels are activated.
System Action:
The Netview emulation initialization wizard continues.
User Action:
None.
Reason:
Deconcatenation of the set of partitioned datasets assigned to the DDname given by P1 failed.
P2 is the return code.
P3 is the reason message.
System Action:
The Netview emulation initialization wizard attempts to continue.
User Action:
Press PF5 to view the wizard log and look for possible reasons and actions.
Reason:
The previously-allocated partitioned dataset P1 assigned to the DSIPARM or NVPANELS DDname was deallocated. This is a normal process when the new definitions for DSIPARM or Netview panels are activated.
System Action:
The Netview emulation initialization wizard continues.
User Action:
None.
Reason:
Deallocation of the partitioned dataset P1 allocated to the DSIPARM or NVPANELS failed.
P2 is the return code.
P3 is the reason message.
System Action:
The Netview emulation initialization wizard attempts to continue.
User Action:
Press PF5 to view the wizard log and look for possible reasons and actions.
Reason:
The partitioned dataset P1 was allocated to DSIPARM or NVPANELS.
P2 is the DDname.
System Action:
The Netview emulation initialization wizard continues.
User Action:
None.
Reason:
Allocation of the partitioned dataset P1 to the DSIPARM or NVPANELS DD failed.
P2 is the return code.
P3 is the reason message.
System Action:
The Netview emulation initialization wizard attempts to continue.
User Action:
Press PF5 to view the wizard log and look for possible reasons and actions.
Reason:
A defined collection of up to five partitioned datasets were allocated to P1 DDname.
System Action:
The Netview emulation initialization wizard continues.
User Action:
None.
Reason:
Concatenation of the set of partitioned datasets assigned to the DDname given by P1 failed.
P2 is the return code.
P3 is the reason message.
System Action:
The Netview emulation initialization wizard attempts to continue.
User Action:
Press PF5 to view the wizard log and look for possible reasons and actions.
Reason:
The Netview emulation initialization parameters were obtained from DSIPARM Datasets.
P1 is the DSIPARM PDS statement name.
P2 is the DSIPARM PDS memeber name.
System Action:
The Netview emulation initialization wizard continues.
User Action:
None.
Reason:
An attempt to access the Netview emulation initialization member P1 in any of the partitined datasets allocated to P2 DDname failed.
System Action:
The Netview emulation initialization wizard assigns default values to the parameters expected in the specified member.
User Action:
Ensure that the PDS that contains the P1 member is allocated to the
P2 DDname. Correct the situation and reactivate the parameter group.
Reason:
An attempt to access one of the partitioned datasets allocated to Netview emulation P1 DDname or reading member P2 failed.
System Action:
The Netview emulation initialization wizard assigns default values to the parameters expected in the specified member.
User Action:
Press PF5 to view the log and look for messages that indicate the reason for the error. Correct the situation and reactivate the parameter group. Verify that P2 member exists in PDS P1 .
Reason:
A call to internal routines returned an unexpected return code.
P1 describes the source of the error.
System Action:
The Netview emulation initialization wizard assigns default values to the parameters expected in the specified member.
User Action:
Contact Technical Support.
Reason:
The Command Characteristic Definition (CCDEF) member of DSIPARM finished. P1 is the Return Code. If the Return Code reported is greater than 0, see the activity log for more information.
System Action:
The Netview emulation initialization wizard continues.
User Action:
View the activity log for messages that report errors. Correct the situation and reactivate the parameter group.
Reason:
An attempt to open the library with a DD of P1 failed with return code
P2 feedback code P3 and an error message P4
System Action:
Request to load a panel fails.
User Action:
Investigate why the panels library cannot be opened. Correct the problem and retry.
Reason:
An attempt to open the panel P1 failed with return code P2 feedback code
P3 and an error message P4
System Action:
Request to load a panel fails.
User Action:
Attempt to correct the problem and retry.
Reason:
An attempt to read the panel P1 failed with return code P2 feedback code
P3 and an error message P4
System Action:
Request to load a panel fails.
User Action:
Attempt to correct the problem and retry.
Reason:
Panel P1 was successfully read and found to contain P2 lines. It is followed by one or more XNLOAD05 messages that contain the panel definition as read from the file.
System Action:
None.
User Action:
None.
Reason:
This message is generated only if the GLOBAL variable $XNLOAD is set to YES.
System Action:
None.
User Action:
None.
Reason:
Panel P1 is defined with the KK option. This is not supported in the CA NetMaster REXX VIEW implementation.
System Action:
Panel is not displayed.
User Action:
None.
Reason:
NetView Pipe emulation Extended Trace ( XDB ) was specified. There is one XNPI000 message for each Pipe option ( P1 ) and its value ( P2).
System Action:
None.
User Action:
None.
Reason:
NetView Pipe emulation Extended Trace ( XDB ) was specified. These messages list the Pipe Stage Groups.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
NetView Pipe emulation Extended Trace ( XDB ) was specified.
P1 is the Maximum Message Segment Size.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
NetView Pipe emulation - More than one P1 prefix was found on a stage specification.
System Action:
The command is not processed.
User Action:
Check the syntax of the command.
Reason:
NetView Pipe emulation - Pipe stage P1 has no connections to any other stage.
System Action:
The command is not processed.
User Action:
Check the syntax of the command.
Reason:
NetView Pipe emulation - Found a Pipe stage connector with no related stage specification.
System Action:
The command is not processed.
User Action:
Check the syntax of the command.
Reason:
NetView Pipe emulation - Found a misplaced stage connector.
System Action:
The command is not processed.
User Action:
Check the syntax of the command.
Reason:
Stage name P1 is not supported by NetView Pipe emulation.
System Action:
The command is not processed.
User Action:
None.
Reason:
NetView Pipe emulation does not support stage name P1 from a REXX environment.
System Action:
The command is not processed.
User Action:
None.
Reason:
Stage name P1 is not directly supported from a native environment.
System Action:
The command is not processed.
User Action:
None.
Reason:
Error in updating the In-storage NetView Pipe emulation stage table.
P1 is the feedback code.
P2 is the entry key (stage name).
System Action:
None.
User Action:
Contact Technical Support.
Reason:
Error in accessing a stage alias full name entry from the In-storage NetView Pipe emulation stage table.
P1 is the feedback code.
P2 is the entry key (stage full name).
System Action:
None.
User Action:
Contact Technical Support.
Reason:
A NetView Pipe was called from another NetView Pipe. The required NetView Pipe emulation Environment Table P1 could not be located.
System Action:
The request is terminated.
User Action:
Contact Technical Support.
Reason:
Error in adding the NetView Pipe Default SAFE entry to the NetView Pipe emulation environment table.
P1 is the entry key.
P2 is the table name.
P3 is the feed back code.
System Action:
The request is terminated.
User Action:
Contact Technical Support.
Reason:
An internal error has occurred in the NetView PIPE emulation command handler.
P1 is the internal error number.
P2 is the error reason text.
System Action:
The request terminates.
User Action:
Contact Technical Support.
Reason:
Error accessing a CCDEF entry in the in-storage NetView PIPE emulation Command Characteristic Definition Table.
P1 is the table name.
P2 is the key (command name).
P3 is the feedback code.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
In-storage NetView Pipe emulation tables have been rebuilt.
System Action:
None.
User Action:
None.
Reason:
In-storage NetView Pipe emulation stage tables builder was called with an invalid parameter.
P1 is the parameter.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
Error in adding a prime entry to the In-storage NetView Pipe emulation stage table.
P1 is the feedback code.
P2 is the entry key.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
Error in adding an alias entry to the In-storage NetView Pipe emulation stage table.
P1 is the feedback code.
P2 is the entry key.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
Error in adding a prime entry to the In-storage NetView Pipe emulation EDIT order table.
P1 is the feedback code.
P2 is the entry key.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
Error in adding an alias entry to the In-storage NetView Pipe emulation EDIT order table.
P1 is the feedback code.
P2 is the entry key.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
Error allocating the in-storage NetView Pipe emulation CCDEF table.
P1 is the table name.
P2 is the feedback code.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
Error accessing a command entry in the in-storage NetView PIPE emulation Command Characteristic Definition Table.
P1 is the failing action.
P2 is the table name.
P3 is the key (command name).
P4 is the feedback code.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
The in-storage NetView PIPE emulation Command Characteristic Definition Table (CCDEF) does not exist. A default table is built.
P1 is the table name.
System Action:
A default CCDEF table is built; command processing continues.
User Action:
Check the activity log for related error messages. Contact Support.
Reason:
NetView Pipe emulation Extended Trace ( TRACE ) was specified.
P1 is the NCL ID.
P2 is the trace data.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
NetView pipe emulation executor failed. An unexpected PIPEHELP NOTIFY message was received. P1 is the NOTIFY text.
System Action:
The PIPE command terminates.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Pipe emulation executor failed during the stage handshake procedure. P1 is the handshake data.
P2 is the stage number.
System Action:
The PIPE command is terminated.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Pipe emulation executor failed. An unexpected message was received. P1 is the message text.
System Action:
The PIPE command is terminated.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Pipe emulation executor failed. An unsupported REXXHELP request was received.
P1 is the REXXHELP Request.
P2 is the stage number.
System Action:
The PIPE command is terminated.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Pipe emulation DEBUG 1 option was specified and/or the Pipe stage (DEBUG) option was specified. This message and its companion message XNPI0514 list the Pipe stages input and output streams connections.
P1 is the stage output stream number.
P2 is the stage number.
P3 is the stage specification.
System Action:
None.
User Action:
None.
Reason:
NetView Pipe emulation DEBUG 1 option was specified and/or the Pipe stage (DEBUG) option was specified.
This message and its companion message XNPI0513 list the Pipe stages input and output streams connections.
P1 is the stage input stream number.
P2 is the stage number.
P3 is the stage specification.
System Action:
None.
User Action:
None.
Reason:
NetView Pipe emulation executor failed. A message segment has an incorrect segment sequence number.
P1 was the expected segment sequence number.
P2 is the message segment sequence number.
P3 is the message segment type ( NOTLAST / LAST ).
P4 is the message context (issuing NCLID).
P5 is any additional information.
System Action:
The Pipe command is terminated.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Emulation Pipe Command Executor failed.
P1 is the function/procedure executing at the time of the error.
P2 is the error text.
System Action:
The request is terminated.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Pipe emulation Extended Trace ( TRACE ) was specified.
P1 is the NCL ID.
P2 is the trace data.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
NetView Pipe emulation error has occurred.
P1 is a message of a group of messages that traps the related error details.
System Action:
The Pipe command terminates.
User Action:
Contact Technical Support.
Reason:
NetView pipe emulation stage driver has failed.
P1 is the Stage number.
P2 is the function or procedure executing at the time of the error.
P3 is the error text.
System Action:
The PIPE command terminates.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Pipe emulation DEBUG 1 option was specified and/or the Pipe stage (DEBUG) option was specified.
P1 is the stage number.
P2 is the stage command.
P3 is the stage command execution time. (in seconds and microseconds)
System Action:
None.
User Action:
None.
Reason:
NetView Pipe emulation Extended Trace ( TRACE ) was specified.
P1 is the NCL ID.
P2 is the Trace data.
System Action:
None.
User Action:
Contact Technical Support.
Reason:
NetView Emulation Pipe Command Support Package failed. o P1 is the function/procedure executing at the time of the error. o P2 is the error text.
System Action:
The request is terminated.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Emulation Pipe Command Support Package has encountered a stream status error.
P1 is the Pipe stage number.
P2 is the Pipe stream type (input/output).
P3 is the Pipe stream number.
P4 is the Pipe stream status.
P5 is the current request type.
System Action:
The request is terminated.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Emulation Pipe Command Support Package has encountered an unrecoverable error.
P1 is the Pipe stage number.
P2 is the internal procedure name.
P3 is the error text.
System Action:
The request is terminated.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Pipe emulation stage CONSOLE has failed with an internal error.
P1 is the failing operation.
P2 is the return code.
System Action:
The Pipe command terminates.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Pipe emulation failed during the execution of a CORRWAIT stage. The CORRWAIT stage could not start the procedure P1 . The return code is
P2 and the feedback code is P3 .
System Action:
The Pipe command is terminated.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Pipe emulation failed during the execution of a CORRWAIT stage. The Command Service Procedure is P1 . The reason is P2 .
System Action:
The Pipe command terminates.
User Action:
Review the Activity Log for related error messages and correct, if applicable.
If the error is not a usage error, contact Technical Support with the diagnostic data provided.
Reason:
NetView Pipe emulation failed during the execution of a CORRWAIT stage. The CORRWAIT stage received a command response message segment with an incorrect segment sequence number.
P1 was the expected segment sequence number.
P2 is the message segment sequence number.
P3 is the message segment type ( NOTLAST / LAST ).
P4 is the message context (issuing NCLID).
P5 is any additional information.
System Action:
The Pipe command is terminated.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Pipe emulation failed during the execution of a CORRWAIT stage. The CORRWAIT stage received an unexpected response text from the Command Procedure.
P1 is the Command Procedure name.
P2 is the Pipe Stage number.
P3 is the Command Procedure response.
System Action:
The Pipe command is terminated.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Pipe emulation failed during the execution of a CORRWAIT stage. The command service procedure terminated in error.
P1 is the Command Service Procedure name.
P2 is the reason for the error.
System Action:
The Pipe command terminates.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Pipe emulation stage DROP has failed.
P1 is the failing operation.
P2 is the feedback code.
System Action:
The Pipe command terminates.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
NetView Pipe emulation stage DROP has failed with a message segmentation error, P1 is the error details.
System Action:
The Pipe command terminates.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
EDIT P1 order P2 is not supported by NetView Pipe emulation.
System Action:
The command is not processed.
User Action:
None.
Reason:
Error in accessing a EDIT order alias full name entry from the in-storage NetView Pipe emulation EDIT order table.
P1 is the feedback code.
P2 is the entry key (order full name).
System Action:
The Pipe command is terminated.
User Action:
Contact Technical Support.
Reason:
The specified NetView Pipe emulation EDIT HEXSTRING order is not a valid hexadecimal string. P1 is the specified string.
System Action:
The Pipe command is terminated.
User Action:
Check specification.
Reason:
A NetView Pipe emulation EDIT order has been mapped to an unsupported order code. The associated order parameter was P2. The in-storage NetView Pipe emulation EDIT order table $XNPI01B may be corrupted or could have been updated incorrectly.
System Action:
The Pipe command is terminated.
User Action:
Contact Technical Support.
Reason:
NetView Pipe emulation - Parsing error. The closing delimiter P1 is not the last character of the LITERAL string.
System Action:
The command is not processed.
User Action:
Check the syntax of the command.
Reason:
Vartable processing encountered an MDO that had more than 9999 MDO segments. P1 specified the segment count.
System Action:
Pipe processing is aborted.
User Action:
Re-run the pipe stage. If the problem persists, contact Technical Support and provide a copy of this message and a copy of the Pipe Stage command being executed when this failure occurred.
Reason:
During reference record processing a Vartable action specified in P1 failed with a feedback code specified in P2 .
System Action:
Pipe processing is aborted.
User Action:
Re-run the pipe stage. If the problem persists, contact Technical Support and provide a copy of this message and a copy of the Pipe Stage command being executed when this failure occurred.
Reason:
NetMaster's implementation of the NetView PIPE stage does not support parameter P1 .
System Action:
Pipe processing is aborted.
User Action:
Remove the parameter P1 and rerun the Pipe stage.
Reason:
Safe default processing encountered an MDO that had more than 9999 MDO segments. P1 specified the segment count.
System Action:
Pipe processing is aborted.
User Action:
Re-run the pipe stage. If the problem persists, contact Technical Support and provide them with a copy of this message and a copy of the Pipe Stage command being executed when this failure occurred.
Reason:
During safe default processing a Varatable Add failed.
P1 specified the feedback code at the time of the failure.
System Action:
Pipe processing is aborted.
User Action:
Re-run the pipe stage. If the problem persists, contact Technical Support and provide them with a copy of this message and a copy of the Pipe Stage command being executed when this failure occurred.
Reason:
NetView Pipe emulation failed during the execution of a NETVIEW stage. The NETVIEW stage received a command response message segment with an incorrect segment sequence number.
P1 was the expected segment sequence number.
P2 is the message segment sequence number.
P3 is the message segment type ( NOTLAST / LAST ).
P4 is the message context (issuing NCLID).
P5 is any additional information.
System Action:
The Pipe command is terminated.
User Action:
Contact Technical Support with diagnostic data provided.
Reason:
NetView Pipe emulation failed during the execution of a NETVIEW stage. The reason is P1 .
System Action:
The Pipe command terminates.
User Action:
Review the Activity Log for related error messages and correct if applicable.
If the error is not a usage error, contact Technical Support with the diagnostic data provided.
Reason:
NetMaster's implementation of the SORT Pipe Stage does not support position or length values greater than 256. P1 specifies the value in error.
System Action:
Pipe processing is aborted.
User Action:
Specify a value between 1 and 256 and rerun the Pipe Stage.
Reason:
NetMaster's implementation of the SORT Pipe Stage does not support the total length value greater than 256. P1 specifies the value in error.
System Action:
Pipe processing is aborted.
User Action:
Ensure that the total length of the specified position length pair does not exceed 256 and rerun the Pipe Stage.
Reason:
NetMaster's implementation of the NetView Pipe Stage does not support parameter P1 .
System Action:
Pipe processing is aborted.
User Action:
Remove the parameter P1 and rerun the Pipe Stage.
Reason:
NetMaster's implementation of the SUBSYM Pipe Stage does not support message text that is greater than 256 characters in length.
System Action:
Pipe processing is aborted.
User Action:
Ensure messages passed to the SUBSYM Pipe Stage are not longer than 256 characters.
Reason:
Pipe Stage TAKE has failed.
P1 is the failing operation.
P2 is the feedback code.
System Action:
The Pipe command terminates.
User Action:
Contact Technical Services with any diagnostic data provided.
Reason:
Pipe Stage TAKE has failed with a message segmentation error,
P1 is the error details.
System Action:
The Pipe command terminates.
User Action:
Contact Technical Support with any diagnostic data provided.
Reason:
NetMaster's implementation of the Netview PIPE Stage does not support parameter P1 .
System Action:
Pipe processing is aborted.
User Action:
Remove the parameter P1 and rerun the Pipe Stage.
Reason:
The stage identitied in P1 has been invoked in a nested environment. This is not currently supported in the NetMaster emulation of this stage.
System Action:
The Pipe command is terminated.
User Action:
Do not invoke this stage in a nested environment.
Reason:
NetMaster's implementation of the VTAM Pipe Stage does not support parameter P1 .
System Action:
Pipe processing is aborted.
User Action:
Remove the parameter P1 and rerun the Pipe Stage.
Reason:
NetView Emulation Pipe Command Package procedure has encountered an unrecoverable PIPEHELP error.
P1 is the pipe stage number.
P2 is the pipe stream number.
P3 is the PIPEHELP verb that failed.
P4 is the error text.
System Action:
The request terminates.
User Action:
Contact Technical Support with the diagnostic data provided.
Reason:
The CACHE request P1 failed because of reason P2.
System Action:
The VIEW command terminates in error.
User Action:
Global variable &GLBL$XNVIEW can be set to YES to output details of CACHE requests to the activity log.
Reason:
A REXX procedure has issued the VIEW command, but the REXX procedure is not running in full-screen mode. The most likely cause is a REXX procedure running as part of a remote PIPE stage.
System Action:
The VIEW command terminates in error.
User Action:
Do not use REXX procedures that use the VIEW command unless in full-screen mode.
Reason:
This message is generated only if the GLOBAL variable $XNVIEW is set to YES.
System Action:
None.
User Action:
None.
Reason:
A REXX procedure issued the VIEW command and specified more than P2 unique panel attribute combinations.
System Action:
The VIEW command terminates in error.
User Action:
Review the use of panel attribute variables to reduce the number of unique combinations.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |