The specified command could not obtain a work area.
The command terminates.
Increase the region size of the address space by a minimum of nnnK. Alternatively, use the DATA minor of SEEK to decrease the work size area by nnnK.
The SEEK SRB to collect data failed to complete its task because the data area it needed was small.
None.
Use the DATA minor of SEEK to increase the work area.
The specified device either was not found in the UCB lookup table, or was found to be marked offline.
The command stops processing.
Specify a valid volume or vary volume online.
The specified control block (ASCB, TCB, DSAB, JFCB, or JFCX) failed validation in the SRB routine for DATA minor of SEEK.
DATA minor of SEEK does not collect dataset information for the address space which has failed validation.
This is an informational message only.
The SRB to collect data failed to complete its task and returned an invalid return code to the user.
The command stops processing.
Call IBM Software Support to report a possible problem.
An invalid parameter was encountered on the SEEK or DATA command line.
The command stops processing.
Check the syntax and re specify with the correct parameter.
The volser or device address required by SEEK has not been specified.
None.
Specify the Volser or device address and reissue the command.
A seek operation was not observed on the sample number specified in the ITEM parameter, or no seek operations were observed for the specified jobname.
No detail data items are displayed.
This is an informational message only.
The specified sample interval must be between 5 and 500 milliseconds.
Processing continues with the default of 5 milliseconds assumed.
This is an informational message only.
The specified sample count was greater than 100.
Processing continues with the maximum of 1000 samples assumed.
This is an informational message only.
The OBVTAM support program, version nnn, is initializing.
OBVTAM processing continues.
None.
The OPEN macro for the VTAM® ACB was successful.
Initialization processing continues.
None. OBVTAM is ready to accept a log on.
OBVTAM attempted to open an ACB to VTAM with the identifier cccccccc. The attempt failed for the reason specified.
If the reason is a condition that can be retried (for example, if the network APPL is inactive at the time OBVTAM attempts access), OBVTAM retries the operation for up to 30 minutes. Otherwise, the OBVTAM network APPL stops processing.
The reasons that appear follow. Take the appropriate action for the reason that appears with this message.
Another MVS job or started task has the OBVTAM network APPL allocated.
The OBVTAM stops processing.
Contact the VTAM systems programmer at your installation.
OBVTAM attempted to open an ACB to VTAM for an network APPL that was inactive.
OBVTAM attempts access again for up to 30 minutes.
Activate the network APPL.
VTAM has not completed recovery processing after an OBVTAM failure.
Once VTAM processing is complete, the network APPL becomes available to OBVTAM automatically.
None. This is an informational message only.
The OBVTAM APPL was not defined to VTAM.
OBVTAM terminates.
Contact the VTAM systems programmer at your installation to define an APPL to VTAM for OBVTAM. Start the OBVTAM again.
The error code associated with the VTAM OPEN ACB process was nn.
If the error code is 14, OBVTAM retries the operation for up to 30 minutes. Otherwise, OBVTAM stops processing.
Write down the VTAM error code and contact the VTAM systems programmer at your installation, or contact IBM Software Support.
OBVTAM was started before VTAM.
OBVTAM attempts to open the network APPL for up to 30 minutes.
Start VTAM, then restart OBVTAM.
The OBVTAM start parameter included SWAP=N, but OBVTAM cannot mark itself non-swappable without APF authorization.
OBVTAM processing continues, but OBVTAM remains swappable.
If you want OBVTAM to be non-swappable, restart it from an APF-authorized library.
Secondary Logical Unit cccccccc tried to establish a session using a VTAM Logmode that specifies an FM/TS session profile of nnnn. OBVTAM supports FM/TS profiles 0303 and 0202 only.
OBVTAM rejects the session request from SLU ccccccc.
Select a VTAM Logmode which specifies a supported FM/TS profile, or select an alternate device.
A VTAM session was established between OBVTAM (network identifier aaaaaaaa) and Secondary Logical Unit bbbbbbbb.
OBVTAM processing continues; initialization starts for an OMEGAMON session.
None.
The initiation of a session between OBVTAM (network identifier aaaaaaaa) and Secondary Logical Unit bbbbbbbb failed. These are the VTAM status values associated with the request:
OBVTAM rejects the session request from SLU bbbbbbbb.
Refer the VTAM status information to your Network Support group or contact IBM Software Support for assistance.