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 CA OPS/MVS API request was sent to a target system. However, the system is unknown or no CA NetMaster region on that system is linked to this region. p1 identifies the target system.
System Action:
The request terminates.
User Action:
Reason:
An invalid value p2 for parameter p1 was passed on the CA OPS/MVS API call (an internal error).
System Action:
The request terminates.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
While trying to extract the resource information from the CA OPS/MVS RDF tables, the p1 function call returned RC p2 and optionally, SQLCode p3.
System Action:
Extraction of resource information from the RDF tables fails.
User Action:
Review the job log for any error messages that the called OPS/REXX function generates.
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:
Specify a supported channel. The following channels are supported: ALERTS.
Enable the supported channels that are not registered on the RSS Feeds panel in the INTERFACES WEBCENTER parameter group of the associated region.
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:
An invalid value for the LIMIT parameter was specified on the URL.
System Action:
Process terminates.
User Action:
Take one of the following actions:
Note: If a larger value is specified, the region enforces an implicit limit of 2000.
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:
A CA SYSVIEW command was attempted to the target system p1. This system is either unknown or not connected to this region.
System Action:
The command is not executed.
User Action:
Specify a correct system ID for a connected system.
Reason:
A CA SYSVIEW API request was sent to a target system that is either unknown or not linked to this region. p1 identifies the target system.
System Action:
The request terminates.
User Action:
Reason:
An invalid value p2 for parameter p1 was passed on the CA SYSVIEW API call (an internal error).
System Action:
The request terminates.
User Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
A request was directed to the CA SYSVIEW API. The API was not found in the system linklist or in the STEPLIB of the region.
System Action:
The request terminates.
User Action:
If CA SYSVIEW is installed, ensure that its load library is in the system linklist or in the STEPLIB of the region.
Reason:
A request was directed to the CA SYSVIEW API. The API did not respond in a reasonable time.
System Action:
The request terminates.
User Action:
Search for any related system or CA SYSVIEW messages or ABENDs in the region job log or system log. For assistance, contact CA Support at http://ca.com/support.
Reason:
A request was directed to the CA SYSVIEW API. The RXXCMD call failed with return code p1.
System Action:
The request terminates.
User Action:
Search for any related messages or ABENDs in the region job log or system log. For assistance, contact CA Support at http://ca.com/support.
Reason:
A request to the CA SYSVIEW API failed. p1 is the return code.
System Action:
The request terminates.
User Action:
Search for any related CA SYSVIEW messages or ABENDs in the region job log or system log. For assistance, contact CA Support at http://ca.com/support.
Reason:
A request was directed to the CA SYSVIEW API. The API returned RC=20. This code indicates that either the API failed to initialize or terminated.
System Action:
The request terminates.
User Action:
Search for any related CA SYSVIEW messages or ABENDs in the region job log or system log. For assistance, contact CA Support at http://ca.com/support.
|
Copyright © 2014 CA.
All rights reserved.
|
|