Messages EVJ000I to EVJ440I (TWS Automation)
EVJ000I date time module ENTRY/EXITparms/RC=rc
Explanation
When the trace option is activated, TWS Automation
writes this data to the log for entry and exit tracing. The date is shown in the format
mm/dd/yyyy.
Operator response
None.
EVJ001I command: STARTED, PARMS=parameters
Explanation
Command processor has been entered with the parameters shown. This is an informational message issued for audit purposes.
System action
None.
Operator response
None.
System programmer response
None.
Destination
Command processor name, parameters.
EVJ002I command: COMPLETED SUCCESSFULLY, PARMS=parms
Explanation
Command processor has completed successfully. This is an informational message issued for audit purposes.
System action
None.
Operator response
None.
System programmer response
None.
Destination
Command processor name, parameters.
EVJ003E command UNABLE TO PROCESS PARMS=(parameters), REASON=reason
Explanation
OPC has initiated a request, but it cannot be processed due to the reason shown. This message will normally be preceded by a message giving specific details of the failure.
System action
The request is canceled.
Operator response
Review log for other messages.
System programmer response
Resolve any system or definition problems, then reset the request.
Destination
Request parameters, reason text.
EVJ005E module UNABLE TO OBTAIN parameter
Explanation
The module indicated tried to obtain the value of a parameter from product globals, but the value was null or not as expected.
System action
The module ceases processing and returns a non-zero return code to its calling routine.
Operator response
Review log for other messages and notify your system programmer.
Determine the source of the failure, typically an incorrect control file value or failure of the product initialization routines (beginning with EVJEAAIC) to run, and correct it. Call IBM® Service if you require assistance.
Destination
Module name and failing parameter
EVJ006E cmdname COMMAND FAILED FOR module: RETURN CODE=rc PARMS=parms
Explanation
A command issued within this command processor received an invalid return code.
- The variable cmdname shows the name of the command that failed.
- The variable module shows the name of the calling command processor.
- The variable rc shows the return code from the failing command.
- The variable parms shows the parameters passed to the failing command.
System action
The command processor terminates and logs an error message.
Operator response
Review the error messages in the NetView and MVS logs.
System programmer response
Review the associated error messages in the NetView and MVS logs. If necessary, correct definition problems and retry the operation.
EVJ007E SUBSYSTEM subsys IN INVALID STATUS stat FOR REQUEST (request)
Explanation
TWS Automation has attempted to execute the request for the indicated subsystem, but was unable to complete because the subsystem was in an invalid status. For example, trying to start a subsystem that is already up, or stop a subsystem that is already down.
System action
The operation in OPC is posted in error with a U001 status.
Operator response
Review NetView log for prior activity for the subsystem.
Check for manual intervention with the subsystem, such as starts and stops performed outside of automation control. Also, for shutdowns, specify RESTART=CTL so that subsystems will not be restarted by NetView initializations.
Destination
Command processor name, subsystem, subsystem status, TWS Automation request type.
EVJ008E OPERATION ALREADY IN PROGRESS FOR subsys, REQUEST=(reqparms)
Explanation
TWS Automation has attempted to execute the request for the indicated subsystem, but was unable to process because a previous request is still outstanding for the subsystem, or the previous request may not have completed successfully.
- The variable subsys shows the name of the subsystem involved.
- The variable reqparms shows the details of the previous request.
System action
The new operation, indicated by additional message EVJ003E is posted in error with a U005 status.
Operator response
Review NetView log for prior activity for the subsystem.
Check for previous errors in the log, or review TWS and workstation definitions. When problems are resolved, reset the TWS status file record using OPCAQRY and rerun the operation.
EVJ009E NO RESPONSE FROM SYSTEM domainid WHILE SENDING REQUEST (request)
Explanation
TWS Automation has attempted to forward the request to the remote domain, but did not receive an acknowledgment from that system.
System action
The operation in OPC is posted in error with an S999 status.
Operator response
Check status and connectivity of the system in question. If the problem can be resolved, rerun the failing operation.
Your gateway to the remote NetView is blocked, or the remote system may be extremely busy. If the former, you should resolve the gateway problem. If the latter you should schedule your operations on this remote NetView farther apart.
Destination
Domain ID, request parameters.
EVJ010I variable data
Explanation
This message is used internally to transfer data between systems.
System action
None, this is a normal message.
Operator response
None.
Destination
Date, time, message text.
EVJ011I date time OPC message text
Explanation
While attempting to communicate with OPC, an operator initiated request to display or modify data has failed. The message text is the OPC message received. This message is normally preceded by another message, indicating the TWS Automation module that was attempting to request data from OPC.
System action
None.
Operator response
Review message in the appropriate OPC/ESA or OPC/A manual.
Correct problems such as incorrect definitions of OPC subsystem name.
Destination
Date, time, message text.
EVJ025E INVALID VALUE "value" FOR keyword
Explanation
The parameter you have supplied is not valid.
System action
None.
Operator response
Try again using the correct parameters.
EVJ026E MISSING PARAMETER parameter
Explanation
The parameter is required, but was omitted.
System action
None.
Operator response
Try again using the correct parameters.
EVJ029I command ENCOUNTERED UNEXPECTED EVENT event_name
Explanation
The indicated command was issued, but the response received was not as desired. For example, the command may have timed out, or the procedure may have been canceled while waiting for a message.
System action
None.
Operator response
Investigate the cause of the failure.
EVJ040I PROCESSING COMMANDS
Explanation
The TWS Batch Command Processor is starting.
System action
None.
Operator response
None.
EVJ041E POSITIONAL PARAMETER name MUST BE SPECIFIED
Explanation
The parameter mentioned in the message is required and must be specified.
System action
Batch command processing aborts and the batch job ends with RC=16.
Operator response
Correct the EVJRYCMD command and retry.
EVJ042E PARAMETER name ERROR, VALUE NOT NUMERIC
Explanation
The value specified in parameter name is not numeric. The value must be a number.
System action
Batch command processing aborts and the batch job ends with RC=16.
Operator response
Correct the EVJRYCMD command and retry.
EVJ043E PARAMETER name ERROR, information
Explanation
The value of the named parameter is incorrect.
- The variable name represents the parameter in error.
- The variable information contains the detail of the error.
System action
Batch command processing aborts and the batch job ends with RC=16.
Operator response
Contact your system programmer.
System programmer response
Ensure that the PPI destination named is 1 to 8 characters in length and consists of alphanumeric characters.
EVJ044E PARAMETER TRACE ERROR, INVALID VALUE - SEE THE REXX TRACE COMMAND
Explanation
Specification of the TRACE= parameter requires a value consistent with the REXX Trace command.
System action
Batch command processing aborts and the batch job ends with RC=16.
Operator response
Contact your system programmer.
System programmer response
Check with your IBM Support Center. Re-specify the TRACE= parameter with the correct value.
EVJ045I OPENING PPI INTERFACE FROM source TO destination
Explanation
Command Processing is about to send commands to the SA z/OS PPI command processor. This message is issued when the PPI interface is being opened.
- The variable source is the PPI Sender id used for this batch job.
- The variable destination is the PPI receiver name of the command server. It is specified with the SERVER= parameter.
System action
Processing continues.
Operator response
None.
System programmer response
None.
EVJ046E UNABLE TO OPEN PPI FOR receiver_name
Explanation
An attempt to open the PPI receiver named receiver_name failed. This message is followed by EVJ047I that describes why the attempt to open failed.
System action
Command processing is aborted and the batch job will terminate with return code 20.
Operator response
Contact your system programmer.
System programmer response
Check message EVJ047I to find the probable cause of the error.
EVJ047I dsiphone_error [, PPI reason ppi_error]
Explanation
This message provides details of the NetView DSIPHONE error that caused processing to fail. It also gives details of the PPI error reason if that is feasible.
The DSIPHONE error responses are:
- DSIPHONE called without arguments.
- Too many parameters for this request type.
- Too few parameters for this request type.
- Invalid request type.
- REXX stem or variable name too long.
- REXX variable operation failed.
- PPI receiver name is too long.
- PPI request failed.
- Stem's .0 element invalid.
- Too many elements in stem.
- First line of MLWTO not control line.
- Invalid WAIT interval specified.
- Argument 6 is not 'APPEND' or blank.
- PPI RECEIVE timed out.
- Invalid MLWTO line type attribute.
- Invalid MLWTO attribute length.
- Unable to obtain storage.
- Invalid attempt to call DSIPHONE from NetView.
- Invalid attempt to call DSIPHONE.
- Internal error.
- An unknown error occurred.
The PPI error responses are:
- The specified receiver is not active.
- The PPI is available.
- The receiver program is active.
- The receiver program is inactive.
- The receiver program is already active.
- The receiver ECB is not zero.
- The request code is not defined.
- The program is not in Primary Addressing mode.
- The program is not authorized.
- The PPI interface is not active.
- The ASCB address is not correct.
- The receiver program is not defined.
- No active SSI for PPI found.
- No data buffer in receiver buffer queue.
- Receiver buffer is not large enough.
- No NetView storage available.
- Buffer length is not valid.
- Receiver queue is full.
- ESTAE recovery cannot be established.
- Sender or Receiver ID not valid.
- Processing error has occurred.
- System abend occurred.
- User abend occurred.
- AIFR or the input length was not valid.
- Could not identify the data as a message.
- Incomplete multiline message was discarded.
- Illegal alert forwarding loop was detected.
- Specified target type does not support the data.
- User is not authorized.
- An unknown error occurred.
Numeric codes may also be present for either the DSIPHONE code or the PPI code.
System action
Command processing is aborted and the batch job terminates with return code 20.
Operator response
Contact your system programmer.
System programmer response
For some of the PPI error responses action can be taken to correct the error:
PPI receiver not defined
is usually due to an incorrect SERVER= specification.PPI interface not active
orNo active SSI
is usually due to no NetView SSI subsystem having started.
Most of the other reasons will require you to contact your IBM Support Center.
EVJ048I EXECUTING COMMAND
Explanation
Command processing is about to send a command to SA z/OS for processing.
System action
Processing continues.
Operator response
None.
System programmer response
None.
EVJ049E UNABLE TO SEND TO destination FOR source / EVJ049E UNABLE TO RECEIVE FROM destination
Explanation
PPI processing failed to send data from the source to the destination PPI receivers, or receive data from the destination PPI receiver.
- The variable source is the PPI Sender Id for this batch job.
- The variable destination is the PPI receiver name of the command server and is specified with the SERVER= parameter.
This message is followed by EVJ047I or INGPC028I to describe the problem in more detail.
System action
Processing is aborted and the batch job is terminated with return code 20.
Operator response
Contact your system programmer.
System programmer response
Refer to the information in the following EVJ047I message and take any appropriate action.
EVJ052E PPI INTERFACE FAILED TO CLOSE FOR source
Explanation
The PPI interface did not successfully close after command processing was completed.
- The variable source is both the PPI receiver name of the batch job and the job name of the batch job.
System action
Command processing is aborted and the batch job is terminated with return code 20.
Operator response
None.
System programmer response
Possibly no action. Check whether commands that were issued by the batch job executed correctly on the NetView by examining the NetView log.
EVJ053I BATCH COMMAND RECEIVED FROM userid JOBNAME jobname
Explanation
An OPC batch command has been received from a batch job and is to be executed on this NetView.
- The variable userid shows the user ID of the user who submitted the batch job.
- The variable jobname is the job name of the batch job.
System action
The command specified in message EVJ054I is processed.
Operator response
None.
System programmer response
None.
EVJ054I BATCH COMMAND IS command-text
Explanation
An OPC batch command has been received from a batch job and is to be executed on this NetView. This message logs the command to be executed.
- The variable command-text shows the batch command.
System action
The command is processed.
Operator response
None.
System programmer response
None.
EVJ055I PIPE PPI FOR receiver FAILED. RC=returncode - description
Explanation
A PIPE PPI command failed when attempting to communicate with the receiver.
- The variable returncode shows either the return code from the PIPE command or the return code from the PPI stage.
- The variable description shows a description of the error.
System action
The output from the current command received from the batch job will not be sent to the batch job. However, the command may have run successfully. The batch job will probably time out or produce some other error.
Operator response
For recoverable errors such as errors with the receiver, resubmit the batch job if you are allowed to rerun the failed batch job. For all other errors notify your system programmer.
System programmer response
Report the error to your service representative.
EVJ056E Command return code nn greater than MAXRC mm - Command Processing Aborted.
Explanation
A command sent to the SA z/OS agent for processing has executed and returned with a code greater that the maximum acceptable return code.
- The variable nn shows the return code from the command.
- The variable mm shows the maximum acceptable return code from the MAXRC parameter of the EVJRYCMD command.
System action
The batch interface will stop sending commands to the SA z/OS Agent and will terminate. The return code for the batch job step will be determined by the HIGHRC parameter.
Operator response
For recoverable errors, such as errors with the receiver, resubmit the batch job if you are allowed to rerun the failed batch job. For all other errors notify your system programmer.
System programmer response
If this is not a user-defined situation, report the fault to your service representative.
EVJ060I Executing command for ADID=name WSID=identifier OPNUM=nnn IATIME=timestamp >> command_text
Explanation
A command has been received from TWS and is to be executed on this NetView. This message logs the command to be executed. Note that the command might be truncated if it is too long.
- The variable name shows the application description identifier as defined in TWS.
- The variable identifier shows the workstation identifier.
- The variable nnn shows the TWS operation number.
- The variable timestamp shows the input arrival time as determined by TWS.
- The variable command_text shows the command.
System action
The command is processed.
Operator response
None.
System programmer response
None.
EVJ061I Command for ADID=name WSID=identifier OPNUM=nnn failed IATIME=timestamp RC=nn
Explanation
A command received via the TWS interface was executed but reported a non-zero return code. See the preceding message EVJ060I for the command in error.
- The variable name shows the application description identifier as defined in TWS.
- The variable identifier shows the workstation identifier.
- The variable nnn shows the TWS operation number.
- The variable timestamp shows the input arrival time as determined by TWS.
- The variable nn shows return code from the command.
System action
None.
Operator response
None.
System programmer response
None.
EVJ062I REQUEST for wsname adname opnum iatime purged
Explanation
While performing a configuration refresh, System automation detected that a deleted resource was involved in TWS request. Since the resource is no longer under control of SA z/OS the request is removed from the internal control structure.
- Variable wsname identifies the workstation name involved.
- Variable adname identifies the application name involved as defined in TWS
- Variable opnum specifies the operation number
- Variable iatime specifies the input arrival time assigned to the request.
System action
Processing continues.
Operator response
None.
EVJ063I Command for ADID=name WSID=identifier OPNUM=nnn IATIME=timestamp finished. ERRCODE=errcode
Explanation
A command received via the TWS interface was executed and finished. See the preceding message EVJ060I for command that was executed.
- The variable name shows the application description as defined in TWS.
- The variable identifier shows the workstation identifier.
- The variable nnn shows the TWS operation number.
- The variable timestamp shows the input arrival time as determined by TWS.
- The variable errcode shows the error code for the operation if the operation is in error, or the return code if the operation is complete.
System action
None.
Operator response
None.
System programmer response
None.
EVJ064E Operation with ADID=name WSID=identifier OPNUM=nnn is not unique
Explanation
While the OPCAPOST command has informed the workload scheduler environment that this operation has finished, it cannot determine it uniquely due to missing IDATE, ITIME, or both parameters. As a result, OPCAPOST cannot delete the final checking timer.
- The variable name shows the application description identifier as defined in workload scheduler.
- The variable identifier shows the workstation identifier.
- The variable nnn shows the workload scheduler operation number
System action
OPCAPOST found more than one operation running with fitting parameters and could not remove the scheduled checking timer.
Operator response
Access the NetView log, look for additional EVJ065E messages, and follow the operator responses.
System programmer response
To prevent such a situation in the future, look at your user written code and ensure that OPCAPOST invocations do include according IDATE and ITIME specifications in their parameter list to uniquely identify a running operation.
EVJ065E Found Operation: ADID=name WSID=identifier OPNUM=nnn IATIME=timestamp
Explanation
The shown operation has been detected as running besides other operations with the same ADID, WSID and OPNUM parameters. The input arrival time (IATIME) of each detected operation differs.
OPCAPOST has informed the workload scheduler environment that this operation has finished.
- The variable name shows the application description identifier as defined in the workload scheduler.
- The variable identifier shows the workstation identifier.
- The variable nnn shows the workload scheduler operation number.
- The variable timestamp shows the input arrival time as determined by the workload scheduler subsystem.
System action
System Automation shows this operation as running which could have been marked as completed or as in error within your workload scheduler environment.
Operator response
Consult each found EVJ065E message and check the status of the listed application within the workload scheduler environment.
If the according operation inside has been found as completed or as in error and if the max wait time has not expired yet, then you can issue the preceding OPCAPOST including the IDATE and ITIME parameters to exactly identify the operation.
Reissuing OPCAPOST will remove the timer for the final completion check within your automation environment.
System programmer response
To prevent such a situation in the future, look at your user written code and ensure that OPCAPOST invocations do include according IDATE and ITIME specifications in their parameter list to uniquely identify a running operation.
EVJ100I EVJ07001: ENTERING SA z/OS TWS/OPC EXIT
Explanation
TWS has now called the EVJ07001 exit.
System action
None.
Operator response
Information message.
System programmer response
Information message.
Destination
None.
EVJ101I EVJ07001: DATA SENT=data
Explanation
This message logs the data sent to NetView across the NetView PPI in the system log.
System action
None.
Operator response
Information message.
System programmer response
Information message.
Destination
Data passed.
EVJ102I EVJ07001: PPI REQUEST nn FAILED, RC=rc
Explanation
EVJ07001 was unable to complete a NetView PPI request. See the NetView PPI manual for more information on this request type and return code.
System action
TWS operation will be set to E status.
Operator response
Review error message in log.
System programmer response
Review error message in log.
Destination
Request type and return code.
EVJ103I EVJ07001: GETMAIN FOR WORKAREA FAILED
Explanation
EVJ07001 was unable to do a GETMAIN for work area storage.
System action
EVJ07001 will put the TWS operation in E status.
Operator response
Report the problem to your system programmer.
System programmer response
Review NetView storage allocation and usage.
Destination
None.
EVJ104I EVJ07001: OPC BAD OPERDESC: data
Explanation
EVJ07001 has found the contents of the operation description field to be invalid. Message EVJ105I will list the actual error data.
System action
EVJ07001 will put the TWS operation in E status.
Operator response
Inform TWS Scheduler of possible definition error.
System programmer response
None.
Destination
TWS application name.
EVJ105I EVJ07001: OPC DATA data
Explanation
EVJ07001 has found this data to be invalid.
System action
EVJ07001 will put the TWS operation in E status.
Operator response
Inform TWS Scheduler of possible definition error.
System programmer response
None.
Destination
Data.
EVJ106I modname1: modname2 STATUS UPDATE FAILED, RC=rc
Explanation
The module listed was unable to update operations status using DRK/EQQUSINT.
System action
WTO error message is issued.
Operator response
Inform TWS schedulers and system programmers.
System programmer response
Review system and TWS/OPC message logs.
Destination
Issuing module and status update module.
EVJ107I EVJ07001: TWS/OPC FEATURE EXIT ENDED
Explanation
EVJ07001 has successfully ended.
System action
None.
Operator response
Information message.
System programmer response
Information message.
Destination
None.
EVJ108I module-name UNABLE TO LOAD MODULE CNMCNETV
Explanation
This message is issued from the TWS status change exit, (EQQUX007/DRKUX007), when it cannot load the NetView PPI interface.
System action
Processing for this request halts. The operation will be posted in error with a return code of UNTV.
Operator response
Notify your system programmer.
System programmer response
This message most likely indicates an installation error. You must make the NetView PPI module accessible to TWS, either by STEPLIB or putting the NetView load library, CNMLINK, in LINKLST.
Destination
Issuing module name.
EVJ109I EVJ07001: LEAVING SA Z/OS TWS/OPC EXIT
Explanation
EVJ07001 has successfully ended.
Operator response
Information message.
System programmer response
Information message.
Destination
Module name and successful command name.
EVJ110I modulename UNABLE TO LOAD MODULE target-module-name
Explanation
This message is issued from an TWS command processor, which is unable to find or load an TWS interface module.
System action
Processing for this request halts.
Operator response
Notify your system programmer.
System programmer response
This message most likely indicates an installation error. You must make the TWS interface module accessible to NetView, either by STEPLIB (preferred) or by putting the TWS load library in LINKLST.
Destination
Issuing module name and target module name.
EVJ120I applid iatime opnum job status wsname errcode abcode usrcode job# stepname
Explanation
A TWS operation has been put into TWS error status or has been reset from TWS error status. This causes a Status Display Facility (SDF) update. For an operation changing to error status the update will add an entry to SDF, while an operation changing from error status will remove an entry from SDF. SDF entries are added to the 'OPC Automation Application in Error' panel (OPCERR). When enabled, alerting for the specified event notification targets will occur.
- The variable applid shows the TWS application name.
- The variable iatime shows the TWS input arrival time.
- The variable opnum shows the TWS operation number.
- The variable job shows the TWS job name.
- The variable status shows the TWS status.
- The variable wsname shows the TWS workstation for this operation.
- The variable errcode shows the TWS error code.
- The variable abcode shows the TWS abend code.
- The variable usrcode shows the TWS user code.
- The variable job# shows the TWS job number.
- The variable stepname shows the TWS job's stepname.
System action
SDF is updated according to the data displayed in the message and when enabled, an alert for event notification targets will be generated.
Operator response
None.
System programmer response
None.
EVJ121I Application jobname opno NOT RESET BECAUSE TIME LIMIT EXCEEDED
Explanation
This operation was found to be in error status in OPC with error code, UNTV, indicating that the NetView interface was unavailable at the time it came READY. Now that the interface is available, the status was not reset because more time has elapsed since the failure than is permitted by the OPRESET value in the control file (see ENVIRON OPCAO).
System action
Operation remains in error status.
Operator response
Manually reset operation when appropriate. OPCACMD may be used to do this.
System programmer response
Determine whether the OPRESET value should be increased.
Destination
Application name, Job name, Operation number.
EVJ122E UNKNOWN TWS API SEGMENT segment ENCOUNTERED
Explanation
When the INGTWS command is decoding data returned from TWS via the API, an unknown segment name was encountered.
- The variable segment shows the name of the segment that is unknown to the command.
System action
Data from the TWS API is not successfully decoded. The command will present data that has been decoded up to the point of the failure.
Operator response
Notify your system programmer.
System programmer response
Report the error to your service representative.
EVJ123I [DEFAULT SAFE|UPDATE PARAMETER] INVALID MODIFICATION PARAMETERS FOLLOW:
Explanation
For an INGTWS REQ=MOD request an invalid update parameter was encountered that the command could not process. The source of the parameter in error is either the Default Safe for the DEFAULT SAFE version of the message or the UPDATE command parameter for the UPDATE PARAMETER version of the message. Message EVJ124I follows this message with a list of up to five parameter names that are in error.
System action
Processing stops.
Operator response
Correct the incorrect parameter and reissue the command.
System programmer response
None.
EVJ124I parm1 parm2 parm3 parm4 parm5
Explanation
This message follows message EVJ123I and specifies up to five parameter names that are in error.
System action
None.
Operator response
Correct the incorrect parameter/s and reissue the command.
System programmer response
None.
EVJ125I subsystem IS NOT AN ACTIVE CONTROLLER OR A TRACKER
Explanation
This message is issued when INGOPC cannot resolve the resource specification to an active controller or to an available tracker.
System action
None.
Operator response
Correct the incorrect parameter (or parameters) and reissue the command. Make sure that the resource specification will resolve to an active Available Controller or an Available Tracker.
System programmer response
None.
EVJ201I EVJTOPPI: TASK IS ACTIVE
Explanation
NetView optional subtask initialization has completed successfully.
System action
None.
Operator response
Information message.
System programmer response
Information message.
Destination
None.
EVJ202I EVJTOPPI: PPI TO EVJTOPPI INITIALIZED
Explanation
NetView optional subtask has initialized its NetView PPI queue.
System action
None.
Operator response
Information message.
System programmer response
Information message.
Destination
None.
EVJ203I EVJTOPPI: PPI TO EVJTOPPI DEACTIVATED
Explanation
NetView optional subtask has deactivated the NetView PPI queue.
System action
None.
Operator response
Information message.
System programmer response
Information message.
Destination
None.
EVJ204I EVJTOPPI: TASK IS TERMINATED
Explanation
NetView optional subtask has terminated successfully.
System action
None.
Operator response
Information message.
System programmer response
Information message.
Destination
None.
EVJ205E EVJTOPPI: PPI REQUEST nn FAILED, RC=rc
Explanation
EVJTOPPI was unable to complete a NetView PPI request. Refer to the NetView Application Programming Guide: PPI for more information on the request type and return code.
System action
None.
Operator response
Notify your system programmer.
System programmer response
Review log for messages that may indicate the reason for the failure. A possible reason is that NetView is being shutdown.
Destination
Request type and return code.
EVJ206I EVJTOPPI: PPI DATA FROM EVJTOPPI DISCARDED
Explanation
EVJTOPPI received request data from a non-OPC subsystem. The data is logged in the NetView log, but is not passed to EVJESPVY.
System action
None.
Operator response
Informational. Review message EVJ214I for data.
System programmer response
Informational.
Destination
None.
EVJ207I EVJTOPPI: DSIFRE FAILED FOR USER STORAGE
Explanation
EVJTOPPI was not able to FREE user storage before terminating.
System action
None.
Operator response
Report problem to system programmer.
System programmer response
Review error.
Destination
None.
EVJ208I EVJTOPPI: DSIFRE FAILED FOR QUEUED STORAGE
Explanation
EVJTOPPI was not able to FREE queued storage before terminating.
System action
None.
Operator response
Report problem to system programmer.
System programmer response
Review error.
Destination
None.
EVJ209I EVJTOPPI: DSIGET FAILED FOR USER STORAGE
Explanation
EVJTOPPI was not able to GET user storage at initialization.
System action
None.
Operator response
Report problem to system programmer.
System programmer response
Review NetView storage allocation and utilization.
Destination
None.
EVJ210I EVJTOPPI: DSILCS FAILED TRYING TO GET A SWB
Explanation
EVJTOPPI was not able to GET a service work block.
System action
None.
Operator response
Report problem to system programmer.
System programmer response
Review NetView storage allocation and utilization.
Destination
None.
EVJ211I EVJTOPPI: ENQ ERROR
Explanation
EVJTOPPI was not able to perform an ENQUEUE.
System action
None.
Operator response
Report problem to system programmer.
System programmer response
Check for multiple EVJTOPPI tasks or possible deadlock condition.
Destination
None.
EVJ212I EVJTOPPI: DEQ ERROR
Explanation
EVJTOPPI was not able to perform a dequeue.
System action
None.
Operator response
Report problem to system programmer.
System programmer response
Check for multiple EVJTOPPI tasks started, or a deadlock condition.
Destination
None.
EVJ213I EVJTOPPI: DSILCS FAILED TRYING TO FREE SWB
Explanation
EVJTOPPI was not able to FREE a service work block.
System action
None.
Operator response
Report problem to system programmer.
System programmer response
Contact support center.
Destination
None.
EVJ214I EVJTOPPI: xxxxxxxxxxxxxxxxxxxxxxxxx
Explanation
This message is sent to the NetView log to document the discarded data.
System action
None.
Operator response
Informational.
System programmer response
Informational.
Destination
Data.
EVJ300I EVJSAOPS: DRK/EQQUSINT POST WAS SUCCESSFUL
Explanation
Post to OPC using DRK/EQQUSINT was successful.
System action
None.
Operator response
Informational.
System programmer response
Informational.
Destination
None.
EVJ302I cmdname: INVALID KEYWORD SUPPLIED
Explanation
Invalid KEYWORD was issued when invoking this command. Message EVJ303I will follow listing the KEYWORD and DATA in error.
Operator response
Correct parameters used to invoke the command.
System programmer response
Correct the command and retry.
Destination
Command name.
EVJ303I cmdname: KEYWORD ERROR, KEYWORD(keyword) DATA(data)
Explanation
This message gives the keywords and data that are invalid when this command was invoked.
Operator response
Review parameters used to invoke the command.
System programmer response
Modify parameters accordingly.
Destination
Command name, keyword and data.
EVJ410I ADID JOBNAME WS OPNO S ERRC IA OPTEXT
Explanation
This is the first line of a multiple-line message. It displays the titles for message EVJ411I.
EVJ411I applid jobname workstation opid status errcode IA_time text.
Explanation
This is the second line of a multiple-line message. It displays the corresponding information from message EVJ410.
EVJ412I END OF REQUEST.
Explanation
This message indicates the end of the data.
EVJ413I UNABLE TO FIND DATA FOR REQUESTED LIST
Explanation
This message is issued from OPCALIST or OPCACMD and indicates that no application or operation in the current plan meets the combination of input parameters specified.
System action
Processing for this request halts.
Operator response
Correct the input to the OPCALIST command or the OPCACMD panel. If it is not obvious which parameter is error specify fewer parameters and issue the command again, so that OPC may return a list of valid application occurrences in the current plan. If there are none go to the OPC dialog under ISPF and add an occurrence.
System programmer response
None.
Destination
None.
EVJ424E COULD NOT LOCATE OPC CONTROLLER - reason
Explanation
The OPC Controller as defined in the OPCA PCS automation control file statement could not be located in either the local system or any of the systems in the local sysplex.
The reason variable (optional) shows the reason code.
System action
Processing is terminated.
Operator response
Investigate the cause of the failure. Further diagnostic messages may be available in the NetView log. Possible causes include:
- An error in the OPCA PCS statement in the automation control file.
- The OPCA PCS defines the controller to be running on another system.
- No OPC controller is running (UP status in SA z/OS) where specified.
EVJ425I NO SRSTAT ENTRY FOUND IN OPCA PCS DEFINITION FOR OPC AUTOMATION.
Explanation
OPCA PCS,
SRSTAT=YES|NO|ALLSystem action
None.
Operator response
Report to your system programmer that the OPCA PCS statement in the automation control file for setting special resources status was not defined. This entry allows TWS Automation to set OPC special resources for the named job name in the OPCA OPCSRSTAT definition.
System programmer response
Refer to IBM Z® System Automation Workload Scheduler Programmer's Reference and Operator's Guide for further information.
EVJ430I ADID JOBNAME WS OPNO S ERRC IA OPTEXT
Explanation
- ADID
- OPC Application ID
- JOBNAME
- MVS Job Name
- WS
- OPC Workstation
- OPNO
- OPC Operation Number
- S
- OPC Status
- ERRC
- OPC Error Return Code
- IA
- OPC Input Arrival Time
- OPTEXT
- OPC Operations Text
EVJ431E adid jobname ws opno s errc ia optext
Explanation
This is the continuation of a multiple-line message begun with EVJ430I.
Destination
- adid
- OPC Application ID
- jobname
- MVS Job Name
- ws
- OPC Workstation
- opno
- OPC Operation Number
- s
- OPC Status
- errc
- OPC Error Return Code
- ia
- OPC Input Arrival Time
- optext
- OPC Operations Text
EVJ440I date day WORK|FREE.
Explanation
This message tells you whether today is a work day or a free day in the OPC calendar. The date is
shown in the format mm/dd/yyyy.