IA0217 IA COLLECTION TASK TIMES OUT AFTER n MINUTES

Explanation

Informs the user of the current time-out interval. If the time-out facility has been turned off, the message is IA COLLECTION TASK WILL NOT TIME OUT.

System action

The IATO command is accepted.

User response

None.

IA0301 PERFORMANCE GROUP OPERANDS UNACCEPTABLE IN GOAL MODE

Explanation

Performance group information is not available under the Work Load Manager goal mode.

System action

The command stops.

User response

Enter the correct the command.

IN0004 THE KEYWORD FLAGGED ABOVE IS UNKNOWN

Explanation

A keyword operand was misspelled or is not valid on this command.

System action

The command does not execute.

User response

Enter the correct the command.

IN0005 PARAMETER WAS EXPECTED BUT NOT FOUND

Explanation

A keyword with a parameter list was specified, but the parameter list did not contain enough parameters.

System action

The command does not execute.

User response

Enter the correct the command.

IN0006 THIS PARAMETER MUST BE NUMERIC

Explanation

A parameter was specified which must be numeric but is not.

System action

The command does not execute.

User response

Enter the correct the command.

IN0007 ‘)’ MISSING AFTER FIRST PARAMETER

Explanation

A ‘)’ was expected after the first parameter and was not found.

System action

The command does not execute.

User response

Correct the command format and retry.

IN0050 datasetname FAILED TO ALLOCATE

Explanation

An error occurred during dynamic allocation of the dataset name specified in the MLIB DSN list.

System action

The command continues if there are other dataset names in the MLIB DSN list.

User response

Check the reason for the dynamic allocation error and correct accordingly. Message IN0051 might accompany this message.

IN0051 DAIR CODE = rc

Explanation

The Dynamic Allocation Interface Routine (DAIR) return code is displayed.

System action

Same as message IN0050.

User response

Same as message IN0050.

IN0060 datasetname FAILS MLIB REQUIREMENTS

Explanation

The dataset failed the MLIB requirement because it neither has a Format 1 DSCB nor is in a load module format. Message IN0061 or IN0062 gives more information on the error.

System action

The command continues if there are other dataset names in the MLIB DSN list.

User response

Make sure the correct data set name was specified.

IN0061 DATASET IS NOT LOAD MODULE FORMAT

Explanation

The MLIB failure was due to the data set not being in a load module format.

System action

The command continues if there are other data set names in the MLIB DSN list.

User response

Only load data sets can be specified on the MLIB command.

IN0062 FORMAT1 DSCB COULD NOT BE LOCATED

Explanation

The dataset specified in message IN0060 was not found.

System action

The command continues if there are other data set names in the MLIB DSN list.

User response

Make sure that the data set exists on the volume as indicated by the system catalog and retry the command.

IN0070 datasetname FAILED TO OPEN

Explanation

The OPEN failed for the data set.

System action

The command continues if there are other data set names in the MLIB DSN list.

User response

Make sure that OMEGAMON is authorized to use the specified data set.

IN0080 datasetname IS NOT OPEN

Explanation

OMEGAMON tried to close a data set that was not open.

System action

CLOSE processing continues for remaining data sets.

User response

Call IBM Software Support for assistance.

IN0081 datasetname FAILED TO CLOSE

Explanation

The data set cannot be closed.

System action

CLOSE processing continues for the remaining data sets.

User response

Investigate why the data set failed to close. If necessary, call IBM Software Support for assistance.

IN0082 datasetname FAILED TO DEALLOCATE

Explanation

The data set cannot be deallocated.

System action

Deallocate processing continues for remaining data sets.

User response

Investigate why the data set failed to deallocate by examining the accompanying DAIR code in message IN0083.

IN0083 DAIR CODE = rc

Explanation

The Dynamic Allocation Interface Routine (DAIR) return code is displayed with message IN0082.

System action

See message IN0082.

User response

Refer to the appropriate IBM® manual for a description of the return codes.

IN0090 ADD AND DEL MUST NOT BE ISSUED TOGETHER

Explanation

The ADD and DEL parameters cannot be issued together in the same MLIB command.

System action

The commands do not execute.

User response

Issue ADD and DEL separately.

IN0091 datasetname IS NOT IN THE MLIB DSN LIST

Explanation

The data set specified with the delete option of the MLIB minor of INSP was not found in the MLIB list because it was never added or was already deleted.

System action

The operation is ignored.

User response

Specify the correct data set name for the delete.

IN0092 PREVIOUS LINE WAS TRUNCATED

Explanation

The previous display line has been truncated because the line length was exceeded.

System action

None.

User response

None.

IN0100 ccccccc HAS A HIGHER PRIORITY THAN OMEGAMON

Explanation

The address space dispatching priority of job ccccccc, which is being monitored by INSP, is running at a higher priority than OMEGAMON. This is the jobname specified by the JOB( ) keyword.

System action

INSP attempts to take samples, but will probably detect very little activity in the monitored address space. Any results are incorrect.

User response

Run OMEGAMON as a performance group which has a higher priority than the address space being monitored.

IN0101 ccccccc IS NO LONGER RUNNING

Explanation

INSP was monitoring an address space when the jobname ccccccc changed. The ccccccc value is the name specified by the JOB( ) keyword.

System action

Sampling stops.

User response

If you want more data, rerun the job and use a shorter sampling period.

IN0102 START INVALID, ALREADY SAMPLING

Explanation

The START keyword was specified on the INSP command when sampling of the target address space was already in progress.

System action

The START keyword is ignored.

User response

None required.

IN0103 STOP INVALID, NOT SAMPLING

Explanation

The STOP keyword was specified on the INSP command when sampling of the target address space was not in progress.

System action

The STOP keyword is ignored.

User response

None required.

IN0104 ATTACH FAILED

Explanation

This is an internal error message.

System action

Sampling does not start.

User response

Call IBM Software Support for assistance.

IN0105 ccccccc NOT FOUND

Explanation

No job with the name ccccccc specified is currently active. The jobname is the name specified by the JOB( ) keyword.

System action

The new jobname specification is not used.

User response

Use the JOB( ) keyword to specify the name of a running job. If necessary, use OMEGAMON commands such as ALLJ to determine a valid jobname.

IN0106 SAMPLER TASK HAS ABENDED

Explanation

This is an internal error message.

System action

Sampling stops and diagnostic information appears.

User response

Record the diagnostic information and call IBM Software Support.

IN0900 $GMEM FAILED FOR INSP WORKAREA

Explanation

OMEGAMON was unable to obtain memory for the INSP work area.

System action

The command does not execute.

User response

Increase the OMEGAMON region size to correct the problem.

IN0901 RETURN CODE rc FROM OMPBM INITIALIZATION

Explanation

An error occurred during INSP initialization.

System action

The command does not execute.

User response

Call IBM Software Support for assistance.

IN0902 INSPECT REQUIRES DEXAN

Explanation

To run INSP, the DEXAN® product is required.

System action

The command does not execute.

User response

None.

IN0903 LOAD MACRO FAILED FOR OMPBM WITH ABEND=nnn

Explanation

INSP module OMPBM could not be loaded.

System action

The command does not execute.

User response

Refer to the IBM system codes manual for an explanation of the abend code.

IN0904 INSPECT ERROR CODE nn

Explanation

An internal error occurred on the INSP command. The error code is nn.

System action

The command does not execute.

User response

Call IBM Software Support for assistance.

LSCX* (message text varies)

Explanation

SAS/C generates messages that have LSCX prefixes.

System action

None.

User response

Contact IBM Software Support.