ChangeMan ZMF Message Descriptions

ChangeMan ZMF messages and their meanings are listed below in ascending numeric order.

Note

In the message descriptions in this book, where a value is shown between {and} then that value represents a variable, and will be lower case italic. Example: CMN_208I CMN Member {member} not found. The {and} characters are not displayed in the message.

ZMF Server Messages

These messages are issued by the ZMF server programs and are displayed at the SERPRINT sysout data set in the SERNET started task.

Tip

The fourth character of the message number is the subsystem ID of the started task where the message is displayed.

`CMN_000I` `CMNENTFY Error - Port or IP address not found`

Explanation: No port or IP address found and the CMNENTFY has failed. Refer also to message CMN_004I.

`CMN_000I` `CMNENTFY Error - Event Notification Task Exiting`

Explanation: This message advises that the Event Notification Task is exiting.

`CMN_004I` `CMNENTFY Port {``nnnnnn``} IP address {``iiiiii``}`

Explanation: The event notification task has started and is using port nnnnnn and IP address iiiiii. If these are blank, there is no port or IP address in use and the startup has failed.

`CMN_204I` `CMN Unable to allocate JCL file to submit {``site position``}`

Explanation: The ZMF scheduler is unable to find the X node data set for a site. The site position is the position of the site in the query package Site Information table. This message is paired with message CMN_303I, which displays the package name.

Solution: Recover the missing X node data set. The scheduler automatically submits the job on the next cycle of the scheduler interval.

`CMN_208I` `CMN Member {``member``} not found`

Explanation: The ZMF scheduler is unable to find the indicated member in the X node data set for a change package. This message is paired with message CMN_303I, which displays the package name.

Solution: Recover the member that is missing from the X node data set. The scheduler automatically submits the job on the next cycle of the scheduler interval.

`CMN_300` `Attach Failure`

Explanation: Attempt to manually start a ZMF subtask with the ATTACH modify command has failed.

Solution: Ensure that the files required by the subtask are available (i.e. the impact analysis LSD for IADS, the staging versions masters for SSV.)

`CMN_300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=ELDS,@TCA={``address``},@TCB={``address``}`

Explanation: Component history LDS subtask is successfully attached. This message is displayed at ZMF startup.

`CMN_300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=IADS,@TCA={``address``},@TCB={``address``}`

Explanation: Impact analysis LDS subtask is successfully attached. This message is displayed at ZMF startup or when the impact analysis subtask is manually attached using the ATTACH modify command.

`CMN_300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=INFO,@TCA={``address``},@TCB={``address``}`

Explanation: INFO interface subtask is successfully attached. This message is displayed at ZMF startup or when the INFO interface subtask is manually attached using the ATTACH modify command.

`CMN_300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=SERVDLAY,@TCA={``address``},@TCB={``address``}`

Explanation: Delay processing subtask is successfully attached. This message is displayed at ZMF startup.

`CMN_300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=SSV,@TCA={``address``},@TCB={``address``}`

Explanation: Staging version subtask is successfully attached. This message is displayed at ZMF startup and when the staging versions subtask is manually attached using the ATTACH modify command.

`CMN_300I CMNSTART Initialization in progress; @TCA={``address``}`

Explanation: ZMF startup has begun.

`CMN_301I` `Loading CMN services; @ADR={``address``}`

Explanation: CMN services loading at {address}.

`CMN_302I` `CMNSTART ERO has been disabled Server started with reusable ASID`

Explanation: ERO is licensed, but it is disabled on this ZMF instance because the SERNET started task was started with z/OS START parameter REUSASID=YES. ERO calls DB2, which is not compatible with reusable ASIDs, so ERO is not compatible with reusable ASIDs.

Solution: If you want to use ERO on this ZMF instance, restart the SERNET started task without START command parameter REUSASID=YES.

`CMN_303I` `CMNSTART Initialization Complete`

Explanation: SERVER has called CMNSTART with the WAKEUP function (once each minute), and startup functions are complete; CMNDELAY is finished, it has opened the started task to external logon, and it has released the ENQ resource for the delay file.

Note: Because subtask SERVDLAY processes asynchronously, this message may be displayed up to one minute after messages print for other activities that started after CMNDELAY finished.

Solution: No action required.

`CMN_303I Scheduled job member submitted {``member``} {``package``}`

Explanation: This message is displayed before the ZMF scheduler submits the indicated member in the X node dataset for the indicated change package. Solution: No action required.

`CMN_304I` `CMNSERVR - Calendar shifting problem`

Explanation: Displayed at startup when ZMF attempts to increment the peg date to the current date. The peg date is the last date on which the task was active. There are two possible causes:

The “last date active” in the package master global record is corrupt or missing.
The increment value is invalid. This could occur if the system IPL was given the wrong date causing the increment to be too large or too small.

Solution: Ensure that:

Package master VSAM file is not corrupt
Package master VSAM file is the correct one for this ZMF instance
Package master VSAM file has a valid global record
Machine IPL date is greater than the last peg date

`CMN_304W` `CMNSTART Calendar shifting warning {``sitename``} {``date``}`

`CMN_305I` `CMNSTART Detach U=CMNSTART,F1=DETACH,F2={``subtask``},@TCA={``address``}, @TCB={``address``}`

Explanation: A DETACH modify command is received and the process of detaching the subtask specified in F2= is initiated. This message is displayed at ZMF shutdown or when the subtask is manually detached using the DETACH modify command.

Solution: Information only, no action is required.

`CMN_306E` `CMNSTART Calendar shifting error`

Explanation: Internal error.

Solution: Contact Micro Focus Customer Care with details.

`CMN_308I` `CMNSTART ZMF version 7.1.3`

Explanation: Displays the v.r.mp for the ZMF application running under SERNET, where:

v = Version level
r = Release level
m = Maintenance level
p = Patch level (alpha)

Example: 7.1.2a is ZMF 7.1.2.01.

Solution: Information only. Use this information when reporting an issue to Micro Focus Customer Care.

`CMN_309I` `CMNSTART Invalid command syntax, please reenter.`

`CMN_310E` `CMNSTART CMNSTART Log full or global record problem - abend 310.`

`CMN_311I` `CMNSTART Unrecognized command, please reenter.`

`CMN_313I` `CMNSTART Termination Complete`

Explanation: ZMF has shut down successfully. SERNET is still terminating.

Solution: Information only, no action is required.

`CMN_315I` `CMNSTART IADS Task Attached`

Explanation: A manual start of the impact analysis subtask with the ATTACH modify command is successful.

Solution: Information only, no action is required.

`CMN_315I CMNSTART Reject; IADS Already Attached`

Explanation: You have attempted to manually start a ZMF subtask with the ATTACH modify command when the subtask is already attached.

`CMN_315I CMNSTART HLLX address space is already active, no action taken.`

Explanation: This message is issued when there is an attempt to start the HLLX address space with command "/F {server},CMN,ATTACH,HLLX" where {server} is the ZMF STC name, but the HLLX address space is already active.

`CMN_316I` `CMNSTART IADS Task Detached`

Explanation: A manual detach of the impact analysis LDS with the DETACH modify command is successful.

`CMN_317I` `CMNSTART All scheduled jobs held`

Explanation: Information.

`CMN_340I CMNSTART Loading active exits`

Explanation: Exits that have been enabled by the customer are being loaded. This message is displayed at ZMF startup.

Note: Batch exits like CMNEX101 and CMNEX103 are not listed because they are not loaded.

Solution: Information only, no action is required.

`CMN_340I {``exit name``} loaded`

Explanation: Information, specified exit has been loaded.

`CMN_350I` `CMNSTART * Warning * DB2 CAF interface module could not be loaded - DSNALI.`

Explanation: You are licensed for the DB2 Option so this check is being performed.

Solution: You can either ignore the warning or add the DB2 load libraries to the concatenation to suppress the message.

`CMN_350I CMNSTART * Warning * Missing DD Name = {``ddname``}`

Explanation: A DD statement normally included in a started procedure for ZMF is missing. Solution: Add the missing DD statement to the started procedure.

`CMN_381E` `Scheduling error detected in subsys({``subsys``}) for {``function``}`

Explanation: This message is displayed when a scheduler function has failed. There is a another message in SERPRINT for the ZMF instance that indicates the specific failure. IMPORTANT! This message is also written to the console log (WTO) when the error will interfere with the scheduled installation of a change package.

Important! This message is also written to the console log (WTO) when the error will interfere with the scheduled installation of a change package.

Solution: Find the message in SERPRINT that described the error and correct the problem.

`CMN_381E Scheduled job member submitted {``member``} {``package``}`

Explanation: This message is displayed before the ZMF scheduler submits the indicated member in the X node dataset for the indicated change package. Solution: No action required.

`CMN_381E I/O error detected at CMNSCHED+{``offset``}`

Explanation: This message is issued if CMNSCHED encounters an I/O error trying to read package schedule records on the package master. Note:

Solution: Manually submit the installation job. If this error occurs repeatedly, contact Micro Focus Customer Care

`CMN_385I` `CMNINFVS Attempting INFO API Connect CMNINFAP (MVS-6.1.0) 20100517 19.17 Copyright`

`CMN_385I CMNSSV Attempting SSV initialization CMNSSV (MVS-7.1.0) 20100517 16.31`

`CMN_386I` `CMNINFVS Unable to load BLGYSRVR - INFO API`

`CMN_387I` `CMNINFVS INFO Connection disabled`

`CMN_387I CMNSSV SSV initialization failed`

`CMN_387I CMNSSV SSV terminated`

`CMN_388I CMNSSV SSV initialization complete`

`CMN_391I` `CMNIAM00 Attempting to open the I/A Dataspace.`

Explanation: Open for the impact analysis data space has been initiated. This message is displayed at ZMF startup or when the impact analysis subtask is started manually with the ATTACH modify command.

Solution: Information only, no action is required.

`CMN_392I` `CMNIAM00 I/A Dataspace OPEN, LDS {``dsn``}`

Explanation: The impact analysis data space has been opened successfully, populated from the impact analysis VSAM LDS dataset, and is available through the started task. This message is displayed at ZMF startup or when the impact analysis subtask is started manually with the ATTACH modify command. See message CMN_391.

`CMN_393I` `CMNIAM00 I/A Dataspace open failed, rc {``return code``}, rsn {``reason code``}.`

Explanation: An attempt to open the impact analysis data space has been unsuccessful. This message is displayed at ZMF startup or when the impact analysis subtask is started manually with the ATTACH modify command. See message CMN_391I.

Solution: Ensure that the impact analysis LDS is defined and either initialized or populated. After you have resolved the problem, you must SHUTDOWN and START the started task.

`CMN_394I` `CMNIAM00 Closing the I/A Dataspace.`

Explanation: The process of closing the impact analysis data space has been initiated. This message is issued at ZMF shutdown or when the impact analysis subtask is manually detached with the DETACH modify command.

Solution: Information only, no action is required.

`CMN_395I` `CMNIAM00 The I/A Dataspace is now offline.`

Explanation: The process of closing the impact analysis data space and detaching the impact analysis subtask is complete. The impact analysis LDS is available for offline processing. This message is issued at ZMF shutdown or when the impact analysis subtask is manually detached with the DETACH modify command. See message CMN_394I.

Solution: Information only, no action is required.

`CMN_400E` `CMNSTART Invalid Major Function= {``function``}`

Explanation: Internal message.

Solution: Contact Micro Focus Customer Care.

`CMN_402A` `ATTENTION I/A dsp full | ATTENTION The impact analysis dataspace is full, reorganization is required.`

Explanation: The impact analysis data space is full, and all freespace is used.

Solution: DETACH the IADS subtask or shut down the ZMF instance, reorganize the impact analysis LDS, and ATTACH the IADS subtask or start the ZMF instance again.

Note

If you are using XML Services to perform mass deletes of impact analysis relationships, use the FREEPCT= execution parameter with program CMNIAIN0 to increase freespace and increase the proportion of freelist rows.

`CMN_403A` `I/A dsp full | The current I/A operation must be terminated, ABENDU0937.`

Explanation: The impact analysis data space is full, and all freespace is used.

Solution: An accompanying diagnostic message should describe the problem. Execute the solution described for that message.

`CMN_460I` `CMNDELAY - START of processing`

Explanation: The delay processing subtask has started program CMNDELAY.

Solution: No action required.

`CMN_461I` `CMNDELAY - END of processing {``trancnt``}`

Explanation: Delay file processing is finished, CMNDELAY has opened the started task to external logon, and it has released the ENQ resource for the delay file.

Solution: No action required.

`CMN_464I CMNDELAY - {``package``} {``trancd``} {``trandata``}`

Explanation: This message shows updates made by CMNBATCH. This message has several formats in addition to the one shown above. Solution: No action required.

`CMN_468I` `CMNDELAY - Waiting for resource => {``qname rname``}`

CMNDELAY - CHGMAN {delay.file.name}

Explanation: CMNDELAY is attempting to gain exclusive control of the delay file through an ENQ resource. The second CMN_468I message shows qname of the resource and the rname, which is the delay file name. If another process, such as a CMNBATCH job step, has ownership of the resource, CMNDELAY waits as a resource requestor until the other process releases the resource.

Solution: No action required.

`CMN_469I` `CMNDELAY - Resource obtained successfully.`

Explanation: CMNDELAY has obtained exclusive control of the delay file through an ENQ resource.

Solution: No action required.

`CMN_470I` `CMNSTART CMNDELAY is waiting for jobname,asid,system {``jobname``} {``asid``} {``smfid``}`

Explanation: Delay processing is in a requestor wait for the ENQ resource for the delay file. This message is displayed once a minute until CMNDELAY gets ownership.

Solution: No action required.

`CMN_476I` `CMNSTART Delay file processing started`

Explanation: Delay file processing has been requested via a modify request.

Solution: No action required.

`CMN_477I` `CMNSTART Delay file processing already in progress`

Explanation: Delay file processing has been requested previously and has not completed yet. New request ignored.

Solution: Wait until previous request has completed.

`CMN_478I` `CMNSTART Delay file processing complete`

Explanation: Delay file processing has completed.

Solution: No action required.

`CMN_480I` `CMNSTART Waiting for HLL exit address space to initialize.`

Explanation: A start command has been issued for the HLLX address space; ZMF will wait to be contacted by HLLX. ZMF will wait/retry for up to 5 minutes reissuing this message every 30 seconds. When contact is successful, message CMN_481I will be issued. If connection is not made within the 5 minute window, ZMF will issue message CMN_490I.

`CMN_481I` `CMNSTART Successfully connected to HLL exit address space.`

Explanation: ZMF has established contact with the HLLX address space.

`CMN_482I` `CMNSTART Termination of HLL exit address space requested`.

Explanation: ZMF is shutting down or a DETACH command has been issued for the HLLX function.

`CMN_483I` `CMNSTART Termination of HLL exit address space complete.`

Explanation: HLLX has indicated to ZMF that shutdown is complete.

`CMN_484I` `CMNSTART Nothing heard from HLLX, unilateral termination.`

Explanation: During shutdown of started task, ZMF requests HLLX to shut down. ZMF waits a total of 40 seconds before issuing this message and proceeding to shutdown itself.

`CMN_485I` `CMNSTART HLLX active exit table has been reloaded.`

Explanation: The HLLX reload command has been issued. ZMF has read the exit definitions from the package master and communicated these to the HLLX address space.

`CMN_486I` `CMNSTART No active HLLX exits are defined, HLLX will shut down.`

Explanation: The HLLX reload command has been issued but no active exit definitions were read from the package master. There is no activity required of HLLX; HLLX will shut down.

`CMN_487I` `CMNSTART Please issue ATTACH HLLX command or restart ZMF if you wish to re-activate one or more exits.`

Explanation: This message succeeds CMN_486I. After HLLX has shut down, you must issue the ATTACH HLLX command to restart it.

`CMN_488I` `CMNSTART Prior instance of HLLX still active, please try later.`

Explanation: An ATTACH HLLX command has been issued but an instance of the HLLX address space is already active for this ZMF subsystem.

`CMN_489I` `CMNSTART HLL exit address space creation failed.`

Explanation: An attempt to start up HLLX has failed; examine the ZMF MSGLOG and SYSLOG to further identify the reason(s) it has failed.

`CMN_490I` `CMNSTART HLL exit address space failed to initialize, re-attempt via ATTACH command.`

Explanation: ZMF has abandoned attempt to establish communications with the HLLX address space (see associated message CMN_480I).

`CMN_491I` `CMNSTART There are currently no active HLL exits.`

Explanation: Issued in response to a CMN,DISPLAY,HLLX command. No active HLL exits exist. NOTE CMN_491I is mutually exclusive with CMN_492I - only one can be issued.

`CMN_492I` `CMNSTART Displays a set of messages identifying each active HLLX exit.`

Explanation: Issued in response to a CMN,DISPLAY,HLLX command if active exits are defined. The list of active exits follows this message.

`CMN_493I` `CMNSTART End of HLLX active exits list.`

Explanation: Issued in response to a CMN,DISPLAY,HLLX command. The list of active exits is terminated by this message.

`CMN_494I` `CMNSTART IntName Typ Env External Name Debug Ids`

Explanation: Issued in response to a CMN,DISPLAY,HLLX command. Headings for the active exits list.

`CMN_495I` `CMNSTART {``intname``} STD {``env``} {``external name``}`

Explanation: Issued in response to a CMN,DISPLAY,HLLX command. One message is issued for each active standard exit definition and shows the internal exit name, the fact that it is a standard exit definition, whether it is REXX or LE, and the external module name which implements the functionality.

`CMN_496I` `CMNSTART {``intname``} DBG {``env``} {``external name``} {``debug ids``}`

Explanation: The CMN_496I message is issued for each active debug exit definition and shows, in addition to the CMN_485I information, the list of up to 10 userids which will take the debug exit ahead of the standard exit.

`CMN_497I` `CMNSTART No active HLL exits are defined, the HLLX address space will not be started.`

Explanation: This message will display during ZMF startup if no active HLL exits are defined. The HLLX started task is not started.

`CMN_498I` `CMNSTART The HLLX started task is not active, No action taken or required.`

Explanation: A RELOAD HLLX command has been issued however HLLX is not currently active.

`CMN_520I` `ZMF Health Check exit CMNHCADD is already in place.`

Explanation: A pre-existing version of CMNHCADD is already registered in the HZSADDCHECK system exit list.

`CMN_521I ZMF health check exit CMNHCADD is not present.`

Explanation: The CMNHCADD routine is not currently in the list of HZSADDCHECK system exits.

`CMN_522I` `The active exit CMNHCADD is current, it will not be refreshed.`

Explanation: The pre-existing version of CMNHCADD is at least as current as our version, we will leave it in place.

`CMN_523I` `Existing ZMF Health Check exit CMNHCADD is being refreshed.`

Explanation: The existing CMNHCADD routine is older than ours, we will replace it with ours.

`CMN_524I` `Health Check exit CMNHCADD was refreshed successfully.`

Explanation: We have replaced the current active exit with our later version.

`CMN_525I` `Health Check exit CMNHCADD was added successfully.`

Explanation: Our version of CMNHCADD was added to the list of HZSADDCHECK system exits.

`CMN_526I` `ZMF Health Checks have been scheduled.`

Explanation: The CMNHCADD exit has been scheduled to be run by the IBM Health Checker address space. This will cause defined health checks to be run.

`CMN_527E` `Attempt to schedule ZMF Health Checks has failed, rc/rsn`

Explanation: Invocation of the HZSADCHK REQUEST=ADDNEW macro has failed with these return/reason codes. The health checks will not be run.

`CMN_528E` `Error in LIST function of CSVDYNEX, rc/rsn`

Explanation: The attempt to list the HZSADDCHECK system exits using CSVDYNEX has failed with these return/reason codes. No further health check processing will take place.

`CMN_529E` `Error in DELETE function of CSVDYNEX, rc/rsn`

Explanation: The attempt to delete our CMNHCADD exit from the list of HZSADDCHECK system exits has failed with these return/reason codes. No further health check processing will take place.

`CMN_530E` `Error in ADD function of CSVDYNEX, rc/rsn`

Explanation: The attempt to add our CMNHCADD exit to the list of HZSADDCHECK system exits has failed with these return/reason codes. No further health check processing will take place.

`CMN_531I` `Health Check exit CMNHCADD has been removed.`

Explanation: The health check exit that we placed into CSA during start up has now been removed (issued during ZMF termination).

`CMN_532I` `No action taken on termination.`

Explanation: No action required during ZMF termination. Either a pre-existing CMNHCADD exit was left in place or no CMNHCADD exists.

`CMN_533E` `Loop in CSVDYNEX execution, Health Check setup has been terminated.`

Explanation: Internal error in health check exit list process. No further health check processing will take place.

`CMN_534I` `The IBM Health Checker address space is not active, no ZMF health checks will be scheduled.`

Explanation: As it says. Also this is followed by message CMN_531I.

`CMN_800I` `{``userid``} Opened VSAM file {``delay.file.name``} Exclusive`

Explanation: CMNDELAY is starting delay file processing and has opened the VSAM file after first gaining ownership of the ENQ resource for the file.

Solution: No action required.

`CMN_800I` `{``userid``} Closed VSAM file {``delay.file.name``}`

Explanation: CMNDELAY has completed delay file processing and closed the VSAM file.

Solution: No action required.

`CMN_820I` `CMNSTART Change Man VSAM File Statistics`

Explanation: A series of CMN_820I messages at ZMF shutdown provides a table of ZMF VSAM file statistics covering the life of the started task. Each CMN_820I message adds a row of counts for each of these columns: CMNPMAST CMNLOG CMNRECV CMNDELAY CMNINFO. There is a separate CMN_820I message (row) for each these file actions/conditions:

Read Update
Read Only
Read Next
Write (Sync)
Write (ASync)
Update
Delete
Start
Start Generic End Request
Dup Records
Record locks
Max locks used
CI locks found

CMN001 ISPF Panel Messages

These messages are issued by ISPF panels in the ChangeMan ZMF ISPF client. The short and long message text resides in the MESSAGES library concatenation at the ISPMLIB DD statement.

The messages in this section are generated by ISPF panel edits, and they are intended to be self-explanatory. There is no explanation or solution listed for the messages in this section.

`CMN001` `Invalid command | "&ZCMD" is an invalid primary command.`

`CMN002` `Invalid table command | "&LCMD" is not a valid table line command.`

`CMN003` `Operand invalid | Line command "&LCMD" supports only numeric operands.`

`CMN004` `Invalid source type | The valid types are CPY, CTC, DOC, JCL, LCT, PRC, SRC and VLD.`

`CMN005` `Invalid language | The valid languages are ASM, COBOL, DBD, EASYTREV, MARK, MFS, PLI and PSB.`

`CMN006` `Invalid record format | The valid types are F, FB, V, VB, U.`

`CMN007` `Invalid record length | Record length is inconsistent with block size for this format.`

...

`CMN008` `Invalid library type | Enter 3 alphanumeric characters (first cannot be numeric).`

`CMN009` `Invalid package type | Package type must be "planned permanent" for package level 2 or 3.`

`CMN010` `Invalid package level | Level must be "Simple" if it's rescinding other packages.`

`CMN011` `Invalid package type | Package type must be 1 or 3 if it's rescinding other packages.`

`CMN012` `Invalid proc type | The valid types are COBOL, ASM, PLI, MFS, PSB, DBD, MARK, EASYTREV.`

`CMN013` `Invalid application | Application must be 3 or 4 alphanumerics starting with alphabetic.`

`CMN014` `Invalid package name | Package name must be 3-4 alphanumerics followed by 1-6 numerics.`

`CMN015` `Invalid table command | In browse mode, S (select) is the only valid command.`

`CMN016` `Invalid dataset name | This dataset name cannot have any quotes.`

`CMN017` `Invalid space type | Space type must be TRK, CYL or BLK.`

`CMN018` `Bad specification | Language must be similar to source type.`

`CMN019` `Invalid dsorg | The valid dataset organizations are PDS, SEQ, PAN, LIB and OTH.`

`CMN020` `Invalid page format | The format of the page command is "PAGE 3".`

`CMN021` `Invalid option | The Dates function is not available in the production environment.`

`CMN022` `Unsupported value | This value is not supported at this time.`

`CMN023` `Invalid value | You may only specify this value for environment DEV, PROD, or DP.`

`CMN024` `Invalid line command | "&LCMD" line command is invalid at this time.`

`CMN025` `Not enough lead time | Not enough time to review this component. Contact administrator.`

`CMN026` `Invalid component status | Component status must be FROZEN or UNFROZEN for line command "&LCMD".`

`CMN027` `Invalid line command | S and B are the only valid line commands while in%Query+function.`

`CMN028` `Invalid locate format | The format of locate command is "L MEMBER" or "L MEM".`

`CMN029` `Invalid value | You may only specify one of the listed values.`

`CMN030` `Invalid next page format | The format of the next page command is "NEXT PAGE".`

`CMN031` `Invalid transmit vehicle | The valid transmit vehicles are NDM, BDT, IEBCOPY and OTHER.`

`CMN032` `Unsupported function | Delete member function is only valid for PDS or SEQ development library.`

`CMN033` `Invalid field | Enter either a generic unit name or a volume serial.`

`CMN034` `Enter required field | Either generic unit name or volume serial must be specified.`

`CMN035` `Invalid record format | Valid record formats are F, FA, FB, FBA, FBM, FM, FS, V, VA, VB, VBA, VBM, VM, and U.`

`CMN036` `Invalid page value | Valid values are 1 to 9999.`

`CMN037` `Enter required field | Language name is required for "SRC" or SRC-Like library types.`

`CMN038` `Enter required field | Component name must be entered when Source Library is blank.`

`CMN039` `Invalid force option | Valid force options are 1 or 2.`

`CMN040` `Invalid selection code | Valid codes are S (Select) and D (Delete).`

`CMN041` `Invalid selection code | Valid codes are S (Stage), D (Delete), R (Recompile), H (History), and I (Short History).`

`CMN042` `Invalid selection code | S (Select) is the only valid selection code.`

`CMN043` `Invalid selection code | Valid codes are S (Stage), D (De-select), H (History), and I (Short History).`

`CMN044` `Invalid selection code | Valid codes are S (Sel), D (De-Sel), E(Edit), B (Browse), H (History), and I (Short History).`

`CMN045` `Invalid selection code | Valid codes are I (Insert), R (Repeat), and D (Delete).`

`CMN046` `Invalid selection code | Valid codes are A (Approve), R (Reject), V (Further Review), + and C (Checkoff).`

`CMN047` `Invalid selection code | Valid codes are I (Insert), R (Repeat), D (Delete), and S (Select).`

`CMN047A` `Invalid selection code | Valid codes are I (Insert), R (Repeat), D (Delete), S (Select), and * (List).`

`CMN048` `Invalid selection code | Valid codes are A (Allocate) and D (Defer Allocation).`

`CMN049` `Invalid selection code | U (Undelete) is the only valid selection code.`

`CMN050` `Invalid selection code | Valid codes are U (Unfreeze), and SL (Source to load relationship).`

`CMN051` `Invalid selection code | Valid codes are B (Browse), H (History), I (Short history), L (List), R (Rename), S(Scratch) and V (View).`

`CMN052` `Invalid selection code | Valid codes are D (Delete), H (History), I (Short History), and L (Libraries).`

`CMN053` `Invalid selection code | Valid codes are B (Browse), H (History), S (Select) and V (View).`

`CMN054` `Invalid selection code | The only valid code is V (Verify)`.

`CMN055` `Invalid selection code | Valid codes are L (Lock), U (Unlock), and R (Reset)`.

`CMN055A` `Invalid selection code | The only valid code is R (Reset)`.

`CMN056` `Invalid selection code | Valid codes are B (Browse), H (History), M (Mass), S (Select) and V (View)`.

`CMN057` `"&TCMD" command invalid | "&TCMD" command can only be entered on the command line`.

`CMN058` `Invalid command | Valid commands are BROWSE, CANCEL, HISTORY, LOCATE, RENAME, SCRATCH, SORT and VIEW`.

`CMN058A` `Invalid command | Valid commands are BROWSE, CANCEL, HISTORY, LOCATE, LONG, RENAME, SCRATCH, SHORT, SORT and VIEW.`

`CMN059` `Invalid command | Valid commands are REFRESH and CANCEL.`

`CMN060` `Enter required field | This field is required for this option.`

`CMN061` `Enter required field | Component type field must be SRC for designated procedure option.`

`CMN062` `Enter required field | Component name is required for designated procedure option`.

`CMN063` `Invalid select command | Use "SELECT ALL" command to browse all descriptions`.

`CMN064` `Invalid set command | Command format is SET??? ### (??? = MON-SUN or ALL; ### = Number of packages.)`.

`CMN065` `Invalid set value | The valid set values must range from 0 to 255.`

`CMN066` `Level out of range | Baseline level must range from 2 to 10 for this storage means.`

`CMN067` `Level out of range | Baseline level must range from 2 to 255 for this storage means.`

`CMN068` `Enter required field | Baseline level must be entered if performing mass checkout`.

`CMN069` `Conflicting information | Enter R or D to relink or delete a single load module`.

`CMN070` `Invalid command | Valid commands are CANCEL, REFRESH, CLEAR, LOCATE, SELECT, DELETE, and RENAME`.

`CMN070A` `Invalid command | Valid commands are CANCEL, REFRESH, CLEAR, LOCATE, and SELECT`.

`CMN071` `Required string missing | The &TCMD command requires specification of a valid release ID string`.

`CMN072` `Required string missing | The &TCMD command requires a second valid string of new release ID`.

`CMN073` `Invalid selection code | Valid codes are S (Select), D (Delete), R (Rename), and C (Clear)`.

`CMN074` `&CMDPRM2 already exists | Invalid to rename to an existing release ID`.

`CMN075` `Invalid command | Valid commands are LOCATE, EDIT, and SELECT.`

`CMN076` `Invalid selection code | Valid codes are S (Select), E (Edit) and V (View)`.

`CMN076A` `Invalid selection code | Valid codes are S (Select) and V (View).`

`CMN076E` `Invalid selection code | Valid codes are B (Browse), V (VIEW), Q (Query), P (Process) and C (Checkout)`

`CMN077` `Invalid command | Valid commands are LOCATE and SELECT`.

`CMN078` `Invalid selection code | The only valid selection code is S (Select)`.

`CMN079` `New name not allowed | New name is entered only for the rename member option`.

`CMN080` `Enter required field | Component type required when relationship is present`.

`CMN081` `Invalid command | Valid commands are LOCATE, BROWSE, SELECT, DESELECT, HISTORY, REFRESH and CANCEL.`

`CMN082` `Invalid command | Valid commands are LOCATE, REFRESH, and CANCEL`.

`CMN083` `Invalid selection code | Valid codes are S (Select) and B (Browse)`.

`CMN084` `Invalid selection code | Valid codes are S (Select) and D (De-select)`.

`CMN085` `Invalid selection code | Valid codes are (B) Browse, (H) History and (S) Select.`

`CMN085A` `Invalid selection code | Valid codes are (B) Browse, (H) History, (S) Select and (V) View`.

`CMN086` `Invalid command | Valid commands are LOCATE, REFRESH and CANCEL.`.

`CMN087` `Invalid command | Valid commands are LOCATE, SAVE, COPY, REFRESH, and CANCEL`.

`CMN087A` `Invalid command | Valid commands are LOCATE, COPY, REFRESH, and CANCEL`.

`CMN088` `Invalid command | Valid commands are HOLD, RELEASE, CHANGE, REFRESH and CANCEL`.

`CMN089` `Invalid selection code | Valid codes are H (Hold), R (Release), C (Change), D (Delete), and S (Submit)`.

`CMN090` `Invalid selection code | Valid codes are S and R (Relink), B (Browse), and H (History)`.

`CMN090A` `Invalid selection code | Valid codes are S and R (Relink), B (Browse), H (History) and V (View)`.

`CMN091` `Invalid selection code | Enter S to browse compressed member`.

`CMN092` `Invalid selection code | Valid codes are CD (Change Date), CS (Change Status), DE (Delete), MD (Memo Delete) and S (Submit)`.

`CMN093` `Invalid selection code | Valid Codes are A (Approve), S (Select package), and Q (Query package)`.

`CMN094` `Invalid package level | Package level can only be updated to Simple or Participating.`

`CMN095` `Invalid command | Valid commands are REFRESH, CANCEL, SORT and LOCATE`.

`CMN096` `Invalid command | Valid commands are BACK and CANCEL`.

`CMN097` `Invalid selection code | Valid codes are B (Browse), BL (Browse Listing), H (History), S (Comp/Link options), SL (Source to Load), UL (User List), V (View), VC (Version Control), and VL (View Listing)`.

`CMN097A` `Invalid selection code | Line command D (Delete) is not valid for unfrozen components`.

`CMN097B` `Invalid selection code | Line command D (Delete) is not valid for a frozen package`.

`CMN098` `Invalid command | Valid commands are BROWSE, CANCEL, HIST, LOCATE, REFRESH, SORT, STAGE and VIEW.`

`CMN099` `Invalid command | Valid commands are BROWSE, SELECT, HIST, REFRESH, CANCEL, SORT and LOCATE.`

`CMN099A` `Invalid command | Valid commands are BROWSE, CANCEL, HIST, LOCATE, LONG, REFRESH, SELECT, SHORT, SORT, VIEW, MASS and MASSALL`.

`CMN099B` `Invalid command | Valid commands are BROWSE, CANCEL, HIST, LOCATE, LONG, REFRESH, SELECT, SHORT, SORT, VIEW, MASS, MASSALL and XLONG`.

`CMN100` `Invalid selection code | Valid codes are B (Browse), S (Stage), and H (History)`.

`CMN101` `Invalid command | Valid commands are CANCEL, LOCATE, LONG, REFRESH, SHORT, SORT and XLONG.`

`CMN101A` `Invalid command | Valid commands are CANCEL, DCD, EDIT, LOCATE, LONG, MASS, REFRESH, SHORT, SORT and XLONG.`

`CMN102` `Level out of range | Baseline level must range from 2 to 999 for this storage means`.

`CMN103` `Invalid command | Valid commands are REFRESH, CANCEL, SETALL, and SETMON to SETSUN`.

`CMN104` `Invalid checkout | Check out to staging requires a package name`.

`CMN105` `Invalid selection code | Enter one of the listed codes below`.

`CMN106` `Invalid selection code | Valid codes are B (Browse), S (Select), D (Delete), and H (History)`.

`CMN107` `Invalid value | Valid values are 0, -1 to -999, and +1 to +99.`

`CMN108` `Invalid selection code | Valid codes are: I (Insert), R (Repeat), D (Delete), and * (List)`.

`CMN109` `Invalid selection code | Valid codes are B (Browse), H (History), SL (Source to Load relationship), UL (User list) and V (View).`

`CMN110` `Invalid command | Valid commands are DCD, LOCATE, LONG, SHORT, SORT and XLONG.`

`CMN111` `Invalid release ID | Enter up to 4 alphameric chars (1st must be alpha; rest: A-Z, 0-9).`

`CMN112` `Invalid command | Valid commands are U (Unfreeze), and F (Freeze)`.

`CMN113` `Invalid command | Valid commands are BROWSE, HIST, CANCEL, REFRESH, LOCATE and SORT`.

`CMN114` `Invalid selection code | Valid codes are B (Browse), D (Deselect), H (History), S (Select) and V (View)`.

`CMN115` `Invalid selection code | U (Unfreeze) is the only valid command`.

`CMN116` `Invalid value | Enter one of the listed values ('/,Blank')`.

`CMN117` `Invalid command | Valid commands are CANCEL, EDIT, LOCATE, REFRESH, SELECT, SORT and VIEW`.

`CMN117A` `Invalid command | Valid commands are CANCEL, LOCATE, REFRESH, SELECT, SORT and VIEW`.

`CMN118` `Invalid command | Valid codes are B (Browse), H (History), S (Options), UL (User List), V (View) and VC (Version Control).`

`CMN119` `Invalid command | Valid commands are LOCATE, SORT, SHORT, LONG, CANCEL, and REFRESH`.

`CMN121` `Invalid command | Valid commands are U (Unfreeze), F (Freeze), and S (Select)`.

`CMN122` `Invalid selection code | Valid codes are F (Freeze), U (Unfreeze), and SL (Source to load)`.

`CMN123` `Invalid value | Installed packages value must be zero, greater than, or equal to the staging datasets and staging versions values`.

`CMN123A` `Invalid value | Component history value must be zero, greater than, or equal to the installed packages value`.

`CMN124` `Invalid selection code | Valid codes are F (Freeze), and U (Unfreeze)`.

`CMN125` `Invalid date format | Enter a valid gregorian date in the format YYYYMMDD`.

`CMN126` `Invalid application | Application name must be 3 or 4 alphamerics starting with alphabetic`.

`CMN127` `Invalid library type | Library type must be 3 alphameric characters starting with alphabetic`.

`CMN128` `Invalid command | Valid commands are CANCEL, LOCATE, REFRESH, RESET and VIEW`.

`CMN129` `Invalid value | Retry wait must be 0 if retry count is 0.`

`CMN130` `Invalid selection code | Valid codes are B, BS, C, H, L, P, V, VS and X`.

`CMN131` `Invalid value | Valid values are 0, -1 to -998, and +1 to +99.`

`CMN132` `Invalid value | Valid values are Y (Yes) and N (No)`.

`CMN133` `Invalid value | Valid values are 0 to 80.`

`CMN134` `Invalid value | From column must be less than To column.`

`CMN135` `Invalid command | Valid commands are REFRESH, CANCEL, SORT, and LOCATE`.

`CMN136` `Invalid selection code | Valid codes are B, BS, C, D, H, P, V, VS and X`.

`CMN137` `Invalid selection code | Valid codes are B, C, D, and H.`

`CMN138` `Invalid value | Valid values are PDS, PDSE, SEQ, PAN, and LIB.`

`CMN139` `Invalid selection code | Valid codes are S (Select), and D (Deselect)`.

`CMN140` `Invalid type | Valid types are AP, PG, DS, SC, RP, CN, and OX.`

`CMN141` `Invalid type | Valid DC types include CICS, IDMS, IMS, ISPF, MVS, DLG, and DDS`.

`CMN142` `Invalid type | Valid DB types include DLI, IDMS, IMS, and VSAM.`

`CMN143` `Invalid type | Valid SQL types include OS2DM, XDB, SQLDS, DB2, and SQL400`.

`CMN144` `Invalid option | Valid options are YES, and NO`.

`CMN145` `Invalid option | Valid CICS release values are 0, 1.7, 2.1, and 3.1`.

`CMN146` `Invalid option | Valid IMS release values are 0, 2, and 3.`

`CMN147` `Invalid selection code | Valid codes are B (Browse), BA (Browse Activity file), BD (Browse Description), BL (Browse Listing), H (History), SL (Source to Load), V (View) VC (Version Control) and VL (View Listing)`.

`CMN148` `Invalid syntax | Valid syntax: EDIT MEMBER.LIB`.

`CMN149` `No related scratches | &MEMBNME..&CMPTYPE scratch saved. Prior baseline package not found. Scratch requests for related components (e.g. LOD) must be added manually.`

`CMN150` `Invalid sub-type | Valid IMS Sub-types are P, D, M, S, B, F, and R`.

`CMN151` `Invalid acb type | Valid ACB types are P (PSB) and D (DBD)`.

`CMN152` `Control statement error | Valid ACB control statements are B (Build) and D (Delete)`.

`CMN153` `Control statement error | Valid DBD control statements DATASET, AREA, SEGM, FIELD, LCHILD, XDFLD, DBD, and DBDGEN.`

`CMN154` `Control statement error | Valid PSB control statements are PSBGEN, PCB, SENSEG, and SENFLD`.

`CMN155` `Invalid sub-type | Valid Db2 sub-types are B, D, N, P, Q, R, S, and T`.

`CMN156` `Invalid act lib type | Valid types are B (Bind plan/pkg), S (SQL/StoPro), and V (Bind service)`.

`CMN157` `Invalid IMS ID | Valid IMS ID is 4 alphanumeric characters (1st must be alpha)`.

`CMN158` `Invalid Db2 ID | Valid Db2 ID is 4 alphanumeric characters (1st must be alpha)`.

`CMN159` `Invalid command | Valid commands are S (Select) and CANCEL`.

`CMN160` `Invalid option | Valid options are 1, 2, 3, 4 and 5`.

`CMN161` `Invalid id | Valid report IDs are numbers 000 to 999`.

`CMN162` `Invalid type | Valid report types are G (Global Admin.), A (Application Admin.) and U (User)`.

`CMN163` `Invalid type | Valid report types are A (Application Admin.) and U (User)`.

`CMN164` `Invalid number | Package number can not be masked and is a 1 to 6 digit number`.

`CMN165` `Invalid option | Valid options are 1 and 2.`

`CMN166` `Invalid value | Enter "HELP" for valid values.`

`CMN167` `Invalid line command | Enter "HELP" for valid line commands.`

`CMN168` `Invalid command | Valid commands are CANCEL, LOCATE and SORT.`

`CMN169` `Invalid command | Valid commands are CANCEL, LOCATE, REFRESH, SELECT and SORT`.

`CMN170` `Invalid release id | Valid Release ID is 1 to 4 alphanumeric characters (1st must be alpha)`.

`CMN171` `Invalid application | Valid application name is 3 or 4 alphanumeric characters (1st must be alpha)`.

`CMN172` `Invalid TCP/IP address | TCP/IP addresses must be in format nnn.nnn.nnn.nnn`.

`CMN173` `Invalid package | Only Simple Planned Permanent packages can be attached to releases`.

`CMN174` `Command disabled | The delete command is currently disabled in this version of ERO`.

`CMN175` `Missing area information | Subsystem areas require that a next area is defined`.

`CMN176` `Missing area information | System areas require that a prior area is defined`.

`CMN177` `Invalid ID | Valid ID is 1 to 5 alphanumeric characters (1st must be alpha).`

`CMN178` `Invalid command | Valid commands are CANCEL, LOCATE, LONG, REFRESH, SELECT, SHORT and SORT.`

`CMN179` `Invalid command | Valid commands are CANCEL, LONG or SORT.`

`CMN180` `Invalid selection code | Valid codes are B (Browse), C (Compare), D (Delete), R (Recover), M (Merge) and V (View).`

`CMN181` `Invalid selection code | Valid codes are B (Browse), C (Compare) and V (View)`.

`CMN182` `Invalid selection code | Valid codes are P (Parms), T (Plan/pkg named templates), B (Plan/pkg general templates), Q (SQL named templates), G (SQL general templates), V (Service named templates), H (Service general templates), I (Insert), R (Repeat) and D (Delete)`.

`CMN182A` `Invalid selection code | Valid codes: P (Parms), T (Plan/pkg named templates), B (Plan/pkg general templates), Q (SQL named templates), G (SQL general templates), V (Service named templates), H (Service general templates), I (Insert), R (Repeat) or D (Delete), and * (List)`.

`CMN183` `Enter Required Field | Relationship and subordinate component name are required`.

`CMN184` `Enter Required Field | Relationship and component name are required`.

`CMN185` `Invalid selection code | Valid codes are B (Browse), and V (View).`

`CMN186` `Invalid selection code | Valid codes are P (Parms), T (Plan/pkg named templates), B (Plan/pkg general templates), Q (SQL named templates), G (SQL general templates), V (Service named templates), and H (Service general templates).`

`CMN187` `Invalid command | Command not valid in browse mode.`

`CMN188` `Library mismatch | Libraries must be all zFS or NON-zFS.`

`CMN189` `Invalid field | First character cannot be an asterisk`.

`CMN190` `Invalid Selection | INFO VSAM and INFO BUS SYSTEM are mutually exclusive`.

`CMN191` `Invalid command | Valid commands are REFRESH, CANCEL and LOCATE.`

`CMN192` `Invalid command | Valid commands are REFRESH, CANCEL, LOCATE, LONG, and SHORT.`

`CMN193` `Invalid volume | Volume name must contain only alphanumeric characters and characters $, # and @.`

`CMN194` `Invalid Type | Component activity file type must be different from source type source_type {``library type``}`

`CMN195` `Invalid command | Valid commands are LOCATE, SORT, SHORT, LONG, CANCEL, REFRESH and FIND.`

`CMN196` `Invalid Browse | Browse only valid for userids, Entity = N or blank.`

`CMNEX000` `Invalid format | Valid format: Operation Identification is nn, ie. (01).`

`CMNEX001` `Invalid format | Valid format: Predecessor Identification is nn, ie. (01).`

`CMNEX002` `Invalid date format | Valid date format: YYYYMMDD - YYYY=Year MM=Month DD=Day, ie.(19930205).`

`CMNEX003` `Invalid month | Valid months are 01 to 12 for January thru December.`

`CMNEX004` `Invalid day entered | Valid days for the Month selected are 01 to 31.`

`CMNEX005` `Invalid day entered | Valid days for the Month selected are 01 to 30.`

`CMNEX006` `Invalid day entered | Valid days for the Month of February are 01 to 28 or 01 to 29 for leap year.`

`CMNEX007` `Invalid time format | Valid format: HHMM - HH=Hours MM=Minutes, ie. (2115).`

`CMNEX008` `Invalid hours | Valid hours are from 00 to 23 in twenty-four hour format.`

`CMNEX009` `Invalid minutes | Valid minutes are from 00 to 59.`

`CMNPM000` `.WINDOW=NORESP | Invalid selection option: Press ENTER for retry.`

`CMNZ000` `&ZERRSM | &ZERRLM`

`CMNZ001` `Invalid primary command | Primary command not valid for this panel.`

`CMNZ002` `Invalid line command | Line command not valid for this panel.`

`CMNZ003` `Invalid command suffix | Line command suffix must be numeric.`

`CMNZ004` `Changes saved | Changes saved in the Package Master.`

`CMNZ005` `Changes cancelled | Changes cancelled at user request.`

`CMNZ006` `Line command not allowed | Form &XFRMID has invalid status for this request.`

`CMNZ007` `Access denied | Access denied - see administrator.`

`CMNZ008` `Package not found | Package &XPKGNAME not found in the Package Master.`

`CMNZ009` `Package memo deleted | Package &XPKGNAME is memo deleted.`

`CMNZ010` `Duplicate rows | Duplicate rows not allowed for this form.`

`CMNZ011` `Variable name reserved | Variable names beginning with X, Y or Z are reserved.`

`CMNZ012` `Form error | Form data record not found - retry command.`

`CMNZ013` `Form undefined | Form definition record not found - see administrator.`

`CMNZ014` `Form limit exceeded | Form data must not exceed 32,767 bytes.`

`CMNZ015` `Invalid form ID | Form id must be numeric.`

`CMNZ016` `Invalid form description | Form description must not be blank.`

`CMNZ017` `Invalid lead time | Lead time must be numeric.`

`CMNZ018` `Invalid variable name | Variable name contains an invalid character.`

`CMNZ019` `Invalid variable format | Variable format must be CHAR or FIXED.`

`CMNZ020` `Invalid variable length | Variable length must be in range 1-3072 (CHAR) or 1-4 (FIXED).`

`CMNZ021` `Invalid table variable | Table variable must be YES or NO.`

`CMNZ022` `Invalid key variable | Key variable must be YES or NO.`

`CMNZ023` `Variables exceeded | Number of variables must not exceed 200.`

`CMNZ024` `Variable length exceeded | Total of variable lengths must not exceed 3,072.`

`CMNZ025` `Invalid vehicle | Notification vehicle must be MVSSEND, EMAIL or BATCH.`

`CMNZ026` `Undefined vehicle | Notification vehicle undefined.`

`CMNZ027` `Invalid userids | Notification userids must not be blank.`

`CMNZ028` `Notifications exceeded | Notifications must not exceed 10 rows.`

`CMNZ029` `Approve/reject denied | Approve/reject authorization denied - see administrator.`

`CMNZ030` `Form already exists | Form &XFRMID already exists in the Package Master.`

`CMNZ031` `Form created | Form &XFRMID created in the Package Master.`

`CMNZ032` `Form deleted | Form &XFRMID deleted from the Package Master.`

`CMNZ033` `Form updated | Form &XFRMID updated in the Package Master.`

`CMNZ034` `No panels defined | No panels defined for form &XFRMID - see administrator.`

`CMNZ035` `Key variable not allowed | Key variable must be table variable.`

`CMNZ036` `Form in use | Form currently in use by userid &XLOCKID.`

`CMNZ037` `Invalid allow access | Allow access must be YES or NO.`

`CMNZ038` `Invalid allow submit | Allow submit must be YES or NO.`

`CMNZ039` `Form status changed | Form status has changed - use REFRESH command.`

`CMNZ040` `Skeleton not found | Skeleton &XSKEL not found in ISPSLIB.`

`CMNZ041` `Form unlocked | Form was unlocked.`

`CMNZ042` `Access denied | Unlock requires administrator authority.`

`CMNZ043` `Invalid package status | Form &XFRMID has invalid request for package in &XPKGSTAT status.`

`CMNZ044` `Browse mode only | Only Browse, Comment or Print allowed in Browse mode.`

`CMNZ045` `Lead time expired | Lead time for form &XFRMID has expired.`

`CMNZ046` `Invalid form data | Proceed through panels to correct invalid data.`

`CMNZ047` `Approve error | CMN3160A - Package creator cannot approve the package.`

`CMNZ048` `Approve error | CMN3161A - Approval is not allowed when approver worked on a component.`

`CMNZ050` `Userid error | Userids are a maximum of 8 characters separated by comma.`

`CMNZ051` `Userid error | Userids are alphanumeric and national characters only (@,#,$).`

CMN0200 General

`CMN0200I` `User detached | User being cancelled from ChangeMan ZMF`.

`CMN0205I` `Unable to open //CMNIMPFL | Impact Analysis abandoned CMN0206`.

`CMN0206I` `//CMNIMPFL file empty | Impact Analysis abandoned`.

`CMN0208I` `Warning; //CMNIMPFL has no date/time stamp`.

`CMN0209I` `Warning; //CMNIMPFL not in ascending order`.

`CMN0215I` `Dynamic allocation error | Allocation failed for LCT data set`.

`CMN0216I` `Open error | Allocation failed for LCT data set`

...

`CMN0217I` `Member not found | Member not found in LCT data set`

`CMN0218I` `LCT data set read error | I/O error reading LCT data set`

`CMN0221I` `Package Master Error | Some kind of error during Package Master READSEQ`

`CMN0222I` `Log File Error | Some kind of error during Log READSEQ`

`CMN0235I` `Notification Error | Invalid number of approvers specified`

`CMN0236I` `Notification Error | Invalid mail id specified`.

`CMN0237I` `Notification Error | Unable to logon to specified notification vehicle`.

`CMN0238I` `Notification Error | Mail database full or no storage`

`CMN0239I` `Notification Error | Invalid mail id password`

`CMN0240I` `Notification Error | Invalid options specified`

`CMN0241I` `Notification Error | Invalid mail type code`

`CMN0242I` `Notification Error | Invalid link to notification vehicle`

`CMN0243I` `Notification Error | Invalid notification vehicle specified. Contact Local Admin`.

`CMN0244I` `Notification Error | Approve record notification indicator not updated`

`CMN0245I` `Notification Error`

`CMN0246I` `Shutdown in progress | Change Man is shutting down, try later`

`CMN0247I` `Maximum users logged on | Maximum users logged on, try later`

`CMN0248I` `Session terminated | User has been disconnected from Change Man`

`CMN0250I` `P.M. Unloaded | All Package Master records transferred to QSAM`

`CMN0251I` `Error uncovered | An error of undetermined origin has been uncovered`

`CMN0252I` `Synchronous Error | Synchronous error in writing to VB QSAM file`

`CMN0253I` `Package Master Error | Unable to read global record 1`

`CMN0254I` `Package Master Error | Unable to read package general record 1`

`CMN0255I` `DSN Construction Error | Construction of staging data set failed`

`CMN0256I` `Package Master Error | Unable to read package master`

`CMN0257I` `Allocation Error | UNABLE TO ALLOCATE FLAT PACKAGE MASTER`.

`CMN0258I` `Open Error | Unable to open DCB`

`CMN0274I` `INPUT FILE I/O ERROR | Allocate input file`.

`CMN0275I` `SUCCESSFUL STAGE | We have successfully staged a program.`

`CMN0276I` `ALLOC. INPUT FILE | Unable to allocate staging input file`.

`CMN0277I` `DSORG INPUT FILE | Unable to determine staging input file DSORG`.

`CMN0278I` `CANNOT STAGE ISAM | Cannot stage ISAM files into staging libraries`.

`CMN0279I` `CONFLICTING DESCRIPTION | Inconsistent information describing file to be staged`.

`CMN0280I` `OPEN INPUT FILE | Unable to open input file to be staged`.

`CMN0281I` `MEMBER NOT FOUND | Requested member not found in specified library`.

`CMN0282I` `ALLOC. OUTPUT FILE | unable to allocate staging output file`.

`CMN0283I` `OPEN OUTPUT FILE | unable to open staging output file`.

`CMN0284I` `DIFFERING STAGER | Warning - You have overlaid a prior () version`.

`CMN0285I` `I/O ERROR | Staging I/O error`.

`CMN0286I` `MEMBER DELETE ERROR | Unable to Delete specified member in staging library`.

`CMN0287I` `RECFM UNDEFINED | Cannot stage undefined (RECFM=U) length records`.

`CMN0288I` `ATTEMPT TO OVERLAY | Overlaying prior {``userid``} version disallowed by ADMIN`.

Explanation: Displayed when the application administration parameter OVERLAY PRIOR STAGED MODULE is set to disallow and you attempt to stage a component from development to overlay an existing package component that is identified by another person’s userid. The compare is between the userid of the person attempting the stage from development and the userid that is stored in the package component record.

Solution: Consult with userid to coordinate your concurrent development. Delete the existing component from the package or stage the existing package component yourself to eliminate the conflict.

`CMN0289I` `STOW error | STOW error - no space in staging data set directory`

`CMN0290I` `X37 abend | Insufficient space in staging data set; abend xxx-xx`

`CMN0291I` `Alloc. SYSUT3 file | Unable to allocate IEBCOPY SYSUT3 file - xxxx`

`CMN0292I` `Data set in use | Staging data set in use by TSO user or batch job`.

`CMN0293I` `Compress error | Error detected while compressing staging data set`.

`CMN0294I` `Copy error | Error encountered copying from staging data set`.

`CMN0295I` `Close Input File | Unable to close input file to be staged.`

`CMN0296I` `User Verification Error | Unable to verify user; check local security module SERLCSEC.`

...

`CMN0297I` `Input file error | Dynamic input file unspecified.`

`CMN0298I` `STOW Error | Unable to update data set directory entry.`

`CMN0299I` `Copy Error | From/To cannot be the same for this library type.`

`CMN0311I` `Immediate Shutdown | Subtask Terminated - immediate shutdown required`

`CMN0329I` `SERDATES Error | Some kind of error during SERDATES processing`

`CMN0330I` `Allocation error; xxxx | Unable to allocate dataset`

`CMN0331I` `Dataset decompressed | Dataset decompressed successfully.`

`CMN0332I` `Decompress error | check Change Man application job for error message.`

`CMN0333I` `Dataset compared | Dataset has been compared successfully.`

`CMN0334I` `Version Copied | A stacked reverse delta version has been copied.`

`CMN0335I` `CMNUPDAT error | Check Change Man application job for error message`

`CMN0339I` `No I/A Dataspace | An I/A dataspace environment has not been established`

`CMN0340I` `DSN constructed | Staging dataset name constructed successfully`

`CMN0341I` `Error in DSN | An error has been detected in DSN construction`

`CMN0346I` `DB2-CAF GENERIC ERROR`

`CMN0347I` `DB2/CAF OK | DB2/Call Attach Facility successful call`

`CMN0348I` `No DB2 Environment | A proper DB2-CAF environment has not been established`

`CMN0349I` `Minor Function Hosed | Expected OPEN, CLOSE, Etc.`

`CMN0350I` `Directory Listed | Entire directory of library listed`

`CMN0351I` `Library alloc/open | Unable to allocate or open the specified library`

`CMN0352I` `Library SRCH error | Unable to search directory of specified library`

`CMN0375I` `Scheduling function err | Invalid scheduling function`

`CMN0376I` `Site data not found | I - Site data for package not found`

`CMN0377I` `Not found on schedule | I - Package not found in master schedule`

`CMN0378I` `Already in schedule | I - Package already in master schedule`

`CMN0379I` `Invalid package id | Invalid format for package id`

`CMN0380I` `Package not found | Package not found on package master`

`CMN0385` `Attempting INFO API connect`

`CMN0386` `Unable to open CMNINFO file`

`CMN0387 1 INFO connection disabled`

`CMN0387 2 INFO block Record number {``cr number``} cleared`

`CMN0387 3 INFO Change Record number {``cr number``} read`

`CMN0387 4 INFO Change Record number {``cr number``} cannot be found`

`CMN0387 5 INFO Change Record number {``cr number``} NOT written`

`CMN0387 6 INFO Change Record number {``cr number``} cannot be created`

`CMN0387 7 INFO Change Record number {``cr number``} updated`

`CMN0387 8 INFO Change Record number {``cr number``} Update attempt, not found`

`CMN0387 9 SSV init failed`

`CMN0387 a SSV terminated`

`CMN0388 1 INFO connection complete`

`CMN0388 2 SSV init complete`

`CMN0389 1 Disconnecting from INFO API`

`CMN0389 2 Terminating SSV`

`CMN0390` `Generic Message Processing`

`CMN0391I` `Opening I/A DSP | Attempting to open the I/A Dataspace`.

`CMN0392I` `I/A DSP available | I/A Dataspace OPEN, LDS {``lds``}`.

`CMN0393I` `I/A DSP Open error | I/A Dataspace open failed, rc: {``rc``}, rsn {``rsn``}`.

`CMN0394I` `Closing I/A DSP | Closing the I/A Dataspace`.

`CMN0395I` `I/A DSP offline | The I/A Dataspace is now offline`.

`CMN0402I` `I/A dsp full | ATTENTION: The impact analysis dataspace is full, reorganization is required`.

`CMN0403I` `I/A dsp full | The current I/A operation must be terminated, ABENDU0937`.

`CMN0405I` `INFO file full | INFO/SYS API INFOSTUB file full, make larger`

`CMN0410I` `Allocation error | Dynamic allocation error; xxxx`

`CMN0411I` `Part space rlse err | Part space rlse err. RC=xxxx`

`CMN0412I` `Obtain error | Unable to obtain data set format-1 DSCB - RC=xxxx`

`CMN0413I` `Data set not cataloged | Requested data set was not found in the catalog`.

`CMN0414I` `Data set not cataloged | Unable to allocate the requested data set`.

`CMN0415I` `Delete error | Unable to delete the requested data set`.

`CMN0416I` `Successful Delete | We have successfully deleted this library`

`CMN0417I` `Successful Alloc. | We have successfully allocated this library`

`CMN0418I` `Data set Not Cataloged | Requested data set is not in the catalog`.

`CMN0419I` `Invalid Dsorg | VSAM data set unsupported`

`CMN0421I` `Invalid RECFM | Valid RECFM: F,FB,FBA,FBM,V,VB,VBA,VBM and U`

`CMN0422I` `Invalid space request | Space request must be in terms of CYL/TRK/BLK`.

`CMN0423I` `Invalid Device Class | Device class is not a direct access storage device`.

`CMN0424I` `Invalid Device Type | Unknown direct access storage device`.

`CMN0430I` `Dict API Inactive | Data Dict. API task not active; contact Global Admin`.

`CMN0431I` `Dict API detached | Data Dict. API task detached; contact Global Admin`.

`CMN0437I` `Major Function Error | Unidentifiable Major Function - RC=12`

`CMN0438I` `User ID Lost | TSO-ID lost when detached for inactivity`.

`CMN0439I` `TSO Server Down | TSO File Tailoring Server Down`

`CMN0440I` `INFO API Inactive | INFO/SYS API task not active; contact Global Admin`.

`CMN0441I` `Info API Detached | INFO/SYS API task detached contact Global Admin`.

`CMN0442I` `INFO API problem | INFO/SYS API task problem, see SERPRINT/APIPRINT`

`CMN0443I` `INFO ENQueue conflict | INFO/SYS API task problem, ENQueue conflict`

`CMN0444I` `INFO ENQueue wait | INFO/SYS API task is waiting for ENQueue`

`CMN0450` `Att. DB2 CAF connect, id=`

`CMN0451` `DB2 Down; Attempting reconnect`

`CMN0452` `DB2 CAF connect ok, id=`

`CMN0453` `Shutting Down - FORCE/ABTERM, ID=`

`CMN0454` `Detected DB2 stop quiesce`

`CMN0455` `DB2 CAF Disconnect`

`CMN0456` `Warning - Problems opening a thread in DB2 at this time`

`CMN0457` `generic message display?`

`CMN0458` `DB2 CAF connect ok, id={``db2 ssid``} DB2VRM= {``db2vrm``}`

`CMN0462 1 PKG status not dis or apr`

`CMN0462 2 pkg dis still pending`

`CMN0462 3 INVALID remote site`

`CMN0462 4 SUBMITTED job....PACKAGE name...`

`CMN0465` `Common print error message`.

`CMN0466` `Common print error message`.

`CMN0467` `PACKAGE inserted...`

`CMN1000A` `ISPF SERVICE ERROR | ISPF {``service``} service error; RC - {``return code``}`.

Explanation: Displays when an ISPF Dialog error is incurred. ChangeMan ZMF invokes the ISPF Dialog Manager to display panels during File Tailoring of Skels.

Solution: Use the return code (RC) to review the ISPF Dialog Manager for the source of the problem.

`CMN1001I` `ChangeMan ZMF is shutting down`.

Explanation: Displays when the operator requests ChangeMan ZMF to perform a controlled shutdown.

Solution: Exit the ChangeMan ZMF panels as soon as it is convenient. See the “Shutting Down the Started Task” section in the ChangeMan ZMF Administrator’s Guide.

`CMN1002I` `ChangeMan ZMF is down`

Explanation: Displays when the operator requests ChangeMan ZMF to perform an immediate shutdown; that is, to purge all users in session.

Solution: Try to reenter the ChangeMan ZMF session at another time. See the “Shutting Down the Started Task” section in the ChangeMan ZMF Administrator’s Guide.

`CMN1003I` `ChangeMan ZMF Started Task is inactive`.

Explanation: Displays when the ChangeMan ZMF started task has not been brought up.

Solution: Ask the operator to bring up the started task.

`CMN1004A` `NOT AUTHORIZED | Not authorized to access {``function``} function`.

Explanation: This breach of security message displays when you try to perform a function that is not authorized at your security level.

Solution: Cancel out of the operation and contact the global administrator.

`CMN1005A` `INVALID OPTION | The entered option is not valid`.

Explanation: Displays when you enter an option that ChangeMan ZMF does not recognize.

Solution: Review the panel options and re-key the entry, or cancel and exit the panel.

`CMN1006A` `INVALID OPTION | Option unavailable - package must be in {``status``} status`.

Explanation: Displays when you request a function that is not available for a package that is not in development status, such as attempting to update a frozen package.

Solution: You can select to revert the package back to development status. See the “Reverting a Package” chapter in the ChangeMan ZMF User’s Guide for the required rules.

`CMN1007A` `INVALID OPTION | Selective demotion disallowed - contact ADMIN`.

Explanation: Displays when you try to selectively demote components within a promoted package whose governing project was set up with demotion rules that disallow selective demotion.

Solution: You can try a full demotion, or talk with the project’s administrator regarding the demotion rules. See the “Promoting and Demoting Components” section in the ChangeMan ZMF User’s Guide and the “Setting Up Global Parameters” and “Setting Application Parameters” sections in the ChangeMan ZMF Administrator’s Guide.

`CMN1008A` `INVALID OPTION | Option disallowed in this environment`.

Explanation: Displays when you enter a menu option that is not allowed in the currently configured environment, such as attempting to configure project baseline, promotion, and so forth, in a remote site (PROD environment).

`CMN1009A` `INVALID OPTION | Option only valid in DEV or DEVPROD environment`.

Explanation: Displays when you enter a menu option that is not allowed in the currently configured environment, such as attempting to configure project remote site information in an ALL environment.

`CMN1010A` `PACKAGE NOT FOUND | {``package id``} does not exist in the Package Master`.

Explanation: Displays when you enter a change package number that ChangeMan ZMF does not recognize during an attempt to perform any function that requires an existing change package, such as updating change package information.

Solution: You should either review the information entered and re-key the package number, or cancel and exit.

`CMN1011I` `INITIALIZATION ERROR | Unable to read Package Master global record`.

Explanation: Displays when you try to initiate a session with a ChangeMan ZMF started task, but no global record is found in the package master. This situation occurs when the package master is not initialized, or has been corrupted. This is a very serious problem, since the global record contains important system information.

Solution: ChangeMan ZMF does not start unless the package master is re-initialized or restored from the previous backup of the package master.

`CMN1012I` `INVALID COMMAND | Command entered was not valid`.

Explanation: Displays when ChangeMan ZMF does not recognize a command that you enter at the command line (COMMAND===>) line.

Solution: Enter the correct command.

`CMN1013A` `ENTER “NAME” STRING | The {``command``} command requires you to enter a NAME string`.

Explanation: Displays when you enter a List command that requires a second parameter, such as LOCATE, SELECT, or BROWSE, at the command line without a second parameter.

`CMN1014I` `MEMBER NOT FOUND | No entry found for member {``member name``}`.

Explanation: Displays when you try to edit, browse, stage, recompile, or relink a member of a partitioned data set that does not exist.

`CMN1015A` `PACKAGE NOT FOUND | {``package id``} participating package does not exist`.

Explanation: Displays when ChangeMan ZMF does not recognize a change package number that you enter while trying to create or update the Super/Complex change package information.

Solution: Either review the information entered and re-key the package number, or cancel and exit. See panels CMNCRT08 and CMNPGNL6 in the ChangeMan ZMF User’s Guide.

`CMN1016A` `ENTER “NEW NAME” STRING | The {``command``} command requires you to enter a NEW NAME string`.

Explanation: Displays when you enter an R (Rename) command at the command line on the Utility: Baseline Selections panel without entering a NEW NAME parameter.

Solution: Specify a NEW NAME string for the component. See the “Utility Requests” chapter in the ChangeMan ZMF User’s Guide.

`CMN1017A` `PACKAGE NOT FOUND | No participating package information found`.

Explanation: Displays when ChangeMan ZMF attempts to update the super/complex package’s participating package information, but the participating information does not exist.

`CMN1018A` `PACKAGE MEMO DELETED | {``package id``} package is in memo deleted status`.

Explanation: Displays when you enter a change package number that ChangeMan ZMF has been asked to delete, during an attempt to perform a function that requires an existing change package, such as updating change package information.

Solution: Remove the Delete Memo before the ChangeMan ZMF batch reports are run. See the “Deleting and Undeleting Packages” chapter in the ChangeMan ZMF User’s Guide.

`CMN1019A` `INVALID DATA SET NAME | Specify only the data set name; member name not allowed`.

Explanation: Displays when you specify a data set name with a member name, but the global administrator has set the global parameter for data set name only.

`CMN1020A` `ENTRY REQUIRED | At least one description line must be entered`.

Explanation: Displays when you try to exit the Create: General Information panel, CMNCRT02, without first making at least one entry in the Package Description field.

Solution: You can either make a valid entry, or cancel and exit the panel. See the ChangeMan ZMF User’s Guide for the General Information panel.

`CMN1021A` `OFM NOT GENERATED | Online Forms Manager data set parameters have not been generated`.

Explanation: Displays when you try to specify on Online Forms Manager data set, but the administrator has not created data set parameters.

`CMN1022A` `INVALID MEMBER NAME |The specified member name contains invalid characters`.

`CMN1023A` `MEMBER NAME LENGTH | The specified member name is too long (8 chars)`.

`CMN1024A` `INVALID OPTION | The entered option is not valid in browse mode`.

`CMN1025A` `ENTRY REQUIRED | At least one instruction line must be entered`.

Explanation: Displays when you try to exit the Create: Implementation Instructions panel, CMNCRT03, without first making at least one entry in the Implementation Instructions field.

Solution: You can either make a valid entry, or cancel and exit the panel. See the ChangeMan ZMF User’s Guide for the Create: Implementation Instructions panel.

`CMN1028A` `ENTRY REQUIRED | At least one affected application must be specified`.

Explanation: Displays when you try to exit the panel Create: Affected Projects (CMNCRT03) without first making at least one entry in the project field of the Projects panel.

Solution: You can either make a valid entry, or cancel and exit the panel. See the ChangeMan ZMF User’s Guide for the Create: Affected Projects panel.

`CMN1030A` `DUPLICATE TABLE ROW | Duplicate row found.`

Explanation: Displays when you enter the information twice, such as attempting to create two remote sites with the same site name.

`CMN1031A` `HLLX is inactive | This function relies on local exits which are currently unavailable. If problem persists contact Admin.`

Explanation: At least one HLL exit point is defined as active for the current function. HLLX is not active, the function cannot proceed.

`CMN1033A` `Invalid exit environment | HLL exit environment must be designated as either REXX (R) or LE (L).`

Explanation: Use a value of R or L for the HLL exit environment.

`CMN1034A` `Invalid exit name | HLL exit program/exec not found for function: {``function``}`

Explanation: The program/exec for this exit point cannot be found. Contact global admin.

`CMN1035A` `UNDEFINED APPLICATION | Undefined application. Contact Local Admin.`

Explanation: Displays when ChangeMan ZMF does not recognize a project mnemonic that you enter during package creation.

`CMN1036A` `HLL exit failure | HLL exit failure - see HLLX STC output for details {``exitname``}`

Explanation: The requested HLL exit program/exec has ended with a non-zero return code. Probably an execution error, details will be found in the HLLX started task output. Contact global admin.

`CMN1037A` `Ended by HLL exit | {``exitname``}`

Explanation: The program/exec called for exit point {*exitname*} has terminated the current function. The reason for this should be apparent from accompanying messages, if not contact global admin.

`CMN1038I` `INSTALL DATE WARNING | Install date has passed for this package ({``yyyy/mm/dd``}).`

Explanation: Displays when you attempt to stage a component from a package.

Solution: You should review the install calendar and select a new installation date.

`CMN1039A` `INSTALL DATE ERROR | Install date more than 364 days in future, not in calendar.`

Explanation: Displays when you enter a change package installation date more than 364 days in the future.

Solution: You should either review the calendar and select a different installation date, or cancel and exit.

`CMN1040A` `INSTALL DATE ERROR | Install date blocked. Contact Global Admin.`

Explanation: Displays when you enter a change package installation date that the administrator has restricted. No packages will be installed on this date.

Solution: You should select a different installation date, or talk with the global administrator about installation dates. See the ChangeMan ZMF User’s Guide for the panels CMNCRT07, CMNCRT06, CMNPRSTI, CMNONSTE, and CMNCLNDR. For date block information, see the “User Exits” appendix in the ChangeMan ZMF Administrator’s Guide.

`CMN1041A` `INSTALL DATE ERROR | Install date must be current or future.`

Explanation: Displays when you attempt to check in, check out, or stage a component into a package whose Install Date / From Time, adjusted for the Site Time Difference, has passed. Also displays in an ALL configuration when you attempt to enter a package Install Date / From Time in the Create Package or Update Package function when that date and time have already passed.

Solution: For check in, check out, or stage, use the Package Update function to advance the package or site Install Date / From Time to a date and time that have not passed. When this message is displayed in the Create Package or Update Package function in an ALL configuration, enter an Install Date / From Time that has not passed.

`CMN1042A` `INSTALL DATE ERROR | Install date must be current for unplanned changes.`

Explanation: Displays when you enter an unplanned change package installation date that is not today’s date.

Solution: You should review the information entered and select a current installation date, or cancel and exit. See the ChangeMan ZMF User’s Guide for the panels CMNCRT07, CMNCRT06, CMNPRSTI, CMNONSTE, and CMNCLNDR.

`CMN1043A` `INSTALL DATE ERROR | Install date selected is full.`

Explanation: Displays when you enter a change package installation date that is listed on the Planned Installation Calendar with a scheduled number of packages, and the maximum allowed number is the same.

Solution: You should review the calendar and select a different installation date, cancel and exit, or consult the global administrator about the installation dates. See the ChangeMan ZMF User’s Guide for the panels CMNCRT07, CMNCRT06, CMNPRSTI, CMNONSTE, and CMNCLNDR. For maximum date information, see the “Planned Installation Calendar” section in the ChangeMan ZMF Administrator’s Guide.

`CMN1044A` `INSTALL DATE ERROR | Install date must be in a Gregorian date format (YYYYMMDD).`

Explanation: Displays when you enter a change package installation date that is not in the same format as shown on the Planned Installation Calendar, such as YYYYMMDD.

Solution: You should review the calendar and reenter the installation date, or cancel and exit. See the ChangeMan ZMF User’s Guide for the panels CMNCRT07, CMNCRT06, CMNPRSTI, CMNONSTE, and CMNCLNDR.

`CMN1045I` `INVALID DATE RANGE | The FROM date is more current than TO date.`

Explanation: Displays when the FROM date range specified to limit package Query, List, or Log is more current than the TO date range.

`CMN1046A` `INSTALL DATE ERROR | Not enough lead time. Contact Global Admin.`

Explanation: Displays when you enter a change package installation date within a time range that the administrator has chosen to restrict. No packages are created with an installation date that does not allow for this amount of lead time.

Solution: You should select an installation date that is more distant than the one entered, or talk with the global administrator about installation dates. See the ChangeMan ZMF User’s Guide for the panels CMNCRT07, CMNCRT06, CMNPRSTI, CMNONSTE, and CMNCLNDR. For lead time information, see the “User Exits” appendix in the ChangeMan ZMF Administrator’s Guide.

`CMN1047I` `INVALID DATE FORMAT | Enter a valid Gregorian date.`

Explanation: Displays when an invalid Gregorian date is specified.

`CMN1048A` `INSTALL TIME ERROR | Invalid install time format; hours 00-23, minutes 00-59.`

Explanation: Displays when you enter a change package installation time that is not in the correct 24 hour format, such as HH:MM, where hours are 00-23 and minutes are 00-59.

Solution: You should review the information and reenter the installation time, or cancel and exit. See panels CMNCRT07, CMNCRT06, CMNPRSTI, CMNONSTE in the ChangeMan ZMF User’s Guide.

`CMN1049A` `UNDEFINED LOCAL PARMS | Undefined local parameters; configure local parameters.`

Explanation: Displays when you attempt a function for a change package whose governing project has not been fully configured.

Solution: The application administrator should review the project. See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN1050A` `UNDEFINED PROMO LIBRARY | Missing promotion library for this LEVEL; contact Local ADMIN.`

Explanation: Displays when you try to promote a change package whose governing project has had the next promotion level only partially configured.

Solution: The application administrator must configure each level of promotion in two steps. The second step (entering the actual promotion library data set names) has not been completed, or the library does not exist.

`CMN1051A` `UNDEFINED BASE LIBRARY | Missing baseline library for this LEVEL; contact Local ADMIN.`

Explanation: Displays when you try to check out a component to a change package whose governing project has had the specified baseline level only partially configured.

Solution: The application administrator must configure each level of baseline in two steps. The second step (entering the actual baseline library data set names) has not been completed or the library does not exist.

`CMN1052A` `INVALID LEVEL | Command valid for minus levels of stacked reverse delta only.`

Explanation: Displays when you, using the Browse Print facility, enter an ‘S’ to try to view a component that has no minus levels. Only components that have previous versions, or minus levels can be stored or viewed as stacked reverse deltas.

`CMN1053I` `LEVEL NOT FOUND | Level not found for this member, maximum level found is {``level``}.`

Explanation: Displays when you, using the browse baseline, checkout, or compare function, try to get a member of a level higher than the maximum level specified for stacked reverse deltas. For example, this message would display when you try to get a level 10, but the level only goes to 4.

`CMN1054A` `INVALID LEVEL | Scan for Librarian files is only valid for level 0.`

`CMN1055A` `UNDEFINED PROD LIBRARY | Undefined production {``project library``} library. Contact Local Admin.`

Explanation: Displays when you attempt any function for a change package whose governing project has not been fully configured.

Solution: The application administrator should review the project. See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN1056A` `INVALID INSTALL TIME | Install TO time must be greater than install FROM time.`

Explanation: You entered an Install TO time that was equal to or less than the specified FROM time. The TO time must be greater.

Solution: Enter an Install TO time that is greater than the specified FROM time.

`CMN1057A` `INSTALL DATE PASSED | Install date passed. Current time is {``yyyymmdd hh:mm:ss``} at {``sitename``}.`

Explanation: Displays for a site in the Create Package or Update Package functions when you enter an Install Date / From Time has already passed at that site, based on the Time Difference defined in the Site Information in Global Administration. The general rule is that you cannot enter an Install Date / From Time in the past.

Solution: Type an Install Date / From Time that has not already passed.

`CMN1058A` `HLLX conversation ended | The HLLX conversation has been interrupted, please begin the current function again.`

Explanation: The current function requires HLLX support and either HLLX has been terminated or the HLLX active exit table has been reloaded in-flight. Retry the function, if the problem persists contact global admin.

`CMN1059A` `HLLX internal error | Internal error processing HLLX call: {``exitname``}`

Solution: If problem persists contact Micro Focus Customer Care.

`CMN1060A` `UNDEFINED SITE INFO | Undefined site job card - Contact Local ADMIN.`

Explanation: Displays when you attempt any function for a change package whose governing project has not been fully configured.

Solution: The application administrator should review the project. See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN1061A` `UNDEFINED IP ADDRESS | Undefined site ip address. Contact Global Admin.`

`CMN1062A` `UNDEFINED SITE PORT | Undefined site port number. Contact Global Admin.`

`CMN1063A` `INVALID IP ADDRESS | IP Address is numeric with a format of nnn.nnn.nnn*.nnn.`

Explanation: Invalid IP address entered in Global Admin.

Solution: Enter a valid IP Address in the correct format.

`CMN1064A` `INVALID SITE PORT | Site port number must be numeric (nnnnn).`

Explanation: Invalid Site Port entered.

Solution: Enter a valid Site Port in the correct format.

`CMN1065A` `UNDEFINED APPLICATION | Undefined project - Contact Security ADMIN.`

Explanation: Displays when you try to perform a function that requires the entry of an application mnemonic, and the specified application has been configured within ChangeMan ZMF but not configured to the resident security system.

Solution: See the “Setting Up Security” section in the ChangeMan ZMF Administrator’s Guide.

`CMN1066I` `UNDEFINED SECURITY ENTITY | Security entity {``entity name``} undefined; contact security ADMIN.`

Explanation: Displays when you try to perform a function that requires the entry of a security entity that needs to be defined in the security system.

Solution: See the ChangeMan ZMF Installation Guide and ChangeMan ZMF Administrator’s Guide for instructions on how to set up security entities.

`CMN1070A` `APPLICATION RESTRICTED | Use of application name {``app name``} restricted by installation exit.`

Explanation: Displays when attempting to define an application that has been restricted due to installation exit CMNEX004.

Solution: See the “User Exits” section in the ChangeMan ZMF Administrator’s Guide.

`CMN1076A` `UNDEFINED BASE LIBRARY | Undefined baseline libraries. Contact Local Admin.`

Explanation: Displays when you try to perform a function that requires the entry of a project mnemonic, but the specified project has not been completely configured within ChangeMan ZMF.

Solution: See the “Configuring Baseline Libraries” section in the ChangeMan ZMF Administrator’s Guide.

`CMN1077A` `UNDEFINED LIBRARY TYPE | Undefined staging library type. Contact Local Admin.`

Explanation: Displays when you try to perform a function that requires the entry of a project mnemonic, but the specified project has not been completely configured within ChangeMan ZMF.

Solution: See the “Determining Staging Library Information” sections in the ChangeMan ZMF Administrator’s Guide.

`CMN1078A` `APPROVAL LIST UNDEFINED | Undefined approval list. Contact Local Admin.`

Explanation: Displays when you try to perform a function that requires the entry of a project mnemonic, but the specified project has not been completely configured within ChangeMan ZMF.

Solution: See the “Setting Up the Approval Process” section in the ChangeMan ZMF Administrator’s Guide.

`CMN1079A` `UNDEFINED LIBRARY TYPE | Undefined library type. Contact Local Admin.`

Explanation: Displays when you attempt a function for a change package whose governing project has not been fully configured.

Solution: The local application administrator should review the project. See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN1080A` `UNDEFINED SITE | Undefined site -{``project``}. Contact Local Admin.`

Explanation: Displays when you attempt a function for a change package whose governing project has not been fully configured.

Solution: The application administrator should review the project. See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN1081A` `PROCEDURE UNDEFINED | Undefined procedure for this language. Contact Local Admin.`

Explanation: Displays when you attempt any function for a change package whose governing project has not been fully configured.

Solution: The application administrator should review the project. See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN1082A` `LANGUAGE NAME UNDEFINED | Undefined language names. Contact Local Admin.`

Explanation: Displays when you attempt any function for a change package whose governing project has not been fully configured.

Solution: The application administrator should review the project. See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN1083A` `UNDEFINED REASON CODE | Undefined reason code. Contact Global Admin.`

Explanation: Displays when you attempt any function for a change package whose governing project has not been fully configured.

Solution: The global administrator should review the project. See the “Setting Up Global Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN1084A` `UNDEFINED PROMO LIBRARY | Undefined promotion libraries. Contact Local Admin.`

Explanation: Displays when you try to perform a function that requires the entry of a project mnemonic, but the specified project has not been completely configured within ChangeMan ZMF.

Solution: See the “Configuring Promotion Environments and Libraries” section in the ChangeMan ZMF Administrator’s Guide.

`CMN1085A` `PROCEDURE UNDEFINED | No procedures found for this library type.`

Explanation: The procedure to compress the staging library was not found. Each library type should have its own compress procedure.

`CMN1086A` `AUTHORIZATION FAILED | Function restricted. Contact Local Admin.`

Explanation: Displays when you try to select a function that is not authorized, such as global administration or package approval.

`CMN1087A` `AUTHORIZATION FAILED | Insufficient authority to access a protected data set.`

Explanation: Displays when you try to define or access a data set that is protected by a security system that allows limited access to the data set.

`CMN1088A` `AUTHORIZATION FAILED | {``data set``} is a protected data set.`

Explanation: Displays when you try to check out TO or stage FROM a data set that your TSOID is not authorized for.

`CMN1089A` `AUTHORIZATION FAILED | Undefined approval entity; contact Security Admin.`

Explanation: Displays when you try to approve a package whose governing project approvers were configured with ChangeMan ZMF, but were not configured to the resident security system. See the “Setting Up Security” section in the ChangeMan ZMF Administrator’s Guide.

`CMN1090A` `AUTHORIZATION FAILED | Application access denied. Contact Local Admin.`

Explanation: Displays when you try to create a package for a project that you have not been given create authority for, or tries to query a project that has been secured to prevent any TSOID without read authority from viewing the project’s packages. The application administrator must define all the project users to the resident security system.

`CMN1091A` `AUTHORIZATION FAILED | Unauthorized to selectively freeze or unfreeze package.`

Explanation: Displays when you, who are not one of the project’s approvers, try to selectively freeze or unfreeze components of a change package.

`CMN1092A` `AUTHORIZATION FAILED | Unauthorized package approver; contact Local ADMIN.`

Explanation: Displays when you, who are not one of the project’s approvers, try to approve a change package.

Solution: The unauthorized user may view the approval panel but cannot enter line commands (APPROVE, REJECT, and so forth).

`CMN1093A` `AUTHORIZATION FAILED | Unauthorized package promoter; contact Local ADMIN.`

Explanation: Displays when you, who are not one of the project’s promoters, try to promote a change package.

Solution: The unauthorized user can view the approval panel but cannot enter line commands (PROMOTE, DEMOTE, and so forth).

`CMN1094A` `UNAUTHORIZED ACCESS | {``entity name``} entity authorization required.`

Explanation: Displays when you, who are not on the TSOID list of a secured component, try to check out or stage the component.

Solution: The application administrator has the option to secure components to specific TSOIDs (generically) or to an entity to which TSOIDs will be associated.

`CMN1095A` `INVALID PACKAGE LEVEL | Package level must be simple or participating.`

Explanation: Displays when you try to perform a function on a change package that does not match the package level, such as trying to freeze a super/complex package or trying to update remote site information for a super/complex package.

`CMN1096A` `INVALID PACKAGE | Undefined package staging libraries.`

Explanation: Displays when you attempt any function for a change package whose governing project has not been fully configured.

Solution: The application administrator should review the project. See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN1097A` `INVALID PACKAGE | No approval list found for this package.`

Explanation: Displays when you attempt any function for a change package whose governing project has not been fully configured.

Solution: The application administrator should review the project. See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN1098A` `INVALID PACKAGE LEVEL | Package level must be participating.`

Explanation: Displays when you try to update the affected application information for a change package that is not participating.

`CMN1099A` `INVALID PACKAGE LEVEL | Package level must be complex or super.`

Explanation: Displays when you try to update super/complex package information, but the specified package ID is not for a super or complex package.

`CMN1100A` `INVALID PACKAGE | Undefined package staging libraries.`

Explanation: Displays when the participating package specified as part of the super/complex package does not have any staging library information.

`CMN1101A` `PROMOTION ERROR | There are no components to promote in this package.`

Explanation: Displays when you try to promote a change package that does not have any components. You can only promote packages that have components in them.

`CMN1102A` `UNDEFINED ENTITY | Security check failed, Undefined Entity {``entity name``}.`

Explanation: Displays when you specify an incorrect mnemonic that cannot be found in the package master.

`CMN1103A` `INVALID PACKAGE | Undefined package site information.`

Explanation: Displays when you attempt any function for a change package whose governing project has not been fully configured.

Solution: The application administrator should review the project. See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN1104A` `NO INFORMATION FOUND | Undefined package site information.`

Explanation: Displays when ChangeMan ZMF cannot access the package site information. This only happens when the ChangeMan ZMF environment has been converted from ALL to DEV or DEVPROD environment, and the package being accessed was created under the ALL environment.

`CMN1105A` `INVALID PACKAGE ID | Package {``package name``} is not a participating package.`

Explanation: Displays when you try to enter change package IDs that are not participating package types on the Super/Complex Information panels (CMNCRT08 or CMNPGNL6).

`CMN1106A` `AUTHORIZATION FAILED | TSOID not associated with the approval entity.`

Explanation: Displays when you try to approve a package, but your TSOID is not associated with the approval entity set up in the security system.

`CMN1107A` `BACKOUT ERROR | Package was not installed at this site.`

Explanation: Displays when you try to back out a change package at a remote site, but the package is not installed there.

`CMN1108A` `INVALID PACKAGE STATUS | Package ID must be in DEV status.`

Explanation: Displays when you try to enter change package IDs that are not in development (DEV) status on the Super/Complex Information panels (CMNCRT08 or CMNPGNL6).

`CMN1109I` `UPDATE CANCELED | Global Notification File update was canceled.`

Explanation: Displays when the global or application administrator cancels a GNF update, or when the administrator makes no changes after selecting the notification option.

`CMN1110A` `INVALID PACKAGE ID | Package {``participating package name``} is a part of super/complex package {``super/complex package name``}.`

Explanation: Displays when you try to enter change package IDs that are currently included in another super/complex package on the Super/Complex Information panels (CMNCRT08 or CMNPGNL6).

`CMN1111A` `UNDEFINED NOTIFY FILE | Global notification not defined. Contact the Global Admin.`

Explanation: Displays when the notification file is not defined in the global, application, or primary menu.

`CMN1112A` `ALLOCATION ERROR | Notification File not allocated. Contact Global Admin.`

Explanation: Displays from the global, application, or primary menu if space was never allocated for the notification file.

Solution: The global administrator should use ISPF commands outside of ChangeMan ZMF to allocate a data set for the notification file before defining it in Global Parameters (Part 2).

`CMN1113A` `INVALID PACKAGE ID | Package ID must be a planned permanent package.`

Explanation: Displays when you try to enter change package IDs that are not a planned permanent type on the Super/Complex Information panels (CMNCRT08 or CMNPGNL6).

`CMN1114I` `UPDATE SUCCESSFUL | Global Notification File was successfully updated.`

Explanation: Displays from global or application administration when an update to the file and the package master was successfully completed.

`CMN1115A` `UNDEFINED APPLICATION | Undefined application - contact Local Application ADMIN.`

Explanation: Displays when you try to create a change package for an application that ChangeMan ZMF does not recognize. This also displays if you enter a non-existing application name while trying to perform a ChangeMan ZMF function.

`CMN1116I` `NOTIFICATION UPDATED | Option-N file last updated {``date time``} last read {``date time``}.`

Explanation: Displays if the notification file has been updated since the last time you selected the option to browse the notification file. When the facility is first activated or when a new ChangeMan ZMF user first receives this message, UNKNOWN is displayed for last read date and time.

`CMN1117A` `RECORD FORMAT ERROR | Notify file must be FB, FBM, FBA, VB, VBA, VBM record format.`

Explanation: Displays when a global administrator has allocated the notification data set outside of ChangeMan ZMF with an unacceptable record format.

`CMN1118A` `DSORG ERROR | Notify file must be allocated as PDS or sequential data set.`

Explanation: Displays if a global administrator allocated the data set with an unacceptable data set organization.

Solution: The global administrator should reallocate the data set outside of ChangeMan ZMF as a PDS or sequential data set.

`CMN1119A` `MEMBER NOT FOUND | Notify File Member {``member name``} not found; contact Global Admin.`

Explanation: Displays from the global, application, or primary option menu if the notification file is a PDS, but no member name or a member name that does not exist was specified in the global parameters.

`CMN1120A` `INVALID JOB CARD | Invalid job card information.`

Explanation: Displays when you enter invalid job card information for any of the functions that perform batch jobs. ChangeMan ZMF checks every job card for basic standards; for example, if it starts with //jobname where //jobname cannot exceed 8 characters; or if you have typed a “without a corresponding”. This message can also display when CMNEX008 is activated. CMNEX008 includes the option to create your own message.

`CMN1121I` `NO MESSAGES | Global Notification File is empty.`

Explanation: Displays when you try to select Option N, but the notification file is empty.

`CMN1122A` `NO BASELINE STATS | No baseline statistics - possible regression`

Explanation: An MVS component was checked out from a baseline without ISPF statistics. Application administration parameter Validate Version During Staging is set to YES. The message is displayed when an edit-in-stage session is initiated on the package component. The message indicates that without baseline ISPF statistics, ChangeMan ZMF cannot determine if a change to the package component will result in a regression. The edit-in-stage session is allowed to proceed, and changes can be saved, but package audit will report a SYNCH1!.

Solution: Use Reset ISPF Statistics (ISPF 3.5) to create ISPF statistics for the baseline library member. Then edit the package component again, saving a change to update the ISPF statistics to avoid SYNCH13! in package audit.

`CMN1125A` `INVALID VALUE | Enter one of the listed values.`

Explanation: Displays when you enter an invalid response, such as entering X when the panel asks for a Yes or No confirmation.

`CMN1130A` `CONFLICTING INFORMATION | Affected application must be different from your application.`

Explanation: Displays when you try to enter an application mnemonic that is the same as the current change package’s governing project in the Create: Affected Projects panel (CMNCRT03) or the Update: Affected Projects panel (CMNPGNL5).

Solution: You should either make a valid entry, or cancel and exit the panel. See the ChangeMan ZMF User’s Guide for the panels mentioned above.

`CMN1135A` `NO SITE SELECTED | At least one site must be selected.`

Explanation: Displays when you try to exit the Create: Site Information panel (CMNCRT07) without first making at least one entry in the site field.

Solution: You should either make a valid entry, or cancel and exit the panel. See the ChangeMan ZMF User’s Guide for the panel CMNCRT07.

`CMN1140A` `ENTER REQUIRED FIELD | Enter required field at the cursor position.`

Explanation: Displays when you neglect to enter a required field.

Solution: You should either review the panel fields and re-key the entry, or cancel and exit the panel.

`CMN1141A` `Storage means mismatch | zFS/non-zFS conflict between baseline/promotion/production libraries`

`CMN1142A` `Library name error | Library name does not match zFS specification`

`CMN1143A` `Storage means mismatch | zFS/non-zFS conflict between libraries`

Explanation: You have attempted to stage from development a file that is incompatible with the staging library type that you are targeting. You cannot stage a PDS member into an zFS library type, and you cannot stage a zFS file into a PDS/E library type.

Solution: Specify a target library type that is compatible with the file you are staging from development.

`CMN1145A` `MAXIMUM SITE | Application restricted to sites listed.`

Explanation: Displays when you try to enter more sites (during package creation or update of remote site installation information) than the application was generated for.

`CMN1146I` `MAXIMUM SITE | Project Gen’d with baseline by site is restricted to one site.`

Explanation: Displays when a project defined with keep baseline by site has more than one site generated.

`CMN1147A` `LIBTYPE NOT FOUND | Target component in package {``package``} has undefined library.`

Solution: Verify LIBTYPE entry then resubmit.

`CNN1148A` `INVALID JOB SCHEDULER | Scheduling Dependencies not applicable to CMN job scheduler.`

Solution: Verify correct job scheduler has been entered.

`CMN1150I` `BROWSE ONLY | Browse only mode has been set.`

Explanation: Displays when ChangeMan ZMF presents a panel that does not allow any data entry, such as Browse Package Control Information CMNPGNL1). See the ChangeMan ZMF User’s Guide for the panel mentioned above.

`CMN1155I` `REQUEST CANCELED | Request for changes has been canceled.`

Explanation: Displays when you opt to cancel and exit from a panel.

`CMN1156I` `REQUEST CANCELED | Query request processing has been cancelled.`

`CMN1160I` `INFORMATION SAVED | {``package id``} participating package information saved.`

Explanation: Displays when you opt to save updates and exit the Update: Super/Complex Information panel (CMNPGNL6). See the ChangeMan ZMF User’s Guide for the panel mentioned above.

`CMN1161I` `INFORMATION SAVED | HLL exit definitions saved.`

Explanation: The information entered on the previous panel has been saved to the package master file.

`CMN1162I` `INFORMATION SAVED | User field names updated.`

`CMN1163I` `INFORMATION SAVED | {``package id``} control information saved.`

Explanation: Displays when the package control information is successfully updated. The new control information is saved in the package master.

`CMN1165I` `INFORMATION SAVED | {``package id``} package general information saved.`

Explanation: Displays when a you are finished updating the package general information in the UPDATE option (1.2). This data is stored in the package master.

`CMN1166I` `INFORMATION SAVED | {``package id``} package general description information saved.`

Explanation: Displays when you save updates and exits the Update: General Information panel (CMNPGNL2). See the ChangeMan ZMF User’s Guide for the panel mentioned above.

`CMN1167I` `INFORMATION SAVED | {``package id``} package installation instruction information saved.`

Explanation: Displays when the package installation instructions are successfully updated.

`CMN1168I` `INFORMATION SAVED | {``package id``} package scheduling information saved.`

Explanation: Displays when the package scheduling information is successfully updated.

`CMN1169I` `INFORMATION SAVED | {``package id``} package affected application information saved.`

Explanation: Displays when the package affected application information is successfully updated.

`CMN1170I` `INFORMATION SAVED | {``package id``} package site information saved.`

Explanation: Displays when you opt to save updates and exit the Update: Remote Site Information panel (CMNPRSTI). See the ChangeMan ZMF User’s Guide for the panel mentioned above.

`CMN1171I` `INFORMATION SAVED | {``package id``} user record information saved.`

`CMN1175I` `INFORMATION SAVED | {``package id``} package onsite coverage information saved.`

Explanation: Displays when a you opt to save updates and exit the Update: Onsite Information panel (CMNONSTE). See the ChangeMan ZMF User’s Guide for the panel mentioned above.

`CMN1180A` `NO COMPONENTS FOUND | No components found in the Package Master.`

Explanation: Displays when you try to stage from the package driven list, but there is no component information found in the package master for the specified package ID.

`CMN1181I` `MEMBER NOT FOUND | {``member name``} component was not found in this baseline library.`

Explanation: Displays when you attempt a checkout from the baseline library, but the listed member is not found.

`CMN1182A` `NO COMPONENTS FOUND | No {``component type``} components found for this package.`

Explanation: Displays when you try to selectively freeze or unfreeze a component type that does not exist within the specified package, such as source/load, copies, utilities, and so forth.

`CMN1184A` `NO COMPONENTS FOUND | No component(s) to list.`

Explanation: Displays when you try to query component information, but there are no components defined in the package master.

`CMN1185A` `NO DESIGNATED PROCS | No designated procedure found; Specify any valid procedure.`

Explanation: Displays when you enter a “?” in the Compiling Procedure field in the Stage: Build (CMNSTG04) or the Stage: Mass Build (CMNSTG05) panels. The component listed has not been set up with a designated procedure.

Solution: You should either choose any of the project’s procedures, or cancel and exit the panel. See the ChangeMan ZMF User’s Guide for the panels mentioned above.

`CMN1190A` `DESIGNATED PROC ENFORCED | Use the designated procedure assigned to this component.`

Explanation: Displays when you enter any procedure other than the designated one in the Compiling Procedure field (and options in fields labeled Compile Parms and Pgm Binder Parms) in the Stage: Build (CMNSTG04) or the Stage: Mass Build (CMNSTG05) panels. The component listed has been set up with a designated procedure and a force level of 2 (required at all times).

Solution: You can either enter the designated procedure and options, or cancel and exit the panel. See the ChangeMan ZMF User’s Guide for the panels mentioned above.

`CMN1200A` `EMPTY DATA SET | {``data set``} contains no members.`

Explanation: Displays when you request a member list, but the PDS is empty. This can occur during checkout, stage, utility requests, or recompile.

`CMN1205A` `DATA SET NOT ALLOCATED | {``data set``} already in use or not found.`

Explanation: Displays when you request a member list, and although the PDS exists, it has not been cataloged. This can occur during checkout, stage, utility requests, or recompile.

`CMN1210A` `DATA SET NOT FOUND | {``data set``} was not found.`

Explanation: Displays when you request a member list, but the PDS does not exist. This can occur during checkout, stage, utility requests, or recompile.

`CMN1215A` `ISPFILE NOT FOUND | {``data set``} ISPFILE data set was not found.`

Explanation: Displays when ChangeMan ZMF does not find your temporary ISPF file. Each time you sign onto ChangeMan ZMF, a temporary ISPF file is created. For some reason, this file has been deleted before you signed off, and ChangeMan ZMF cannot operate properly without your file.

Solution: You should log off ChangeMan ZMF and then log on again.

`CMN1220A` `DYNAMIC ALLOCATION ERROR | {``data set``} allocation RC; {``return code``}.`

Explanation: Displays when ChangeMan ZMF cannot access your temporary ISPF File. Each time you sign onto ChangeMan ZMF, a temporary ISPF file is created; and this message displays when the file cannot be used. The return code (RC) can be used to investigate the problem’s cause by reviewing the Dynamic Allocation Manual; or in some sites, the online ISPF tutorial.

Solution: You should log off ChangeMan ZMF and then log on again. For more information on how ChangeMan ZMF reallocates a data set, see the documentation for SEREX001 in the ChangeMan ZMF Customization Guide.

`CMN1230A` `Undefined LANGUAGE | {``language name``} language name undefined - contact ADMIN.`

Explanation: Displays when you try to check out or stage a source component with an unknown language name specified.

Solution: The application administrator must set up a list of all the language names that you are allowed to select.

`CMN1231A` `UNDEFINED PROCEDURE | {``procedure name``} undefined - contact ADMIN.`

Explanation: Displays when you try to check out or stage a source component using an unknown JCL procedure name specified.

Solution: The application administrator must set up a list of all the JCL procedure names that you are allowed to select.

`CMN1232A` `DELETE DISALLOWED | Exit 26 disallows member {``member name``} Delete; contact Administrator.`

Explanation: Displays when you specify a component to be deleted from a package that only administrators have authority to delete.

`CMN1233A` `DELETE DISALLOWED | Exit 26 disallows library type {``library type``} Delete; contact Administrator.`

Explanation: Displays when you specify a library type to be deleted from a package that only administrators have authority to delete.

`CMN1234A` `UNDEFINED LIBRARY TYPE | {``library type``} library type undefined. Exit 26. Contact Administrator.`

Explanation: Exit program CMNEX026 is attempting to allocate a staging library for a library type that is not defined for the application.

Solution: The ZMF administrator must do one of the following:

Define the library type in the application and specify baseline libraries.
Uncomment the code in exit program CMNEX026 at paragraph X26$0000 to bypass undefined library types.

`CMN1235A` `INVALID LIBRARY TYPE | {``library type``} library type undefined. Perform Checkout or contact ADMIN.`

Explanation: Displays when you try to check out or stage a source component with an unknown library type specified.

Solution: The application administrator must set up a list of all the library types that you are allowed to select.

`CMN1236A` `DELETE DISALLOWED | Exit 26 disallows delete of promoted components.`

Explanation: ChangeMan ZMF Exit 26 (CMNEX026), as coded, prevents deletion of a component if it is promoted or if it generates components that are promoted.

Solution: Determine that the component should be deleted; recode Exit 26 if necessary to allow deletion of promoted components. Refer to the ChangeMan ZMF Customization Guide.

`CMN1237A` `NO DBRMLIB | A DBRM libtype has not been defined. Contact Admin.`

Explanation: Verify a valid DBRM libtype for application exists; define and resubmit.

`CMN1238A` `Invalid lib. org | zFS components can only be recompiled, not rebound.`

Explanation: Displays when you try to rebind a zFS component.

Solution: Submit the zFS component for recompile instead.

`CMN1240A` `INVALID LIBRARY TYPE | {``library type``} is not a valid SOURCE library type.`

Explanation: Displays when ChangeMan ZMF requires a source library to be entered, but you enter a non-source library type.

`CMN1245A` `COMPONENT NOT FOUND | {``component``} does not exist.`

Explanation: Displays when you try to check out, compare, or recompile a component that does not exist in the baseline library.

`CMN1246I` `OVERLAY WARNING | Components listed may be overlaid if promoted.`

Explanation: Displays when you promote a change package or selectively promotes components of the same name as an already existing component. Continuing the promotion will overlay components of the same name.

Solution: To avoid overlaying components, you can cancel the promotion by pressing the END key [PF3]. To overlay a previously existing component, you can press Enter.

`CMN1250A` `COMPONENT NOT FOUND | {``component``} does not exist in the baseline or promotion library.`

Explanation: Displays when you try to check out or recompile a component that does not exist in the specified library.

`CMN1260A` `INVALID PACKAGE STATUS | Package must be in {``package status``} status.`

Explanation: Displays when you try to perform a function on a package with the wrong status, such as trying to freeze a package that is not in development (DEV) status or trying to delete a package that is not in DEV status.

`CMN1265A` `INVALID PACKAGE STATUS | Package must be in FRZ, REJ, INS, BAS, or TCC status.`

Explanation: Displays when you try to approve a package with an invalid status (DEV, DIS, BAK).

`CMN1270A` `INVALID PACKAGE STATUS | This package is already in {``status``} status.`

Explanation: Displays when you request a function that is not available for a package in its current status, such as attempting to freeze a frozen package.

Solution: You should review the package status descriptions. See the “Querying Change Packages” section in the ChangeMan ZMF User’s Guide.

`CMN1275A` `INVALID PACKAGE STATUS | Status must be BAS for ALL, DEV, or DEVPROD, and INS for PROD.`

Explanation: Displays when you try to back out a package whose current status is not INS or BAS.

Solution: See the “Backing a Change Package Out of Production” chapter in the ChangeMan ZMF User’s Guide for the rules and authority required.

`CMN1278A` `INVALID PACKAGE STATUS | Checkout to a frozen package is not allowed.`

Explanation: Displays when you try to check out a component to a change package whose current status is FRZ. Components must be checked out to packages that have a status of DEV.

`CMN1280A` `WRONG ENVIRONMENT | Change Man must be configured for {``variable``} environment.`

Explanation: Displays when you try to revert a package with REJ or FRZ status, but the environment is not set to DEV, ALL, or DEVPROD. It also displays when the administrator tries to configure remote site information with the environment set to ALL or PROD.

`CMN1282A` `RESTRICTED ENVIRONMENT | Change Man is licensed for {``environment``} only.`

`CMN1295A` `INVALID REQUEST | The requested action selected is invalid.`

Explanation: Displays when you enter an invalid command at the command line. Displays in numerous ChangeMan ZMF panels.

Solution: Refer to the ChangeMan ZMF tutorial for the correct commands. The tutorial is accessed on line by pressing the [PF1] key.

`CMN1300A` `UNDEFINED GLOBAL PARMS | Undefined global parameters. Contact Global Admin.`

Explanation: Displays when you attempt a function, and ChangeMan ZMF has not been fully configured.

Solution: The global administrator should review the “Setting Up Global Parameters” section in the ChangeMan ZMF Administrator’s Guide.

`CMN1301A` `Update error | Staging datasets aging value invalid.`

Explanation: The value in AGING - STAGING DATASETS violates a rule about the relationship between values in AGING fields or a rule about the relationship between AGING values in global and application administration.

Solution: Search for AGING - STAGING DATASETS in global and application administration in the ChangeMan ZMF Administrator’s Guide for a full description of aging package staging libraries.

`CMN1302A` `Update Error | Package aging value invalid.`

Explanation: The value in AGING - INSTALLED PACKAGES violates a rule about the relationship between values in AGING fields or a rule about the relationship between AGING values in global and application administration.

Solution: Search for AGING - INSTALLED PACKAGES in global and application administration in the ZMF Administrator’s Guide for a full description of aging packages.

`CMN1303A` `Update Error | Component history aging value invalid.`

Explanation: The value in AGING - COMPONENT HISTORY violates a rule about the relationship between values in AGING fields or a rule about the relationship between AGING values in global and application administration.

Solution: Search for AGING - COMPONENT HISTORY in global and application administration in the ZMF Administrator’s Guide for a full description of aging component history.

`CMN1305A` `UNDEFINED SITE | Undefined site information. Contact Global Admin.`

Explanation: Displays when you attempt a function, and ChangeMan ZMF has not been fully configured.

Solution: The global administrator should review the “Setting Up Global Parameters” section in the ChangeMan ZMF Administrator’s Guide.

`CMN1306A` `NO ACTIVE SITES | Sites must have target production datasets defined.`

Explanation: This message is displayed when you attempt to create a package in a DP environment in an application where there are no sites defined that are eligible for an installation.

Solution: In a DP environment, each application must contain at least one site defined either as a Site whose Site Name is the same as the Site Node Name in Global Administration Parameters, or as a Site for which production libraries have been defined.

Note

If you want to use a DP environment like an A (ALL) environment without defining production libraries, define a Global Site with a Site Name that is the same as the Site Node Name in Global Application Parameters and a Logical Unit/System Name that is the same as the Logical Unit Or System Name in Global Application Parameters. Define this site in Application Administration for each application.

`CMN1307A` `UNDEFINED SITE | Site {``site``} undefined for application {``appl``}.`

Explanation: This message is displayed when a site has not been assigned for the application you are accessing.

Solution: A site must be defined for each application in Global Admin.

`CMN1310A` `UNDEFINED TRANSMISSION | Undefined transmission type. Contact Global Admin.`

Explanation: Displays when you attempt a function, and ChangeMan ZMF has not been fully configured.

Solution: The global administrator should review the “Setting Up Global Parameters” section in the ChangeMan ZMF Administrator’s Guide.

`CMN1315A` `UNDEFINED LIBRARY TYPE | {``nnn``} is an undefined library type or no like-load library type is defined.`

Explanation: Displays when you run the Baseline Analyzer Report and you do not have a LOD or like-load library type defined in the application, or when you run the report in batch and you specify a non-load library type in the TYPE= control statement.

Solution: Ensure that you have at least one like-load library type defined in the application, or ensure that you specify a like-load library type in the TYPE= control statement in a batch execution of the report.

`CMN1316A` `PRODUCTION LIBTYP NOTDEF | Baseline library type {``nnn``} not defined as Install in Production.`

`CMN1317A` `NO DB2 LIBRARY TYPES | No DB2 Library Types have been defined by global ADMIN`

`CMN1318A` `NO DB2 LIBRARY TYPES | No DB2 Library Types have been defined by application ADMIN`

`CMN1319A` `DUPLICATE LOGICAL NAME | DB2 logical subsystem name must be unique`

Explanation: Displays when you attempt to exit from the DB2 Logical Subsystems panel where a logical subsystem name has been included in more than one panel row.

Solution: Prior to ChangeMan ZMF 5.3, DB2 logical subsystem names had to be unique within combinations of Logical Name / DB2 Subsys / Site. Starting with Version 5.3, DB2 logical subsystem names must be unique across all physical subsystems.

`CMN1320A` `UNDEFINED LANGUAGE NAME | Undefined language name. Contact Global Admin.`

Explanation: Displays when you attempt a function, and ChangeMan ZMF has not been fully configured.

Solution: The global administrator should review the “Setting Up Global Parameters” section in the ChangeMan ZMF Administrator’s Guide.

`CMN1325A` `UNDEFINED PROCEDURE LIST | Undefined procedure list. Contact Global Admin.`

Explanation: Displays when you attempt a function, and ChangeMan ZMF has not been fully configured.

Solution: The global administrator should review the “Setting Up Global Parameters” section in the ChangeMan ZMF Administrator’s Guide.

`CMN1326I` `SCHEDULER UNDEFINED | Undefined scheduling system. Contact Global Admin.`

Explanation: Displays when you try to select a scheduling system, during package creation or update, that was not globally defined.

`CMN1327I` `SCHEDULER UNDEFINED | Scheduler not defined in Application Admin.`

`CMN1330A` `INVALID PACKAGE TYPE | Package type must be planned or unplanned permanent.`

Explanation: Displays when you try to back out a temporary package.

`CMN1335A` `INVALID PACKAGE TYPE | Package type must be planned permanent.`

Explanation: Displays when you try to promote an unplanned package.

`CMN1340A` `VALUE OUT OF RANGE | Enter a numeric value from ‘1’ to ‘999999’.`

Explanation: Displays when you enter a package ID with nonnumeric characters in the numeric portion. Package IDs are made up of a 3- to 4-character project mnemonic and a 6-digit number.

`CMN1345A` `VALUE OUT OF RANGE | Enter a numeric value from ‘1’ to ‘10’.`

Explanation: Displays when you, who are trying to specify a baseline level, enters a number outside the acceptable range.

`CMN1360A` `MUST BE NUMERIC | Enter a numeric character (0-9).`

Explanation: Displays when you enter a non-numeric value for a field requiring a numeric value.

`CMN1370A` `INVALID MEMBER NAME | Member name {``component``} not valid for partitioned data set.`

Explanation: Displays when you, who are trying to specify a member name, enters a name with an unacceptable format, such as one starting with a number.

`CMN1371A` `INVALID MEMBER NAME | Member name is not valid for sequential data set.`

Explanation: Displays when you try to specify a member name for a sequential data set. Sequential data sets do not have members. The name is one character string.

`CMN1375I` `UPDATE SUCCESSFUL | Global DB2 general parameters updated successfully.`

`CMN1376I` `UPDATE SUCCESSFUL | Application DB2 general parameters updated successfully.`

`CMN1377I` `UPDATE SUCCESSFUL | Global DB2 library subtypes updated successfully.`

`CMN1378I` `UPDATE SUCCESSFUL | Application DB2 library subtypes updated successfully.`

`CMN1379A` `INVALID TYPE | Component type cannot be masked with a command entered.`

Explanation: Remove masking.

`CMN1380I` `NO MATCHING | Member pattern produced no matching members.`

Explanation: Displays when you try to view a member list using a pattern that does not fit any of the members.

`CMN1381A` `INVALID MEMBER | Member name cannot be masked with a command entered.`

Explanation: Displays when you try to select a member name using CMN* in the command. Member names cannot be masked using CMN*.

`CMN1382A` `INVALID PATTERN | Question mark cannot be next to asterisk.`

Explanation: Displays when you try to view a member list using an invalid pattern.

`CMN1383A` `INVALID BASE LEVEL | Baseline level cannot be blank.`

Explanation: Displays when you leave blank the level of a baseline library (0 to 999) or promotion library (0 to 999) while trying to browse that library.

`CMN1384A` `INVALID PATTERN | The specified pattern is invalid. Ex: CMN*, CMN??, CMNA??RV.`

Explanation: Displays when you try to view a member list using an invalid pattern.

`CMN1385A` `INVALID COMMAND | Invalid command for a load library type, use only B, C, or H.`

Explanation: Displays when you try to perform a browse action on a load component other than browse (B), copy (C), or history (H) review of the component. These are the only valid browse actions.

`CMN1386A` `NO MEMBERS FOUND | No members found from the results of the scan.`

Explanation: Displays when no members can be found for the scan criteria you specified.

`CMN1387A` `INVALID DSORG | Load libraries are not supported by scan facility.`

Explanation: Displays when you try to scan a data set organization (DSORG) that ChangeMan ZMF does not support.

`CMN1388I` `NO RELATIONSHIP FOUND | No related load modules found for {``member name``}.`

Explanation: Displays when a SRC to LOD relationship does not exist. CMNSR2LD is the panel where the source member is requested.

Solution: You should spell the requested library type correctly.

`CMN1389I` `LCMD NOT APPLICABLE | Source to load relationship command only applies to source.`

Explanation: Displays when the SRC to LOD relationship command was attempted on a non-SRC type.

Solution: You should check the project library configuration to make sure the requested library type is SRC or like SRC.

`CMN1390A` `COMMAND INVALID | Line Command: S - Select.`

Explanation: Displays when you enter an invalid line command.

`CMN1391I` `NO MATCHING LEVEL | Member pattern produced no matching members with level specified.`

Explanation: Displays when you, who are using the Browse Baseline function, try to get a member using a pattern that is cannot be used with the level specified for Stacked Reverse Deltas.

Solution: For example, this message would display when you try to use ABC* for level 10, but ABC* is not valid for this level.

`CMN1392I` `LCMD NOT APPLICABLE | Component TSOID work records not stored. Contact CMN Administrator.`

Explanation: Displays when you attempt to use the UL line command on the Stage: package Components panel when your administrator has not enabled component work records in global and application administration.

Solution: The UL line command displays component work records only when your administrator has enabled component work records in global and application administration.

`CMN1393A` `INVALID BASE NAME | Baseline dataset name cannot be blank.`

Explanation: Displays when you leave a baseline library data set name line blank on the Baseline Configuration Part 2 of 2 panel in application administration.

Solution: Either define fewer baseline levels on the Baseline Configuration Part 1 of 2 panel, or type a baseline data set name in every line on the Baseline Configuration Part 2 of 2 panel. You should use line command V on every baseline data set name entered on the Baseline Configuration Part 2 of 2 panel to verify that the name you typed is a valid data set name to avoid JCL errors in install jobs.

`CMN1395A` `COMMAND INVALID | Valid line commands for frozen components are: B, BA,BD,BL,H,SL,V,VL.`

Explanation: Displays when components within a package in FRZ (Freeze) cannot be edited or staged.

Solution: You should choose from the following valid line commands:

H - display the component’s history.
B - browse the component.
BA - browse the component’s activity file. The component’s activity file must be checked out along with the member in order to be browsed.
BD - browse the component’s general description. The activity file must be checked out with this member in order for the General Information of this member to be browsed.
SL - display the load relationship of a requested source member.
V - Browse the component in edit mode.

`CMN1396A` `COMMAND INVALID | Recompiled component frozen. Valid commands are: BD,BL,H,SL,VL.`

`CMN1397I` `NO WORK RECORD FOUND | No component userid work record found for {``component-name``}.`

`CMN1400I` `SESSION ESTABLISHED | Session established with Change Man started task.`

Explanation: Displays during all ChangeMan ZMF batch processing jobs.

`CMN1410I` `SESSION TERMINATED | Session terminated with Change Man started task.`

Explanation: Displays during all ChangeMan ZMF batch processing jobs.

`CMN1420A` `NO RELATED INFORMATION | No component history related to this request.`

Explanation: Displays when you request to view a component’s historical information during stage or query, but there is no history for the component.

`CMN1430I STAGING LIBRARY DEFERRED | Check out or stage {``library type``} component to allocate it.`

Explanation: Displays when you try to process a library type that was deferred during package creation. Deferred staging library type can only be allocated when it is checked out or staged.

`CMN1435I` `BASELINE LIB UNDEFINED | {``library type``} baseline library undefined; contact Local ADMIN.`

Explanation: Displays when you try to process a library type that does not have an associated baseline library defined.

`CMN1440I` `NO {``library type``} LIBRARY FOUND | No staging or baseline {``library type``} library found or defined.`

Explanation: Displays when you try to process a library type that does not have an associated staging or baseline library defined. (This is probably a new library type added to the project after the package was created.)

Solution: Before you can add a new library type to the package, the package must be either checked out or staged.

`CMN1445I` `REQUIRED FIELD MISSING | The SORT command requires specification of the field to sort.`

Explanation: Displays when you enter a SORT LIST command at the command line without a field name parameter specified.

`CMN1450I` `INVALID KEYWORD | {``list command``} command contains an invalid keyword. Reenter command.`

Explanation: Displays when you enter a LIST command at the command line with an unknown parameter.

`CMN1455I` `UNDEFINED SORT FIELD | No entry found in ChangeMan ZMF ISPF sort table.`

Explanation: Displays when you enter a SORT LIST command at the command line for a field that is either entered incorrectly or undefined.

`CMN1460I` `DATA SET RECOVERED | Data set {``data set``} recovered.`

Explanation: Displays when the staging or development library being edited in ChangeMan ZMF has been successfully recovered, and the related package staging information is updated accordingly before a system failure occurs.

`CMN1465I` `RECOVERY CANCELLED | Data set {``data set``} recovery cancelled.`

Explanation: Displays when you opt to cancel recovery of the staging or development data set being edited before a system failure occurs.

`CMN1470I` `LOGICAL DB2 UNDEFINED | Undefined application DB2 logical subsystem; contact Local ADMIN.`

Explanation: The application administrator should define the logical DB2 subsystem desired. This is accomplished in the DB2 option (I) of the Application Administration Menu.

Solution: You should be sure to specify the correct mnemonic.

`CMN1475I` `ACTIVE LIB UNDEFINED | Undefined application DB2 active library; contact Local ADMIN.`

Explanation: The application administrator must define the ACTIVE libraries in the ACTIVE option under the DB2 option (I) of the Application Administration Menu.

`CMN1476A` `INVALID ACTIVE TYPE | A - Invalid DB2 active library type; valid values are B Bind or S SQL.`

Explanation: Displays when you enter an invalid DB2 active library type.

Solution: Enter a valid active type.

`CMN1477A` `DUP DB2 LIBRARY | Duplicate DB2 active library definition.`

Explanation: Displays when you enter a DB2 active library definition that is already defined.

`CMN1480I` `DB2 SUBSYSTEM UNDEFINED | Undefined DB2 subsystem identifications; contact Global ADMIN.`

Explanation: To perform the LOGICAL or ASSIST options under the IMPACT option, the application administrator should define the DB2 physical subsystems in the application administration parameters.

`CMN1490I` `ALLOCATION ERROR | Unable to allocate library type {``library type``}.`

Explanation: Displays when a staging library is allocated. Usually, when the started task sends this message to you, it is because an allocated data set already exists in the library.

`CMN1491E` `PACKAGE MASTER CONTENTION | Possible package master contention. Please resubmit request.`

Explanation: Displays when another job or user is attempting to update the same package master record concurrently.

Solution: Try to determine who else is working with this file, then resubmit your job. If this condition persists, talk to your ChangeMan ZMF administrator.

`CMN1492A` `MEMBER LIMIT EXCEEDED | member limit ({``limit``}) exceeded.`

Explanation: The number of members is limited to a limit of limit, and that has been exceeded.

`CMN1495I` `PACKAGE MASTER I/O ERROR | I/O error on package master request.`

Explanation: Displays when a READ, WRITE, or UPDATE is performed on the package master and a VSAM file anomaly is encountered.

Solution: You should attempt an IDCAMS Repro of the file or use a VSAM file utility (such as VSAM Works) to correct the file anomaly. The started task messages provide additional information.

`CMN1496I` `PACKAGE MASTER I/O ERROR | Package master error on {``key``}.`

Explanation: Displays when an I/O error occurs on the package master. The I/O function and the record key are displayed for help in problem resolution.

Solution: You should attempt an IDCAMS Verify and/or Repro of the file or use a VSAM file utility (such as VSAM Works) to correct the file anomaly. The started task messages provide additional information.

`CMN1497I` `PACKAGE MASTER I/O ERROR | Package master error on {``key``}. Retry will be attempted.`

Explanation: Displays when an I/O error occurs on the package master. The I/O function and the record key are displayed for help in problem resolution. Based on the VSAM return code, the program has determined that a retry may complete successfully, and will be attempted.

`CMN1500I` `LOG FILE I/O ERROR | Unable to process LOG file information.`

Explanation: This general error message displays when the LOG file is updated.

Solution: You should reinitialize the LOG file. The Started Task messages provide additional information.

`CMN1505I` `MEMBER LEVEL ERROR | Get member designated procedure service error.`

Explanation: Displays during compiling, recompiling, or relinking. The issue might stem from a member with an incorrect compiling procedure.

Solution: The application administrator should refer to the compiling procedures defined in option C under the Application Administration Menu.

`CMN1510I` `MEMBER LIST ERROR | Get member directory information service error.`

Explanation: Displays when the library is invalid. You can browse the contents of the requested PDS during checkout, stage, and compare.

Solution: You should look at the data set in an ISPF session (option 3.4) to examine the contents for validity. The data set might have been specified as a PDS when the actual baseline data set is a SEQ data set.

`CMN1515I` `MVS OPERATION ERROR | MVS operator console command service error.`

Explanation: Displays when a VSAM get read sequential error occurs that is internal to ChangeMan ZMF. Solution: You should contact Micro Focus Customer Care.

`CMN1520I` `REMOTE SITE ERROR | Remote sites are prohibited for the ‘ALL’ environment.`

Explanation: Displays when you are in an ALL environment and attempt a task involving remote sites, but the task is prohibited for an ALL environment.

`CMN1521I` `INSTALL SITE ERROR | Install sites are not defined for ‘ALL’ and 'P' environments.`

Explanation: Displays when you request a list of install sites for an ALL or P environment. Install sites can only be defined for a D or DP environment.

`CMN1525I` `PROCESS ERROR | Package is in the process of being frozen.`

Explanation: Displays if a batch freeze is in the process of freezing a package, and you try to perform an online function on the same package.

`CMN1526I` `PROCESS ERROR | Package has an outstanding approval.`

Explanation: Displays if you attempt to perform an online function on a package that has a batch approval running, or has already been approved.

`CMN1527I` `PROCESS ERROR - Package installation JCL build outstanding.`

Explanation: You can not approve a frozen package until installation JCL build is complete.

`CMN1528I` `BUILD INSTALL SUBMITTED | Package installation JCL build resubmitted.`

`CMN1530I` `INVALID PACKAGE STATUS | Package ID must be in {``status``} status.`

`CMN1531A` `AUDIT IN PROGRESS | Package {``package id``} is locked for audit by {``userid``}.`

Explanation: You have attempted to work with a package or a component in a package that is locked for package audit.

A package is locked for audit when the LOCK PACKAGE field is selected on the Audit Change Package panel (CMNAUDIT), the audit job is submitted, and program CMNAD000 executes at the beginning of the job. The lock is reset when program CMNAD500 runs at the end of the job.

A package may remain locked for audit because:

The package audit job is still running.
The package audit job failed after program CMNAD000 executed at the start of the job.

Solution: If the audit job failed, fix the problem, reset the audit lock, and resubmit the audit job. To reset the audit lock, type YES in the RESET LOCK field on the Audit Change Package panel (CMNAUDIT) and press ENTER. (The package audit job is not executed.)

`CMN1532A` `ENQUE FAILED | Enque {``nnn``} failed RC={``rc``} Try later.`

Explanation: Failed to enqueue complex package or request package to lock during an audit.

Solution: Retry; if the error persists contact Micro Focus Customer Care.

`CMN1533I` `PACKAGE(S) UNLOCKED | Audit package lock reset.`

`CMN1534I` `LOCK BYPASSED | Package {``nnn``} lock bypassed by admin rule.`

...

`CMN1535I` `PROCESS ERROR | Install JCL build request was never submitted or has completed.`

`CMN1600 ChangeMan ZMF LIBDEF`

`CMN1600I ISPF LIBDEF Dynamic DD allocation not allowed for DDNAME {``ddname``}`

Explanation: This message is displayed when you have performed a LIBDEF service for the indicated DDNAME, the global administrator has set the LIBDEF validation option for the indicated DDNAME, and the LIBDEF allocation is associated with an ISPF DDNAME which is not defined in the started task JCL.

Solution: You are prevented from building execution JCL to submit a job. You can logoff and logon to ChangeMan ZMF to establish a new ISPF environment.

`CMN1615I Pmast read of global record failed during LIBDEF validity check`

Explanation: This message is displayed when a service is performed to read the global generation parameters record from the package master for LIBDEF validation processing, and the read was unable to complete due to an I/O error. If errors continue contact the global administrator.

`CMN1620I ISPF query service for LIBDEF information failed with RC={``rc``}`

Explanation: This message is displayed when:

the global administrator has set the LIBDEF validation option,
you are performing some ChangeMan ZMF activity that builds execution JCL to submit a job, and
the QLIBDEF service was called to obtain the current LIBDEF information in effect for you. The Query LIBDEF service was unable to complete successfully and you are prevented from building execution JCL to submit a job.

Solution: This generally indicates a problem in the ISPF environment which should be reported to the systems programmer.

`LBDFSM01 ISPF library error.`

`LBDFSM05 Libdef service error.`

CMN2000 Package Build

`CMN2000A` `NO INFORMATION FOUND | No super/complex information found for this package.`

Explanation: Displays when you request to query a package that is not a super/complex type, or has not had the participating package information entered yet.

`CMN2020A` `NO STAGING LIB’S FOUND | No staging libraries found to be compressed.`

Explanation: Displays when you request to compress a package that is not a simple or participating type, or has had its staging libraries deleted.

CMN2030 Super/Complex Package

`CMN2030I` `CLOSE ERROR | Package {``participating package name``} is still in motion not BAS or TCC status.`

Explanation: Displays when you try to close a participating package that is still in motion (does not have a status of BAS or TCC).

`CMN2040I` `CLOSE ERROR | Package {``super/complex package name``} is already closed, status CLO.`

Explanation: Displays when you try to close a super/complex package that is already closed.

`CMN2050I` `CLOSE ERROR | Package {``super/complex package name``} is not in OPN status.`

Explanation: Displays when you try to close a super/complex package that is not in OPN status.

`CMN2055I` `APPROVAL STARTED | Package {``participating package name``} approval process started, contact administrator.`

`CMN2060I` `PACKAGE CLOSED | Package {``super/complex package name``} has been closed, status changed to CLO.`

Explanation: Informs you that a super/complex package has been closed and its status changed to CLO.

`CMN2065I` `PACKAGE OPENED | Package {``super/complex package name``} has been reopened, status changed to OPN.`

Explanation: Informs you that a super/complex package has been reopened and its status changed to OPN.

`CMN2070I` `OPEN ERROR | Package {``super/complex package name``} is already opened, status OPN.`

Explanation: Displays when you try to open a super/complex package that is already open.

`CMN2075I` `OPEN ERROR | Package {``super/complex package name``} is not in CLO status.`

Explanation: Displays when you try to open a super/complex package that is not in CLO status.

`CMN2080I` `OPTION NOT ALLOWED | Not authorized to perform this function; contact Administrator.`

Explanation: Displays when you try to perform a function without having authorization to perform it.

`CMN2085I` `NO PARTICIPATING | Package {``super/complex package name``} contains no participating packages.`

Explanation: Displays when you try to remove a participating package, but the super/complex package contains no participating packages.

`CMN2086I` `NO PARTICIPATING | Package {``super/complex package name``} contains no participating packages in motion.`

`CMN2090I` `REMOVAL NOT ALLOWED | Package {``participating package name``} has invalid status {``participating package status``} contact Administrator.`

Explanation: Displays when you try to remove a participating package from the super/complex package list, but the package has an invalid status. Default status for REMOVE is DEV, REJ, DEL, or BAK.

`CMN2095I` `ADD NOT ALLOWED | Package {``participating package name``} has invalid status {``participating package status``} contact Administrator.`

Explanation: Displays when you try to add a participating package to the super/complex package list, but the package has an invalid status. Default status for ADD is DEV, REJ, or BAK.

CMN2100 Package Create

`CMN2100I` `{``package id``} CREATED | {``package id``} change package has been created.`

Explanation: Displays when ChangeMan ZMF completes the creation of a new change package.

Solution: See the “Creating a Change Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN2105A` `CREATE CANCELLED | The creation of new package has been cancelled.`

Explanation: Displays when you opt to cancel and exit from the series of panels used to create a new change package.

Solution: See the “Creating a Change Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN2110A` `NO SITE SELECTED | At least one site must be selected.`

Explanation: Displays when you try to exit the Create: Remote Site Information panel (CMNCRT07) without first making at least one entry in the Site field.

Solution: You can either make a valid entry or cancel and exit the panel. See the ChangeMan ZMF User’s Guide for the panel mentioned above.

`CMN2120A` `APPLICATION RESTRICTED | Application may not create super/complex packages.`

Explanation: Displays when you try to create a super/complex change package for a project that is not allowed to create that type of package.

Solution: See the “User Exits” appendix in the ChangeMan ZMF Administrator’s Guide.

`CMN2130A` `COPY FORWARD RESTRICTED | Package to copy forward must be Super or Complex.`

`CMN2135A` `COPY FORWARD RESTRICTED | Package to copy forward must be Simple or Participating.`

`CMN2140A` `INVALID APPLICATION | Application must be different from your application.`

Explanation: Displays when you try to enter the current package’s governing project mnemonic on the Affected Project panels (CMNCRT05) or (CMNPGNL5).

`CMN2145A` `TEMP. CHANGES DISALLOWED | Temporary changes disallowed. Contact Local Admin.`

Explanation: Displays when you try to create a temporary change package for a project that restricts that type of package.

Solution: See the “Setting Application Parameters” section in the ChangeMan ZMF Administrator’s Guide.

`CMN2160A` `LINE COMMAND RESTRICTED | Deferred allocation was not specified for this library type.`

Explanation: Displays when you try (during package creation) to defer the allocation of a staging library type that the application administrator has set up as required.

Solution: See the “Determining Staging Library Information” sections in the ChangeMan ZMF Administrator’s Guide and ChangeMan ZMF User’s Guide for panel CMNCRT09.

`CMN2170A` `CREATE ERROR | Error encountered while creating package {``package``}.`

Explanation: Displays when there is a problem creating physical components of a package.

Solution: See SERPRINT for other messages that provide details. For example: CMNC020I CMNVRLIO VCA=19300000,USER=$PB001 , File Full F1=MASTER,F2=WRITE,KEY=PAT00000507400032000,RC=000C,FDBK=001C

`CMN2181A` `CREATE ERROR | Package number supplied is zero or blank.`

Explanation: You must supply a valid package number.

`CMN2184I` `CREATE DISALLOWED | Your ID is not authorized to create change packages.`

Explanation: Displays when you try to create a change package and security protecting package create is defined, and your ID does not have authority.

CMN2200 Utility Request

`CMN2200A` `NO INFORMATION FOUND | No rename or scratch information found for this package.`

Explanation: Displays when you request to review or update utility information driven by the contents of a change package that has not yet had such information entered. See the “Utility Requests” chapter in the ChangeMan ZMF User’s Guide.

`CMN2210I` `SCRATCH INFO. SAVED | {``component``} scratch information saved.`

Explanation: Displays when you opt to save updates and exit the Utility: Baseline Member List (CMNUTL01) panel or Utility: Change Package Driven List (CMNUTL02) panel.

Solution: See the ChangeMan ZMF User’s Guide for the panels mentioned above.

`CMN2215I` `NO RELATED SCRATCHES | {``component name.component type``} scratch saved, no prior baseline package found.`

Explanation: Displays when no prior baselined package is found in the history record during scratch/rename. No related scratch requests are generated.

`CMN2220I` `RENAME INFO. SAVED | {``component``} rename information saved.`

Explanation: Displays when you opt to save updates and exit the Utility: Baseline Member List (CMNUTL01) or Utility: Change Package Driven List (CMNUTL02) panel.

Solution: See the ChangeMan ZMF User’s Guide for the panels mentioned above.

`CMN2230A` `COMPONENT NOT FOUND | Component to rename or scratch not found in baseline library.`

Explanation: Displays when you try to set up a utility request for a component that does not exist in the project’s baseline library.

Solution: See the “Utility Requests” chapter in the ChangeMan ZMF User’s Guide.

`CMN2231A` `INVALID COMPONENT NAME | Component mask not allowed in scratch/rename.`

Explanation: Displays when you have entered an invalid component name and included a member pattern (*).

Solution: Enter a valid component name without a member pattern.

`CMN2240A` `COMPONENT EXISTS | {``component``} rename component already exists in the baseline library.`

Explanation: Displays when you try to set up a rename utility request for a component, and the new name is already listed as a component in the project’s baseline library.

Solution: See the “Utility Requests” chapter in the ChangeMan ZMF User’s Guide.

`CMN2250A` `COMPONENT IN PACKAGE | {``component``} exists in the package. Cannot scratch/rename existing component.`

Explanation: Displays when you try to scratch or rename an existing component in a package.

`CMN2260A` `INFO ALREADY EXISTS | {``component``} already has scratch/rename info associated with it.`

Explanation: Displays when you try to scratch or rename a component that already has information associated with it.

`CMN2265A` `{``component``} already has scratch/rename info associated with it in {``package``}.`

Solution: Displays when the component shown already has scratch or rename information associated in the package named.

`CMN2270I` `SCRATCH/RENAME DISALLOWED | Your ID is not authorized to scratch or rename a component.`

Explanation: Displays when you try to scratch or rename a component and security protecting scratch/rename is defined, and your ID does not have authority.

CMN2300 Component Checkout

`CMN2300I { } CHECKED OUT | {``nnn``} checked out from {``data set``}`

Explanation: Displays when you opt to check out components from the project’s baseline or promotion libraries in online mode, and ChangeMan ZMF successfully performs the checkout.

Solution: See the “Checking Out A Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2305A` `ENTER PACKAGE NAME | Checkout requires an associated package for your project.`

Explanation: Displays when you try to check out components from the project’s baseline or promotion libraries, and the project was set up to require you to check out to an existing package.

Solution: See the “Checking Out a Component” chapter in the ChangeMan ZMF User’s Guide and the “Setting Application Parameters” section in ChangeMan ZMF Administrator’s Guide.

`CMN2310I` `CHECKED OUT | {``component``} checked out from {``library``}.`

Explanation: Displays when you check out a single component from the project’s baseline or promotion libraries.

`CMN2315A` `ENTER COMPONENT NAME | Component name required when checking out to a SEQ data set.`

Explanation: Displays when you either try to check out a component and neglect to enter a target data set name, or enter a sequential data set name as the target data set name.

`CMN2320A` `INVALID TARGET DSORG | Target data set has invalid DSORG.`

Explanation: Displays when you try to check out members and specifies a target data set name that is not a PDS, SEQ, LIB, or PAN.

`CMN2325A` `BATCH CHECKOUT ENFORCED | This Checkout must be done through a batch job.`

Explanation: ChangeMan ZMF does not support online checkouts CA-Panvalet® or CALibrarian® staging libraries.

Solution: You must perform this function in batch mode.

`CMN2326A` `Batch checkout exceeded {``nnn``} components requested | Maximum for a single batch checkout is {``nnn``}.`

Solution: Reduce the number of components selected for batch checkout.

`CMN2330I` `DUPLICATE CHECKOUT | {``component``} has already been checked out.`

Explanation: Displays when you try to check out a component into a package where the component is in CHECKOUT status.

Solution: Stage the package component or delete the component from the package before attempting to check it out again.

`CMN2340A` `ENTER TARGET DSORG | Target DSORG is required when Panvalet is generated.`

Explanation: Since a CA-Panvalet library can have a legitimate data set organization of physical sequential (DSORG=PS), it cannot be assumed that a checkout target is an ordinary sequential file.

Solution: You must confirm it.

`CMN2345A` `INVALID TARGET DSORG | Target data set is a PDS, target DSORG must be PDS.`

Explanation: Displays when you try to check out a component to a PDS. You cannot override the DSORG.

`CMN2350A` `INVALID TARGET DSORG | Target DSORG should be either SEQ, PAN or LIB.`

Explanation: Displays when you try to check out a member with a target data set DSORG of PDS, but the actual target data set was not a PDS.

`CMN2355A` `INVALID SITE | Specify one of the listed sites.`

Explanation: Displays when you try to check out a member from the project’s baseline (the project parameters were generated to keep baseline by site), but the site entered on panel CMNCRSSL (from which the baseline member should be selected) is not one that the project is set up to allow.

Solution: See the “Checking Out a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2360I` `INVALID LIBRARY TYPE | Checkout from LST library disallowed.`

Explanation: Displays when you try to check out an LST (List) library type member from the project’s baseline or promotion libraries.

Solution: See the “Checking Out a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2362I` `INVALID LIBRARY TYPE | Copy forward of invalid library type can only be deleted (D).`

`CMN2364A` `INVALID PARENTHESIS | data set name contains unbalanced parenthesis.`

Explanation: Displays when you incorrectly enter a data set name. Member names require open and closed parentheses. For example, data set (member name).

`CMN2365A` `INVALID DSN - QUOTES | Data set name contains unbalanced apostrophes.`

Explanation: Displays when you try to check out a member from the project’s baseline or promotion libraries and has specified a target file data set name without all the required apostrophes.

Solution: See the “Checking Out a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2370A` `INVALID TARGET DATA SET | Data set name cannot contain parenthesis.`

Explanation: Displays when you try to check out a member from the project’s baseline or promotion libraries and has specified a target file data set name with parentheses.

Solution: See the “Checking Out a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2375A` `INVALID PACKAGE MNEMONIC | {``mnemonic``} package mnemonic must be the same as {``mnemonic``} application.`

Explanation: Displays when you try to check out (with package association) a member from the project’s baseline or promotion libraries and specifies a package ID that has a different mnemonic from the one entered for the Project Mnemonic field.

Solution: See the “Checking Out a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2380A` `CHECKOUT ERROR | Checkout for this library type must be submitted as a batch job.`

Explanation: Displays when you try to check out a component online that requires batch checkout. For example, check out to a private CA Panvalet or CA Librarian library requires batch checkout.

Solution: Specify 2-Batch for CHECKOUT MODE. See “Checking Out a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2385A` `BAD ORGANIZATION | Baseline library has invalid DSORG.`

Explanation: Displays when you try to check out members from a project’s baseline library, but the library is not maintained as PDS, SEQ, LIB, or PAN.

`CMN2395I` `NO HISTORY | This component has no history to display.`

Explanation: Displays when you try to review the history of a component to be checked out from the project’s baseline or promotion libraries, but the component has not been previously checked out or staged by ChangeMan ZMF and, therefore, has no history.

Solution: See the “Checking Out a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2400A` `CHECKOUT ERROR | {``member name``} encountered a problem while being checked out.`

Explanation: Displays when you try to check out a member from an application’s baseline library, but the member does not exist. NOTE This message only applies to members that do not exist.

`CMN2405A` `NO COMPONENTS FOUND | No components found for level {``level``} in {``library``}.`

Explanation: Displays when you try to check out a component from a project’s baseline or promotion library that does not contain any components.

`CMN2410A` `INVALID COMPONENT NAME | Component name cannot end with # for Panvalet baseline library.`

Explanation: In CA-Panvalet older versions of components are held by appending # signs and back level numbers. When a component name ends with a # sign, ChangeMan ZMF cannot tell what the real name is.

`CMN2415A` `COMPONENT NOT FOUND | {``component``} does not exist in the promotion library.`

Explanation: Displays when you try to check out this component from the project’s promotion libraries, but the component is not within any promotion library at the specified level.

`CMN2420A` `INVALID FIELD | Component name not required for selection list Checkout.`

Explanation: Displays when you try to check out components from a selection list, and specifies a component name in the Component Name field.

`CMN2440I COMPONENT {``package id``} {``component type``} CHECKED OUT.`

Explanation: Displays when you opt to check out components from the project’s baseline or promotion libraries in batch (as opposed to online), and the batch job successfully performs the checkout. (The package name displays within this message only if the checkout itself is package-associated.)

`CMN2445I` `POTENTIAL CHECKOUT CONFLICT: {``component``} {``component type``} for package {``package id``}.`

Explanation: Displays when you check out components that have already been checked out by another TSOID.

`CMN2450A` `CHECKOUT DISALLOWED | Concurrent Checkout disallowed - {``component``} is in {``package``}.`

Explanation: Displays when you try to check out a new component that is already part of another package, but the project restricts checkout of components that are already in motion.

`CMN2451A` `INVALID APPLICATION | Invalid application {``comp``} is in {``appl``}.`

Explanation: Displays when the Global Administration option allowing components to exist in multiple applications, has not been enabled. The specified component already exists in another applications baseline or as a package component.

`CMN2452A` `INVALID APPLICATION | {``appl``} applications are restricted by rule {``rule``}.`

Explanation: Displays when you have entered an application the specified component does not have access to. Global Administration restricts which applications the component is allowed in.

Solution: Enter a valid application for the specified component.

`CMN2455A` `INVALID LANGUAGE | {``language name``} is the designated language for this component.`

Explanation: Displays when you try to check out a source component with a language different from the language that the application administrator designated.

`CMN2460I` `NO DESIGNATED LANGUAGE | No designated language for this component in the Package Master.`

Explanation: Displays when you request to use a language that the application administrator did not designate.

`CMN2465I` `CHECKOUT ERROR | CMNUPDAT encountered a problem processing an SRD component.`

Explanation: Displays when you encounter a problem while checking out a stacked reverse delta (SRD) component from baseline.

Solution: You should check the ChangeMan ZMF started task to determine the actual reason for failure.

`CMN2466I` `CHECKOUT ERROR | CMNCDCPR encountered a problem processing a compressed component.`

Explanation: Displays when stack reverse delta members in baseline are decompressed for checkout. The member CMNCDCPR performs the decompress step of the checkout process.

Solution: You should search the ChangeMan ZMF started task for an additional message regarding this issue.

`CMN2470I` `CHECKOUT ERROR | Checkout to personal library disallowed; contact Admin.`

Explanation: Displays when a checkout is attempted to a Personal/Development library.

Solution: The application administrator controls this ability in the application administration parameters.

`CMN2471I` `CHECKOUT WARNING | Checkout exit disallowed Checkout of {``component name``}.`

Explanation: Displays when an administrator has restricted checkout of this component.

Solution: You should contact the administrator.

`CMN2475I` `CHECKOUT ERROR | Component Activity File type not present; contact Admin.`

Explanation: Displays when you request an activity file type that has not been specified in the global or application parameters.

Solution: The application administrator can check the library types to verify the activity file type requested. If the requested file type is not present, the administrator can define it in option 2 of the Application Administration Options panel (CMNLAMEN).

`CMN2476I` `Unlock Failed | Component could not be unlocked.`

`CMN2477I` `CHECKOUT ERROR | Component {``component``} is locked.`

`CMN2478I` `Lock Failed | Component could not be locked.`

`CMN2480I` `CHECKOUT ERROR | Component Activity File type {``file type``} not defined; contact ADMIN.`

Explanation: The requested library type is not defined in the project parameters.

Solution: The application administrator can define the library type in the project parameters - option 2 under the Application Administration Options panel (CMNLAMEN).

`CMN2481I` `CHECKOUT DISALLOWED | Your ID is not authorized to checkout a component.`

Explanation: Displays when you try to checkout a component and security protecting checkout is defined, and your ID does not have authority.

`CMN2485I` `CHECKOUT WARNING | Not all component activity files checked out for selected components.`

Explanation: Displays when the components in a package that has activity files do not all have associated component activity files.

Solution: When you stage components from development after baseline ripple, the package contains a complete set of associated component activity files.

`CMN2486A` `CHECKOUT ERROR | Checked out of relinked modules not allowed.`

Explanation: Displays when you try to check out a relinked module.

Solution: You should delete all relinked modules from a package or should not check them out.

`CMN2487I` `COMMAND INVALID | Valid codes for a recompiled component are D, H, SL, UC, UL.'`

`CMN2488A` `REBIND DISALLOWED : pf1 | A - Checked out copy already in pkg. Delete and rebind from baseline.`

Explanation: Rebind is attempted for a like-load component that is already in the package as the result of a checkout or a stage from development of the component as like-load.

Solution: Delete the like-load component from the package and initiate the rebind again.

`CMN2489I` `INVALID COMMAND | Valid codes for a rebound linked component are: D, SL, UL.`

Explanation: Displays when you try to run a command that is not available to a relinked component. The only valid commands you can run for relinked components are delete (DEL) and source-to-load relationship (SL).

`CMN2490I` `CHECKOUT WARNING | {``component``} component activity file not checked out.`

Explanation: Displays when the associated activity file is not checked out with the requested module. The associated activity file was not created, was deleted from the activity file library, or was disallowed from being checked out.

Solution: The application administrator can populate the activity file data set with the proper activity file and allow its availability through option 2 under the Application Administration Options panel (CMNLAMEN). The activity file can be staged from a development data set.

`CMN2491I` `INVALID COMMAND | On-line checkouts are processed immediately.`

Explanation: Displays when a component is already checked out. This process was performed online. When you perform this checkout in batch, a CANCEL is allowed.

Solution: You should view the CHECKOUT panel (CMNCKOT1) for the CHECKOUT MODE FIELD entry.

`CMN2492I` `BAD ORGANIZATION | Only partitioned data set (PDS) can be browsed or viewed.`

Explanation: Displays when you try to browse or view a non-PDS data set. CA-Panvalet or CA-Librarian stack delta members cannot be browsed. Only PDSs can be browsed, using the Browse Compressed Listings under the BUILD option.

`CMN2493I` `AUTHORIZATION FAILED | Not authorized to update this package.`

Explanation: Displays when you try to update a package, but has no authority in the project where the package resides.

`CMN2494I` `COMMAND INVALID | Valid codes are B, D, H, S, SL, UC, UL, V.`

Explanation: Displays when you enter an invalid line command. The valid commands are then listed.

`CMN2495I` `COMPONENT IS FROZEN | Valid codes H (Hist), B (Browse), D (Del), SL (SRC/LOD) V (View).`

Explanation: Displays when you enter an invalid line command. The valid commands are then listed.

`CMN2496A` `UNKNOWN LANGUAGE | No language found for component within system.`

Explanation: Displays when a component is new in the system; no history exists for it.

Solution: You should enter the language name when prompted.

`CMN2497I` `LANGUAGE ASSUMED | Warning: {``component``} components have had their language assumed.`

Explanation: Displays when a component has no language specified. A language is assumed, based on the history of the component.

`CMN2498I` `LANGUAGE MAY BE ASSUMED | Warning: Some components may have their language assumed.`

Explanation: Displays when no language is specified during batch checkout. A language is assumed, based on the history of the component.

`CMN2499A` `CHECKOUT ERROR | Cannot checkout component with scr/ren request pending.`

Explanation: Displays when you try to check out a component with a scratch or rename pending request.

CMN2500 Component Stage

`CMN2500A` `NO STAGING INFORMATION | No component staging information found.`

Explanation: Displays when you review or update stage request information driven by the contents of a change package that has not yet had such information entered.

Solution: See the “Staging a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2501I` `MEMBER NOT FOUND | No member {``member``} in {``data set``} dataset.`

`CMN2502A` `STATUS ERROR | Cannot compile a component in frozen status.`

Explanation: Displays when you in batch mode, try to compile a source or like-source component that is in frozen status.

Solution: You must first revert the component.

`CMN2504A` `NO MATCH | No match on user’s component name and library type: {``library type``}.`

Explanation: Displays when you perform a batch stage, and the component name does not exist.

`CMN2505I` `BATCH STAGE SUBMITTED | The job to stage in batch has been submitted.`

Explanation: Displays when you select batch stage, and the job has been submitted.

`CMN2506A` `SELECT AN OPTION | Select from this list of options:`

Explanation: Displays when you enter an invalid line command.

Solution: You should select a valid line command from the line commands that are listed.

`CMN2507A` `ERROR OPENING ISPFILE | Unable to open file to read JCL to submit.`

Explanation: Displays when the allocated ISPFILE is unavailable.

Solution: You should re-IPL to locate the file.

`CMN2508A` `ERROR ALLOC ISPFILE | Unable to reset in-use bit for ISPFILE`

Explanation: Displays when the in-use of the ISPFILE is set.

Solution: You should re-IPL to allocate a new ISPFILE.

`CMN2509A` `ALLOCATE ERROR | Unable to allocate JCL submit file.`

Explanation: Displays when the ISPFILE is unavailable for allocation.

Solution: Re-IPL to allocate the file.

`CMN2510A` `NO HISTORY INFORMATION | No component history information found.`

Explanation: Displays when you review the history of a component to be staged, but the component has not been previously checked out or staged by ChangeMan ZMF and, therefore, has no history.

Solution: See the “Staging a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2511A` `UNALLOCATE ERROR | Unable to deallocate JCL submit file. Reason code: {``reason code``}.`

Explanation: Displays when the ISPFILE is not available for deallocation. Another user may be holding the file, and until that user makes it available, a second user cannot deallocate it.

`CMN2512I Attempting to restore archived file {``data set name``}, please wait.`

Explanation: Displays when you try to access an archived file.

`CMN2515I` `MAXIMUM LINES SAVED | A maximum of 48 lines of component description has been exceeded.`

Explanation: Displays when the component description exceeds its allowed maximum length.

Solution: You should shorten the component description.

`CMN2516I` `NO DESCRIPTION | No component general description found to browse.`

Explanation: Displays when the member containing the component description was not checked out or was deleted from the staging data set.

Solution: The application administrator can allow or disallow the checkout of this member in option 2 under the Application Administration Menu.

`CMN2517I` `STAGE CANCELLED | Edit changes saved.`

`CMN2520A` `ENTER ORGANIZATION | Data set organization must be entered for BDAM data set.`

Explanation: Displays when you stage a component from a BDAM data set, but do not enter the organization type, such as PAN, LIB, or OTH. ChangeMan ZMF checks to see what kind of data set needs to be staged.

Solution: See the “Staging a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2525A` `BAD ORGANIZATION | Only partitioned data set (PDS) can be browsed, viewed or edited.`

Explanation: Displays when you try to browse or edit from a CA-Panvalet or CALibrarian member list.

Solution: See the “Staging a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2530A` `BAD ORGANIZATION | Data set DSORG must be PDS, SEQ, PAN or LIB.`

Explanation: Displays when you either stage a component from a data set that is not organized in one of the ways ChangeMan ZMF requires, or enter an organization method on the Stage: Development Driven panel (CMNSTG02) that ChangeMan ZMF does not recognize.

Solution: See the “Staging a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2535A` `BAD ORGANIZATION | This is a sequential (SEQ) data set.`

Explanation: Displays when you stage a component from a data set that is not organized in a way that matches the organization method entered on the Stage: Development Driven panel (CMNSTG02).

Solution: See the “Staging a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2540A` `BAD ORGANIZATION | This is a partitioned (PDS) data set.`

Explanation: Displays when you stage a component from a data set that is not organized in a way that matches the organization method entered on the Stage: Development Driven panel (CMNSTG02).

Solution: See the “Staging a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2545A` `BAD ORGANIZATION | Library organization must be PAN, LIB or OTH.`

Explanation: Displays when you stage a component from a BDAM data set and enter an organization type other than PAN, LIB, or OTH. ChangeMan ZMF checks to see what kind of data set is to be staged.

Solution: See the “Staging a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2546A` `BAD ORGANIZATION | Library organization must be PDS for Online Forms Manager data set.`

Explanation: Displays when you stage a component from an Online Forms Manager data set and enter an organization type other than PDS.

`CMN2550A` `BAD ORGANIZATION | {``PAN/LIB/OTH``} organization was not generated - contact Admin.`

Explanation: Displays when you stage a component from a data set that is organized in a method that the project’s administrator restricted when generating the project’s parameters.

Solution: See the “Staging a Component” chapter in the ChangeMan ZMF User’s Guide and the “Setting Application Parameters” section in the ChangeMan ZMF Administrator’s Guide.

`CMN2552I` `STAGE ERROR | Component {``component``} is locked.`

Explanation: Displays when you try to stage, edit, or delete a component that has been previously locked by another user.

`CMN2555I` `COMPONENT OUT-OF-SYNC | The baseline version of component_name has been modified.`

Explanation: Displays when you try to install a module version that predates the module presently in baseline, and the Validate Version During Staging field is set to YES. This message also displays in the event of an audit.

`CMN2556A` `CHANGES WILL BE LOST | Check out new version from baseline; changes will not be saved.`

Explanation: Displays when you try to edit or stage a member whose baseline version has changed since it was checked out.

Solution: You should check out a new baseline version.

`CMN2557I` `STAGE DISALLOWED | Your ID is not authorized to stage a component.`

Explanation: Displays when you try to stage a component and security protecting stage is defined, and your ID does not have authority.

`CMN2560A` `INVALID DATA SET NAME | Staging from a GDG data set is disallowed.`

Explanation: Displays when you stage a component from a Generation Data Group (GDG) data set, because ChangeMan ZMF does not function with GDG data sets. ChangeMan ZMF checks to see what kind of data set is to be staged.

Solution: See the “Staging a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2561I` `COMPONENT IN USE | Component requested is in use by another user.`

Explanation: The requested function is unable to acquire exclusive control of the component.

Solution: Retry the function. If this error persists, determine what function has exclusive control of the component.

`CMN2562I` `COMPONENT IN USE | Component associate dataset is in use by another user.`

Explanation: The requested function is unable to acquire exclusive control of the library or zFS directory.

Solution: Retry the function. If this error persists, determine what function has exclusive control of the library or zFS directory and terminate that function.

`CMN2563I` `COMPONENT IN USE | Component requested is in use by userid.`

Explanation: Displays when you try to work with a component in a data set or zFS file that is currently being used by another user. userid is the userid of the user of job that currently is using the component. userid is displayed as Unknown if users on two different LPARs are attempting to edit the same component at the same time.

`CMN2564I` `COMPONENT ERROR | Component associate dataset cannot be deleted.`

`CMN2565A` `ENTER STAGE NAME | Stage name must be specified when staging from a SEQ type data set.`

Explanation: Displays when you stage a component from a sequential file, but do not enter the member name that the component should be copied to in the staging library.

Solution: See the “Staging a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2566A` `INVALID LRECL | Data truncation due to source LRECL disallowed.`

Explanation: Displays when you attempt to stage from development where the development data set record (minus any Record Descriptor Word) is longer than the staging library record (minus any RDW), making data truncation possible.

Solution: If you are sure that either no data will be truncated or truncation will not be harmful, copy the member to a data set or library with a record that is the same length or shorter than the staging library record (minus any RDW in either record), and then stage from the new data set or library.

`CMN2567A` `STAGE NAME INVALID | Stage name is valid only if member name supplied on panel.`

Explanation: Displays when you, who are staging a component, name the target component name before naming the source component being staged.

`CMN2568I` `PRIOR ASSUMED | Translator options obtained from those displayed previously.`

Explanation: The values displayed or used for the compile, link, or other translator process were obtained from the values previously displayed and used for any component.

`CMN2570A` `ENTER MEMBER NAME | Enter ISPF member name.`

Explanation: At the Stage: Development Driven panel (CMNSTG02) a single member can be staged by entering the component name in field name MEMBER.

`CMN2571I` `HISTORY ASSUMED | Translator options obtained from component history`

Explanation: The values displayed or used for the compile, link, or other translator process were obtained from component history for the current component.

`CMN2572I` `DESIGNATED ENFORCED | Translator options obtained from enforced designated procedure`

Explanation: The values displayed or used for the compile, link, or other translator process were obtained from an enforced component designated procedure for the current component.

`CMN2573I` `STAGE ERROR | Component {``component``} is recompiled or relinked in package.`

`CMN2574I` `COMPONENT STAGED | {``component``} component(s) staged from {``data set``}.`

Explanation: Displays when you stage multiple components from a member list.

`CMN2575I` `{``component``} STAGED | {``component``} component staged from {``data set``}.`

Explanation: Displays when ChangeMan ZMF has successfully begun the requested staging of a component.

Solution: See the “Staging a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2576I` `SUBMITTED FOR STAGE | {``nnn``} component(s) submitted for Stage from {``data set``}.`

Explanation: Displays when ChangeMan ZMF has successfully begun the requested mass staging of library components.

Solution: See the “Staging a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2577I` `INVALID RECORD FORMAT | Source data set RECFM does not match staging data set RECFM.`

Explanation: You should check the record format of the source data set in ISPF 3.4 and confirm that it matches the record format of the staging data sets.

Solution: See the “Staging a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2578I` `PROCEDURE UNDEFINED | Procedure name undefined or not associated to a language name.`

Explanation: Displays when you try to stage (copy and compile) a source component for a change package whose governing project has not been fully configured.

Solution: The administrator must set up a list of compiling procedures for each language and library type. The application administrator should review the project. See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN2579I` `LANGUAGE ASSUMED | Language name for {``component``} has been assumed.`

Explanation: Displays during staging when no language has been specified. A language is assumed, based on the component’s history.

`CMN2580A` `STAGING RESTRICTED | Staging Restriction Level 2 or 3 in effect-Contact Admin.`

Explanation: Displays when you opt to stage, driven by the contents of the development libraries, but the application administrator has restricted the stage function when generating the project’s parameters.

Solution: See the “Setting Application Parameters” section in the ChangeMan ZMF Administrator’s Guide and the “Staging a Component” chapter in the ChangeMan ZMF User’s Guide.

`CMN2581I` `CHECKOUT ENFORCED | User did not pass Checkout entity check {``entity name``}.`

Explanation: Displays when you do not pass the entity check when staging a component from baseline that has not been checked out before.

Solution: You should contact the application administrator to receive authorization to stage the component into a change package.

`CMN2582I` `CHECKOUT ENFORCED | Component must be checked out from the baseline library.`

Explanation: Displays when you stage a component from a development library for a component that already exists in baseline, and the project is set to enforce checkout from baseline if the component exists in baseline.

`CMN2583A` `INVALID LIKE VALUE | Invalid designated load library type. Contact Local Admin.`

Explanation: Displays when the designated target load library does not have valid load library attributes.

`CMN2584I` `{``component``} BUILD BYPASSED | {``component``} component staged from {``dataset``} build bypassed`

`CMN2585A` `STAGE ERROR | Mass staging is disallowed at this option.`

Explanation: The mass stage option is performed in development-driven stage only for PDS libraries. SEQ data sets cannot be mass staged.

`CMN2586A` `STAGE ERROR | Cannot stage component with scr/ren request pending.`

Explanation: Displays when you try to stage a component with a pending scratch or rename request.

`CMN2587A` `STAGE ERROR | Package user information update error for component {`

`CMN2588I` `COMMAND INVALID | Valid line commands for relinked components are: BD,BL,D,ED,H,SL,VL.`

Explanation: Displays when you enter an invalid line command within a component list for a relinked component.

Solution: You should enter a valid command.

`CMN2589I` `COMMAND INVALID | Valid commands for recompiled components are BD, BL,D,ED,H,SL,VL.`

Explanation: Displays when you try to edit or browse a recompiled component. You cannot edit or browse recompiled components, because there is no source code to browse in staging libraries.

`CMN2590A STAGE ERROR | Package Copy information update error for component {``component``}.`

Explanation: Displays when ChangeMan ZMF encounters an error while updating the package copy information.

`CMN2591A STAGE ERROR | Package source/load information update error for component {``component``}.`

Explanation: Displays when ChangeMan ZMF encounters an error while updating the package source/load information.

`CMN2592I PROCESS ERROR | Out of sync situation: component tied to {``component name``}.`

Explanation: Displays when a source/load mismatch is encountered.

`CMN2593A STAGE ERROR | Package history information update error for component {``component``}.`

Explanation: Displays when ChangeMan ZMF encounters an error while updating the package component history information.

`CMN2594I INVALID COMPONENT STATUS | Component must be checked out first before it can be staged.`

Explanation: Displays when you try to stage, recompile, edit, or browse a component that was copied forward from another package but was never checked out from baseline or staged from a development library.

`CMN2595I EDIT/BROWSE DISALLOWED | Edit/Browse of component description disallowed for this library type.`

Explanation: Displays when the library type does not have an associated component description, or the component description was not allowed to be checked out. This is activated in option 2 on the Application Administration Menu.

Solution: The application administrator should let the component description be checked out at the Project_name - Library Types Part 2 of 2 panel (CMNCLLT1) by entering YES in the Checkout Component Description field.

`CMN2596I NO ACTIVITY FILE FOUND | No component activity file found to be edited or browsed.`

Explanation: Displays when the library type does not have an associated component activity, or the component activity file was not allowed to be checked out. This is activated in option 2 on the Application Administration Menu.

Solution: The application administrator should let the component activity file be checked out at the Project_name - Library Types Part 2 of 2 panel (CMNCLLT1) by entering YES in the Checkout Component Activity field.

`CMN2597I INVALID SELECTION | Invalid Staging Selection Code.`

Explanation: Displays when you issue an invalid staging selection code.

`CMN2598I SELECT A COMPONENT | No components were selected for selective mass Stage.`

Explanation: Displays when you issue the STAGE command on the Development Driven Stage Component List panel (CMNSTG03) without selecting any components.

`CMN2599I` `NOT PERMITTED | Batch Stage of OTHER library types is not permitted.`

Explanation: Displays when you try to batch stage an OTH type component. Examples of valid component types are SRC, CPY, and so forth.

CMN2600 Package Audit

`CMN2600I` `AUDIT JOB SUBMITTED | The job to audit this package has been submitted.`

Explanation: Displays when you audit the change package’s staging libraries as a batch job, and ChangeMan ZMF has submitted the batch job.

Solution: See the “Auditing Packages” chapter in the ChangeMan ZMF User’s Guide.

`CMN2601I` `INVALID JOB PARM SPECIFIED | INVALID JOB PARM HAS BEEN ENTERED`

Explanation: Displays when the USER parameter for package audit program CMNAD000 or I/A data extract program CMNIA000 specifies a userid different from the userid that submitted the job. The userid specified in the USER parameter must match the userid of the person who submits the job, unless the submitter is ChangeMan ZMF.

Solution: Correct the USER parameter and resubmit the job.

`CMN2605I CHANGE MAN LOG FILE ERROR!!!!`

Explanation: Displays for several reasons.

Solution: To diagnose the problem you should do the following:

Determine if the STARTED TASK is still running.
Determine if the LOG file is full and, if so, back up the package master and reallocate the LOG file.
Examine the LOG FILE to determine if the STARTED TASK is updating the LOG file correctly.

`CMN2609A EMPTY BUN TABLE | No BUNs found, Run CMNIA000, LDSLOAD`

`CMN2610A INVALID PACKAGE KEY SPECIFIED.`

Explanation: Displays when you submit an audit job with a global key, and a project key is required.

Solution: You should modify the SYSIN card of the job and resubmit the job.

`CMN2611A` `Serious error reported by exit 044, audit has been terminated, contact your administrator.`

`CMN2612I` `List of copybook libraries searched follows:`

`CMN2613I` `Copybook library list ends.`

`CMN2614I` `Package is attached to a Release, package audit processing will be restricted to staging contents.`

`CMN2615I` `PACKAGE NOT FOUND IN PACKAGE MASTER.`

Explanation: Displays when the package that you request for audit is not residing in the package master.

Solution: You should check the package name for the correct entry.

`CMN2616A Unable to obtain sufficient memory for build of hash token table. Getmain RC = {``rc``}.`

`CMN2617I Use ERO Area Audit to ensure integrity across the release areas and baseline.`

`CMN2618A` `INVALID PACKAGE OPTION | Package {``option``} and restrict RC both YES.`

Explanation: You have requested conflicting options during audit process.

Solution: Correct options and rerun audit.

`CMN2619A INVALID PACKAGE OPTION | Package {``package``} simple and restrict RC both YES.`

`CMN2620I RECORD NOT FOUND | Local record not found in Package Master.`

Explanation: Displays when the project parameters were not all configured or were configured incorrectly.

Solution: You should verify the complete project configuration with the application administrator.

`CMN2621A The I/A Dataspace is not available, audit is terminating.`

`CMN2622I I/A table out of date. Cannot find BUN for library type {``libtype``} in application {``appl``}. This may result in invalid synchs.`

Explanation: Package Audit cannot find the Baseline Unique Number (BUN) for libtype included in a package you are attempting to audit. The most likely reason is that Impact Analysis Data Extraction and reload was not run when:

Application appl was added to the ChangeMan ZMF instance.
Library type libtype was added to existing application appl.

Solution: Run Impact Analysis Data Extraction(=A.G.I) for application appl and reload the I/A dataspace, then, rerun Package Audit.

`CMN2623I` `I/A table out of date. Library type {``libtype``} in application {``appl``} is no longer defined. This may result in invalid synchs.`

Explanation: Package Audit cannot find the library type {libtype} included in a package you are attempting to audit. The most likely reason is that Impact Analysis Data Extraction and reload was not run when:

Application appl was added to the ChangeMan ZMF instance.
Library type libtype was added to existing application appl.

Solution: Run Impact Analysis Data Extraction(=A.G.I) for application appl and reload the I/A dataspace, then, rerun Package Audit.

`CMN2624A` `There are no XAP=appl sysin parms OR the application specified is not in the I/A table; Audit cannot continue.`

`CMN2625I` `GLOBAL RECORD NOT FOUND IN PACKAGE MASTER`.

Explanation: Displays when the global parameters were not all configured or were configured incorrectly.

Solution: You should verify the complete site configuration with the global administrator.

`CMN2626I` `JOB TO RESOLVE {``synchx!``} FOR {``copy component name``} IN PACKAGE {``package name``} BYPASSED, SOURCE NOT ACTIVE IN STAGING PRECLUDES BASELINE.`

Explanation: You requested an audit of a participating package on the Audit panel, and specified YES to option 'Auto-Resolve of Out-of-Synchs'. During audit processing for copybook members within source code, source components residing in a staging library for which the following two events occur:

Are not in active status
Have no ISIC record entry in the package master are not considered to be included in the package. The baseline libraries are used.

This message is issued when the following four events occur:

A baseline out-of-synch condition occurs for audit processing of copybook members within source code.
The audit auto-resolve option is set to YES.
The out-of-synch condition qualifies for auto-resolve processing.
The baseline library is referenced for the corresponding source component to resolve the out-of-synch-condition.

If a source component resides in staging where your intent to include or exclude the source from the package cannot be determined, then auto-resolve will be bypassed. Message CMN2627I is issued with this message.

`CMN2627I` `{``source-component-name.library-type``} IN PACKAGE {``package name``} NOT ACTIVE, USER ACTION REQUIRED TO RESTAGE OR DELETE COMPONENT IN STAGING.`

Explanation: This message is issued in conjunction with CMN2626I identifying the name of the inactive source component, the library type, and the name of the package. Stage, update, or delete activity in progress for the component was interrupted before staging library and package master processing could complete.

Note

Your intervention is required to complete the intended action on the source component identified in this message. If your intent is:

To include the source component in the package, then restage the component from ChangeMan ZMF.
Not to use the inactive component, then from ChangeMan ZMF, delete the source component from the package name identified in this message.

`CMN2628I Discrepancy in I/A table for baseline library type {``type``} defined to application {``appl``}. Recommend run assist to update table.`

Explanation: This message is issued:

If there are more than one like-copy library types sharing the same baseline which is defined in the package master, but there is no BUN for the shared copybook in the I/A table.
If the parse of the package master indicates staging like-copy library types are sharing a baseline, and the I/A table shows a different BUN for the shared like-copy lib types.

Message CMN2628I is informational. If the conditions above are detected, audit will continue processing using the information from the package master, not the I/A table, to ensure accuracy.

Solution: The recommended action is to update the Impact Analysis Dataspace by running Impact Analysis Data Extract(=A.G.I) and reload the I/A dataspace.

`CMN2629A Application of package being audited has not been found in the I/A table; Audit cannot continue.`

Solution: The recommended action is to update the Impact Analysis Dataspace by running Impact Analysis Data Extract(=A.G.I) and reload the I/A dataspace

`CMN2630I No Package Site record found in package master.`

Explanation: Displays when the site parameters where the package is installed were not all configured, or were configured incorrectly.

Solution: You should verify the complete site configuration with the global administrator.

`CMN2631A INVALID PACKAGE OPTION | Package {``package``} simple, primary and x-appl options all set to YES.`

`CMN2632A INVALID PACKAGE OPTION | Package {``package``} simple and department no. both to YES.`

`CMN2633A INVALID PACKAGE OPTION | Package {``package``} simple, dept.no and restrictRC all YES.`

...

`CMN2634A INVALID PACKAGE OPTION | Package {``package``} primary, dept. no. and restrictRC all YES.`

`CMN2635I NO ASSOCIATED BASELINE FOUND FOR LIBRARY TYPE {``library type``}.`

Explanation: A baseline library needs to be created for the library type requested for the package.

Solution: The application administrator should check the library types list and the baseline libraries in options 2 and B - LIBRARY and BASELINE - under the Application Administration Options panel (CMNLAMEN).

`CMN2636A INVALID PACKAGE OPTION | Package {``package``} simple, primary, dept. no. and restrictRC all YES.`

`CMN2637A INVALID PACKAGE OPTION | Package {``package``} simple, primary and dept no. all YES.`

`CMN2638A INVALID PACKAGE OPTION | Package {``package``} primary and dept.no. both YES.`

`CMN2639A INVALID PACKAGE LEVEL | Package {``package``} must be participating to audit by department no.`

`CMN2640I` `NO STAGING LIBRARIES FOUND FOR PACKAGE.`

Explanation: Displays when no staging libraries are allocated for the requested package. Either they were never allocated, or they were deleted.

...

`CMN2641I` `STAGING LIBRARIES HAVE BEEN AGED FOR PACKAGE.`

`CMN2642A` `INVALID PACKAGE OPTION | Package {``package``} primary and restrict RC both YES.`

...

`CMN2643A` `INVALID PACKAGE OPTION | Package {``package``} simple and primary both YES.`

Explanation: You requested an audit of a participating package on the Audit panel, and specified both. These two options are mutually exclusive:

YES to the option 'Audit Participating Package as a Simple Package'.
YES to the option 'Audit Participating Package as a Primary Package'.

Solution: Enter a YES to only one of the designated options.

`CMN2644A` `INVALID PACKAGE LEVEL | Package {``package``} must be participating to audit as a primary pkg.`

Explanation: You requested an audit of a package on the Audit panel, and specified YES to the option 'Audit Participating Package as a Primary Package'. The package you specified was a simple package, a complex package, or a super package, and the primary option is available only for participating packages.

Solution: To use the primary package option, specify the name of a participating package.

`CMN2645I` `No package source and load record found for component {``component name``}.`

Explanation: The requested component has no associated source and load members. This integrity issue arises because the component was copied into a staging library outside of ChangeMan ZMF, or the associated source and load members were deleted from the staging libraries.

`CMN2646I` `No package load record found for component {``component name``}.`

Explanation: The requested component has no associated load member. This integrity issue arises because the component was copied into a staging library outside of ChangeMan ZMF, or the associated load member was deleted from the staging libraries.

`CMN2647A` `INVALID PACKAGE LEVEL | Package {``package``} must be participating to audit as a simple pkg.`

Explanation: You requested an audit of a package on the Audit panel, and specified YES to the option 'Audit Participating Package as a Simple Package'. The package you specified was a simple package, a complex package, or a super package, and the simple option is available only for participating packages.

Solution: To use the simple package option, specify a name of a participating package.

`CMN2648I` `THE COMPLEX/SUPER PACKAGE NAME IS INVALID DUE TO A PACKAGE NUMBER PROCESSING ERROR READING GEN RCD 0.`

Explanation: You requested an audit of a participating package. During initial processing in program CMNAUD10 a read is performed to the package master for General Record 0 to extract the complex/super package name associated with the participating package. Validation is then performed on the complex/super package application name to ensure a proper VSAM key can be constructed for a read of General Record 6. This message indicates the complex/super package number is invalid due to a possible invalid General Record 0 for the participating package you requested for the audit.

Solution: Check the field PKGGCSPN of General Record 0 for the participating package that you requested for audit. Perform ‘Update of Complex/Super Package Information’ to ensure the name of the participating package you requested is listed in panel CMNPGNL6 and to redefine the complex/super relationship to the participating package. This rewrites the field PKGGCSPN in General Record 0. Once the error has been corrected, resubmit the audit job.

`CMN2649I` `THE JOB TO RESOLVE {``synch``} FOR {``component``} IN PACKAGE {``participating package name``} BYPASSED, NO PACKAGE FOUND FOR SOURCE COMPONENT.`

Explanation: During processing in program CMNAUD20, an out-of-synch condition for a Synch2! or a Synch9! was detected in a participating package. Because the Auto-Resolve option was set to YES, a search of the participating package list area for the proper name of the participating package associated with the out-of-synch component occurred. This message indicates the participating package name was not found in the list area or the participating package number obtained from the list was invalid.

Solution: Perform an ‘Update of Complex/Super Package Information’ to ensure the name of all participating packages for the complex/super package are listed in panel CMNPGNL6 and to redefine the complex/super relationship to the participating packages. Once the error has been corrected, resubmit the audit job.

`CMN2650I` `Unable to allocate {``baseline/staging``} data set.`

Explanation: Displays when a data set allocation fails. This results from DASD deficiency or incorrect file attributes.

`CMN2651I` `THE JOB TO RESOLVE {``synch``} FOR {``component``} IN PACKAGE {``participating package name``} BYPASSED, NO PACKAGE FOUND FOR CALLED COMPONENT.`

Explanation: During processing in program CMNAUD20, an out-of-synch condition for a Synch5!, Synch8!, or Synch16! was detected in a participating package. Because the Auto-Resolve option was set to YES, a search of the participating package list area for the proper name of the participating package associated with the out-of-synch for a called component residing in a staging library occurred. This message indicates the participating package name was not found in the list area or the participating package number obtained from the list was invalid.

Solution: Perform an ‘Update of Complex/Super Package Information’ to ensure the name of all participating packages for the complex/super package are listed in panel CMNPGNL6 and to redefine the complex/super relationship to the participating packages. Once the error has been corrected, resubmit the audit job.

`CMN2652I` `THE JOB TO RESOLVE {``synch``} FOR {``component``} IN PACKAGE {``participating package name``} BYPASSED, NO PACKAGE FOUND FOR CALLING MODULE.`

Explanation: During processing in program CMNAUD20, an out-of-synch condition for a Synch7! was detected in a participating package. Because the Auto-Resolve option was set to YES, a search of the participating package list area for the proper name of the participating package associated with the out-of-synch for a calling load module residing in a staging library occurred. This message indicates the participating package name was not found in the list area or the participating package number obtained from the list was invalid.

Solution: Perform an ‘Update of Complex/Super Package Information’ to ensure the name of all participating packages for the complex/super package are listed in panel CMNPGNL6 and to redefine the complex/super relationship to the participating packages. Once the error has been corrected, resubmit the audit job.

`CMN2653I` `THE JOB TO RESOLVE {``synch``} FOR {``component``} IN PACKAGE {``participating package name``} BYPASSED, NO PACKAGE FOUND FOR CALLING SOURCE.`

Explanation: During processing in program CMNAUD20, an out-of-synch condition for a Synch4! or a Synch15! was detected in a participating package. Because the Auto-Resolve option was set to YES, a search of the participating package list area to obtain the proper name of the participating package associated with the out-of-synch for a calling source component residing in a staging library. This message indicates the participating package name was not found in the list area or the participating package number obtained from the list was invalid.

Solution: Perform an Update of Complex/Super Package Information ensuring the name of all participating packages for the complex/super package are listed in panel CMNPGNL6 in order to redefine the complex/super relationship to the participating packages. Once the error has been corrected, resubmit the audit job.

`CMN2654I` `GEN RCD 0 NOT FOUND FOR COMPLEX/SUPER PACKAGE {``package name``}, AUDIT RETURN CODE NOT UPDATED FOR PARTICIPATING PACKAGES.`

Explanation: During return code processing in program CMNAUD20 an attempt was made to read General Record 0 from the package master for the name of the complex/super package you requested. Because the participating package list area was not available to obtain the name of the participating package associated with its specific return code, return code processing is suppressed. This message indicates the complex/super package general records may have been deleted or altered while the audit job was running.

Solution: Check to ensure a package exists for the name of the complex/super package you specified for the submission of the audit job. If there are none, attempt to ‘Create a New Package,’ or ‘Update Package Information’ for the existing complex/super package to rebuild the package master records. Perform an ‘Update of Complex/Super Package Information,’ to ensure the names of all participating packages for the complex/super package are listed in panel CMNPGNL6, and to redefine the complex/super relationship to the participating packages. Once the error has been corrected, resubmit the audit job.

`CMN2655I` `SERIFACE Error encountered.`

Explanation: Displays when ChangeMan ZMF tries to read from a CA-Panvalet or CALibrarian baseline library, and encounters a bad record.

`CMN2656I` `PRINTING AUDIT REPORT FOR COMPLEX PACKAGE {``package name``}.`

Explanation: Informs you, in SYSPRINT, that an audit is being processed for this complex package.

`CMN2657I` `PRINTING AUDIT REPORT FOR SUPER PACKAGE {``package name``}.`

Explanation: Informs you, in SYSPRINT, that an audit is being processed for this super package.

`CMN2658I` `PRINTING AUDIT REPORT FOR PARTICIPATING PACKAGE {``package name``}.`

Explanation: Informs you, in SYSPRINT, that an audit is being processed for this participating package.

`CMN2659I` `PARTICIPATING PACKAGE {``package name``} NOT IN DEV/FRZ STATUS, AUDIT RETURN CODE WAS NOT UPDATED.`

Explanation: Informs you that an audit is being processed for this participating package and the audit return code does not have to be updated.

`CMN2660I` `UNABLE TO OPEN {``baseline/staging``} data set.`

Explanation: Displays when another user is accessing the requested data set.

`CMN2661I` `SUPER PACKAGE {``package name``} PASSED THE AUDIT WITH A RETURN CODE OF {``return code``}.`

Explanation: Informs you that an audit is being processed for this super package and the super package has successfully passed the audit. The return code of the super package represents the highest return code generated from the audit of all the participating packages defined to the super package.

`CMN2662I` `SUPER PACKAGE {``package name``} FAILED THE AUDIT WITH A RETURN CODE OF {``return code``}.`

Explanation: Informs you that an audit is being processed for this super package and the super package has failed to pass the audit. The return code of the super package represents the highest return code generated from the audit of all the participating packages defined to the super package.

Solution: Examine the end of the audit report for messages CMN2666I or messages CMN2667I to determine the individual return codes of each participating package, and to identify which participating packages in the super package encountered out-of-synch conditions. See Chapter 8 “Auditing Packages” in the ChangeMan ZMF Administrator’s Guide for information on how to resolve any out-of-synch situations.

`CMN2663I` `PARTICIPATING PACKAGE {``package name``} IN FROZEN STATUS AND NO COMPONENTS SELECTIVELY UNFROZEN, AUDIT RETURN CODE NOT UPDATED.`

Explanation: Informs you that an audit is being processed for this participating package in frozen status, but no components were selectively unfrozen at the time of the submission of the audit job. The audit return code does not have to be updated.

`CMN2664I` `GEN RCD 6 NOT FOUND FOR COMPLEX/SUPER PACKAGE {``package name``}, AUDIT REPORT MAY BE INCOMPLETE FOR PARTICIPATING PACKAGES.`

Explanation: During processing in program CMNAUD20, an attempt was made to read General Record 6 from the package master for the names of the participating packages defined to the complex super package to build an internal participating package list table. Because the participating package list table could not be properly constructed, the audit process might not be able to obtain the name of the participating package associated with a specific out-of-synch condition. This message indicates the complex/super package general records might have been deleted or altered while the audit job was running, or the General Record 0 for the participating package you specified had an invalid pointer to a complex/super package.

Solution: Check to ensure a package exists for the name of the complex/super package. If there is none, attempt to ‘Create a New Package,’ or ‘Update Package Information’ for the existing complex/super package to rebuild the package master records. Perform an ‘Update of Complex/Super Package Information’ to ensure the names of all participating packages for the complex/super package are listed in panel CMNPGNL6 and to redefine the complex/super relationship to the participating packages. Once the error has been corrected, resubmit the audit job.

`CMN2665I` `UNABLE TO CLOSE BASELINE/STAGING data set.`

Solution: Displays when another user is accessing the requested data set.

`CMN2666I` `PARTICIPATING PACKAGE {``package name``} PASSED THE AUDIT WITH A RETURN CODE OF {``return code``}.`

Explanation: Informs you that an audit is being processed for this participating package and the participating package has successfully passed the audit.

`CMN2667I` `PARTICIPATING PACKAGE {``package name``} FAILED THE AUDIT WITH A RETURN CODE OF {``return code``}.`

Explanation: Informs you that an audit is being processed for this participating package and the participating package has failed to pass the audit.

Solution: See chapter 8 “Auditing Packages” in the ChangeMan ZMF Administrator’s Guide for information on how to resolve any out-of-synch situations.

`CMN2668I` `COMPLEX PACKAGE {``package name``} PASSED THE AUDIT WITH A RETURN CODE OF {``return code``}.`

Explanation: Informs you that an audit is being processed for this complex package and the complex package has successfully passed the audit. The return code of the complex package represents the highest return code generated from the audit of all the participating packages defined to the complex package.

`CMN2669I` `COMPLEX PACKAGE {``package name``} FAILED THE AUDIT WITH A RETURN CODE OF {``return code``}.`

Explanation: Informs you that an audit is being processed for this complex package and the complex package has failed to pass the audit. The return code of the complex package represents the highest return code generated from the audit of all the participating packages defined to the complex package.

Solution: You should examine the end of the audit report for message CMN2666I or message CMN2667I to determine the individual return codes of each participating package, and to identify which participating packages in the complex package encountered out-of-synch conditions. See chapter 8 “Auditing Packages” in the ChangeMan ZMF Administrator’s Guide for information on how to resolve any out-of-synch situations.

`CMN2670I` `SERBSAM: PDS GET DIRECTORY ERROR.`

Explanation: Displays when the GET step initiated for a data set from BSAM encounters a problem in the directory of the data set.

`CMN2671I` `PARTICIPATING PACKAGE {``package name``} INSTALL DATE {``install date-install time``} HAS PASSED FOR SITE {``remote site name``}, AUDIT RETURN CODE NOT UPDATED.`

Explanation: Informs you that an audit is being processed for this participating package and the participating package has passed the installation date and time for the remote site identified in the message.

Solution: If the date and time were specified in error when the participating package was created, then you should ‘Update Package Information’ to amend the install date and time for the remote site name, and resubmit the audit job.

`CMN2672I` `| AUDIT SUBMITTING API JOB TO RESOLVE OUT-OF-SYNCH CONDITIONS.`

`CMN2673I` `| PROBLEM ENCOUNTERED ATTEMPTING TO SUBMIT API JOB TO RESOLVE OUT-OF-SYNCHS FOR AUDIT.`

`CMN2674I` `| THE {``job``} JOB TO RESOLVE OUT-OF-SYNCH FOR {``component``} BYPASSED, NO COMPILE/LINK PROC WAS FOUND IN HISTORY`

`CMN2675I` `SERBSAM: PDS FIND MEMBER ERROR FOR {``member name``} WITHIN {``data set``}.`

Explanation: Displays when the FIND step initiated for a data set from BSAM encounters a problem, and the data set is not readable. The member could have been part of a PDS directory, but by the time BSAM started to read the member, it could not find it. The member could have been deleted or moved. You should try the function again.

`CMN2676A` `YOU MUST RUN A FULL AUDIT TO UPDATE AUDIT RETURN CODE.`

Explanation: Displays when you run an internal staging library audit. Solution: You should run the full audit to update the return code.

`CMN2677I` `PACKAGE NOT IN DEV/FRZ STATUS, AUDIT RETURN CODE NOT UPDATED.`

Explanation: Informs you that an audit is being processed for this package and the package status is not DEV for development or FRZ for frozen. Packages determined by audit processing not to be in either DEV status or FRZ status are prevented from having the resulting return code of the audit job updated in the package master.

`CMN2678I` `AUDIT RETURN CODE NOT UPDATED.`

Explanation: Displays when your package was in freeze status, but no components were ever selectively unfrozen. Consequently, the audit return code does not have to be updated.

`CMN2679I` `UNABLE TO OPEN SYSPRINT FILE....`

Explanation: Displays when the system does not allocate the SYSPRINT file.

Solution: You should resubmit the audit job.

`CMN2680I` `UNABLE TO OPEN SYSIN FILE....`

Explanation: Displays when the system is short on DASD space.

`CMN2681I` `CONSTRUCTED {``job type``} JOB TO RESOLVE PACKAGE {``package``} OUT-OF-SYNC FOR {``package id``}.`

Explanation: Displays when you run an audit with audit level 6 turned on. Audit attempts to resolve out-of-synchs by submitting relink/recompile/stage jobs.

`CMN2682I` `PROBLEM ENCOUNTERED TRYING TO SUBMIT {``job type``} JOB TO RESOLVE OUT-OF-SYNC FOR {``package id``}`

Explanation: Displays when ChangeMan ZMF cannot find the necessary information to submit the audit job.

Solution: You should check the SYSPRINT of audit job for missing information.

`CMN2683I` `PRINTING AUDIT REPORT FOR PACKAGE {``package id``}.`

Explanation: Informs you in SYSPRINT that an audit is being run on this package.

`CMN2684I` `INSTALL DATE HAS PASSED, AUDIT RETURN CODE WILL NOT BE UPDATED.`

Explanation: Displays when you try to submit an audit job for a package that has a passed installation date.

`CMN2685I` `UNABLE TO OPEN AUDIT10/20 FILE....`

Explanation: The AUDIT10 file must not be deleted. It is an essential part of the Audit facility.

`CMN2686I` `RECEIVED A BAD RETURN CODE FROM CMNAD000.`

Explanation: Displays when CMNAUD10 encounters a problem while gathering information. This can indicate that the library type has no baseline.

`CMN2687I` `PRIMER RECORD NOT FOUND IN FILE FROM CMNAD000.`

Explanation: Audit10 reads a package master and passes the information that it gathers to Audit20. If a problem occurs during that read, no primer record is written and the job fails.

`CMN2688I` `UNABLE TO OPEN AUDITRPT FILE.....`

Explanation: Displays for a number of reasons, such as out of space, a JCL error, incorrect DCB information, and so forth.

`CMN2689I` `THIS CHANGE PACKAGE HAS PASSED AUDIT.`

Explanation: Displays when a change package has successfully passed Audit.

`CMN2690I` `SERBSAM: UNABLE TO READ A RECORD IN MEMBER {``member name``} WITHIN {``data set``}.`

Explanation: Displays when the READ step initiated for a data set from BSAM encounters a problem after a member is accessed.

`CMN2691I` `INCORRECT TRANSACTION HASH NUMBER {``hash number``}.`

Explanation: Displays when the hash number assigned in the SYSIN card of the submitted job does not match the hash number of the Audit facility.

`CMN2692I` `INCORRECT TRANSACTION HASH NUMBER LOGGED.`

Explanation: Displays when the hash number assigned in the SYSIN card of the submitted job does not match the hash number of the Audit facility. The mismatch is logged.

`CMN2693I` `JOB TERMINATED BY AUDIT EXIT.`

Explanation: Confirms that the audit job has been terminated.

Solution: You should inspect the job output to ensure that the job ran satisfactorily.

`CMN2694I` `THIS AUDIT WILL HAVE TO BE RUN WITHOUT DB2.`

`CMN2695I` `PACKAGE {``package id``} PASSED THE AUDIT WITH A RETURN CODE OF {``return code``}.`

Explanation: Displays after a change package successfully passes an audit.

`CMN2696I` `PACKAGE {``package id``} FAILED THE AUDIT WITH A RETURN CODE OF {``return code``}.`

Explanation: Displays when a change package fails an audit.

Solution: You should check the out-of-synch situation and refer to the ChangeMan ZMF User’s Guide for information about how to resolve the out-of-synch situation.

`CMN2697I` `THE {``job``} JOB TO RESOLVE OUT-OF-SYNCH FOR {``package id``} BYPASSED, NO HISTORY RECORDS TO EXTRACT A COMPILE/LINK PROCEDURE`

Explanation: Displays when audit has bypassed the submission of the job to resolve an out-of-synch condition. This situation occurs when ChangeMan ZMF is unable to locate the source and load record (internally referred to as ISAL) within the package for the component to be auto-resolved. The source and load record is necessary to extract the component’s compile and link information.

Solution: You should conduct a Query Package for the package, then select the SOURCE category. If an entry for the component within the SOURCE category:

Exists, contact Micro Focus Customer Care for assistance.
Does not exist, then the source and load record was not generated for the component when it was staged into the package. Review the stage process for the component and contact Micro Focus Customer Care with this information.

`CMN2698I` `Processed by {``version``} version.`

Explanation: This message from SYSPRINT of an audit job tells what step of the audit you are running (CMNAUD10/CMNAUD20), and the date and time of the Compile.

`CMN2699I` `CANNOT ACCESS I/A TABLE, WILL BYPASS AUDIT PROCESSING`

Explanation: Audit was run and was unable to access the Impact Analysis table. You should be sure the Impact Analysis table is allocated and can be accessed.

`CMN2700` `Component Recompile`

`CMN2700A` `REQUEST CANCELLED | Recompile or Relink request has been cancelled.`

Explanation: Displays when you opt to cancel and exit from the panel that is used to recompile components from baseline or promotion.

Solution: See the “Recompiling and Relinking Packages” chapter in the ChangeMan ZMF User’s Guide.

`CMN2710I` `{``component name``} COMPONENTS SELECTED | {``component name``} components selected to be relinked.`

Explanation: Displays when ChangeMan ZMF has successfully begun the requested recompile of a component.

Solution: See the “Recompiling and Relinking Packages” chapter in the ChangeMan ZMF User’s Guide.

`CMN2711I` `{``component name``} SELECTED | {``component name``} component selected to be relinked.`

Explanation: Informs you which components are selected to be relinked.

`CMN2714I` `INVALID COMMAND | Mass recompile allowed for batch process only.`

`CMN2715I` `{``number of``} COMPONENTS SELECTED | {``number of``} components selected to be recompiled.`

Explanation: Informs you how many components are selected to be recompiled.

`CMN2720A` `INVALID LIBRARY LEVEL | Enter library level from the list below.`

Explanation: Displays when you enter a library level that ChangeMan ZMF does not recognize in the Library List panel (CMNRCMP2).

Solution: You should review the panel options and either re-key the entry or cancel and exit the panel. See the “Recompiling and Relinking Packages” chapter in the ChangeMan ZMF User’s Guide.

`CMN2730A` `NO PROCEDURE FOUND | Specify a Recompile or Relink procedure.`

Explanation: Displays when you enter a ? in the Compiling Procedure field in the Recompile panel (CMNRCMP0) or when the component listed has not been set up with a designated procedure.

Solution: You can either choose any of the project’s procedures or cancel and exit the panel. See the “Recompiling and Relinking Packages” chapter in the ChangeMan ZMF User’s Guide.

`CMN2740I` `RECOMPILE ERROR | Only source or “like-source” components can be recompiled.`

Explanation: Displays when you try to recompile a non-source component.

`CMN2750I` `RECOMPILE ERROR | Components in Checkout or Inactive status cannot be recompiled.`

Explanation: Displays from the stage package driven list when you try to recompile a source component with a checkout or inactive status.

`CMN2755A` `RECOMPILE ERROR | Cannot recompile component with scr/ren request pending.`

`CMN2760I` `RECOMPILE ERROR | The source for this component is already in staging.`

Explanation: Displays to avoid a potential out-of-synch situation between a load module and its corresponding source member. ChangeMan ZMF does not let you stage a SRC member that already exists in the source staging libraries.

`CMN2770I` `{``nnn``} MODULE(S) DELETED | {``nnn``} load modules deleted from staging {``library type``} library.`

Explanation: Informs you how many modules have been deleted from a library. The library type could be LOD, CPY, SRC, and so on.

`CMN2775A` `PROCESS ERROR | Component must be in unfrozen status.`

Explanation: Displays when you select a package in the Recompile panel that contains a component in FRZ status.

Solution: You must either revert the package or selectively unfreeze the component within the Freeze function.

`CMN2776A` `PROCESS ERROR | Relinking from APS library type {``library type``} disallowed.`

`CMN2780A` `PROCESS ERROR | Package must be in DEV status to recompile/relink new modules.`

Explanation: Displays when you select a package in the Recompile panel that has a status other than DEV.

Solution: You must revert the package to development.

`CMN2785I` `Component conflict for {``component``} in package {``package id``}`

Explanation: Displays when the component being processed exists in other change packages that are in motion. This message is issued one time for each package in motion that the component exists in. For example, the message is issued ten times if there are ten packages that contain the component.

`CMN2790I` `RECOMPILE DISALLOWED | Your ID is not authorized to recompile a component.`

Solution: Displays when you try to recompile a component and security protecting recompile is defined, and your ID does not have authority.

`CMN2791I` `REBIND DISALLOWED | Your ID is not authorized to re-bind a component.`

Explanation: Displays when you try to re-bind a component and security protecting rebind is defined, and your ID does not have authority.

`CMN2860I` `DB2 IS NOT LICENSED | DB2 is not licensed for this sub-system.`

Explanation: Displays when you attempt to execute a ChangeMan ZMF Db2 Option function in a ZMF instance that is running without a DB2 Option license.

Solution: Abandon the function you attempted, or obtain a ChangeMan ZMF Db2 Option license from Micro Focus and apply the license to this ZMF instance.

`CMN2861I` `ERO IS NOT LICENSED | ERO is not licensed for this sub-system.`

`CMN2862I` `OFM IS NOT LICENSED | OFM is not licensed for this sub-system.`

CMN2900 Component Compare

`CMN2905A` `NO COMPONENTS FOUND | No components found in the staging library to compare.`

Explanation: Displays when you try to compare a change package that has not yet had any components copied into the staging libraries.

Solution: See the “Staging a Component” chapter and the “Comparing Staging Libraries to Baseline/Promotion” chapters in the ChangeMan ZMF User’s Guide.

`CMN2915A` `LIBRARY TYPE DISALLOWED | Compare of like LOD library type is disallowed.`

Explanation: Displays when you try to compare a change package library that is a load module type (LOD), and it is not allowed.

Solution: See the “Comparing Staging Libraries to Baseline/Promotion” chapter in the ChangeMan ZMF User’s Guide.

`CMN2920A` `COMPONENT NOT FOUND | {``component``} was not found in the staging library.`

Explanation: Displays when you try to compare a component of a change package’s staging library that ChangeMan ZMF cannot find. See the “Comparing Staging Libraries to Baseline/Promotion” chapter in the ChangeMan ZMF User’s Guide.

`CMN2930I` `COMPARE JOB SUBMITTED | The job to compare the staging/baseline libraries was submitted.`

Explanation: Displays when ChangeMan ZMF submits the batch job to compare. See the “Comparing Staging Libraries to Baseline/ Promotion” chapter in the ChangeMan ZMF User’s Guide.

`CMN2935A` `COMPARE ERROR | Only 1 component permitted for PANVALET baseline -xxx level.`

Explanation: Displays when you try to compare more than one component against a minus generation CA-Panvalet baseline library.

`CMN2940A` `DELTA DECK COMPARE | Component must reside in {``data set``} for this Compare.`

Explanation: Displays when the component to be compared is not found in the data set requested.

`CMN2950I` `COMPONENT {``component``} COMPARED | Component {``component name``} was compared.`

Explanation: Confirms that the chosen component was compared.

`CMN2960I` `COMPONENTS COMPARED | {``number of``} component(s) were compared to Baseline/Promotion.`

Explanation: Informs you how many components were compared against a baseline or a promotion library.

`CMN2970I` `COMPONENTS COMPARED | {``variable``} ten components were compared to Baseline/promotion.`

Explanation: Informs you of the first or the next 10 components that were compared against baseline or promotion.

`CMN2980A` `NO STAGING LIBRARIES | This is an empty package. Stage a component to populate it.`

Explanation: Displays when you try to stage an empty package.

Solution: Before attempting to stage a package, you should ensure that it contains one or more components.

`CMN2990I` `DELETE IS BYPASSED | The related staging data sets are allocated to another task.`

Explanation: Displays when you are deleting a component from a package but another user has an enqueue on the staging data set.

`CMN2991I` `ONLINE ONLY | zFS Components may only be compared in online mode.`

CMN3000 Package Freeze

`CMN3000I PACKAGE FROZEN | {``package id``} change package has been frozen.`

Explanation: Displays when ChangeMan ZMF successfully freezes the contents of a change package’s staging libraries.

Solution: See the “Freezing a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3005I` `FREEZE ERROR | {``package``} components must all be at the same promotion level.`

Explanation: Displays when you try to freeze a package containing components that were being promoted to several promotion levels.

Solution: You must either fully promote a package to the appropriate level or fully demote it back to staging level before freezing it.

`CMN3010A` `FREEZE ERROR | {``component``} component is in INACTIVE or CHECKOUT status.`

Explanation: Displays when you try to freeze a change package containing components that have not been staged or activated.

Solution: See the “Utility Requests” chapter, the “Staging a Component” chapter, and the “Freezing a Package” chapters in the ChangeMan ZMF User’s Guide.

`CMN3015A` `FREEZE ERROR | Component {``component``} has an invalid status {``status``}.`

Explanation: Displays when you try to freeze a change package containing components that have not been successfully staged.

Solution: See the “Staging a Component” chapter and the “Freezing a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3017A` `FREEZE ERROR | Participating package requires complex/super relationship.`

Explanation: Displays when you try to freeze a participating package that is not associated with a super or complex package.

`CMN3020A` `FREEZE ERROR | Invalid {``procedure``} used to compile component {``component``}.`

Explanation: Displays when you try to freeze a change package containing components that have been staged without using the designated compiling procedures.

Solution: See the “Staging a Component” chapter and the “Freezing a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3025A` `FREEZE ERROR | Package must be audited when Audit level is greater than 0.`

Explanation: Displays when you try to freeze a change package that has not been audited since the last request to stage.

Solution: See the “Auditing Packages” chapter and the “Freezing a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3026A` `FREEZE ERROR | Package must be audited before selective refreeze can be performed.`

Explanation: Displays when you attempt to selectively refreeze a component or a package category after making a change to a component within that category.

Solution: You should audit the package before selectively refreezing it.

`CMN3030A` `FREEZE ERROR | Conflicting {``action``} and utility information.`

Explanation: Displays when you try to freeze a change package that has a component in the staging library as well as a utility request set up to scratch the component once the package is installed.

Solution: See the “Utility Requests” chapter, the “Staging a Component” chapter, and the “Freezing a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3035A` `AUDIT ERROR | Package needs to be re-audited.`

Explanation: Displays when you edit the members of a previously audited package, or check out new members to this package, and restage the package.

Solution: You should re-audit the package in compliance with the locally set audit rules.

`CMN3036I` `INDICATOR RESET | Freeze in Progress indicator reset.`

Explanation: Displays when two users are freezing a package concurrently. A user freezes the package with batch processing, and another user runs an online freeze on the same package. The user freezing the package online encounters this message.

`CMN3040A` `FREEZE ERROR | Undefined package approval list. Create another package.`

Explanation: Displays when you try to freeze a change package that has been created before the application administrator fully configured the project.

Solution: After the application administrator sets up the complete and abbreviated approval lists, you should create a new package using the current package ID to copy forward, stage all the components using the package driven list, check the utility request list, and then freeze it. See the “Creating a Change Package” chapter, the “Utility Requests” chapter, the “Staging a Component” chapter, and the “Freezing a Package” chapter in the ChangeMan ZMF User’s Guide and the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN3045A` `FREEZE ERROR | Unapproved Online Form: Form ID {``form``}.`

Explanation: Displays when you try to freeze a change package that contains an Online Form that has not been approved. All Online Forms in a change package must be approved before the package can be frozen. (Package approvals are entered after freeze.)

`CMN3046A` `FREEZE ERROR | INACTIVE custom component information.`

`CMN3050A` `FREEZE ERROR | Affected application approval list does not exist.`

Explanation: Displays when you try to freeze a participating change package that was created before the affected application’s application administrator fully configured the project.

Solution: After the application administrator sets up the complete approval lists with interfacing approvers, you should:

Create a new package using the current package ID to copy forward
Stage all the components using the package driven list
Check the utility request list
Freeze the package

See the “Creating a Package,” chapter, the “Utility Requests” chapter, the “Staging a Component” chapter, and the “Freezing a Package” chapter in the ChangeMan ZMF User’s Guide and the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN3055A` `FREEZE ERROR | No package affected application information found.`

Explanation: Displays when you try to freeze a participating change package that has no affected application information entered.

Solution: See the Affected Project panels, CMNCRT05 and CMNPGNL5, and the “Freezing a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3060A` `FREEZE ERROR | This package has failed the Audit.`

Explanation: Displays when you try to freeze a change package that has not passed the audit.

Solution: You should take the necessary steps to resolve the out-of-synch condition, then rerun Audit, and check the summary page of the audit report. See the “Auditing Packages” chapter and the “Freezing a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3064I` `FREEZE ERROR | No components in unfrozen status.`

Explanation: Displays when you try to unfreeze a change package, but either all components in the package are already unfrozen or there are no components in the package.

`CMN3065I` `REFREEZE ERROR | {``component name``} component status must be active/unfrozen before it can be refrozen.`

Explanation: Displays when you try to selectively refreeze a component that has been selectively unfrozen but has not been restaged.

`CMN3066I` `REFREEZE ERROR | No components in active/unfrozen status.`

Explanation: Displays when you try to selectively refreeze components that have been selectively unfrozen, but none of these components are in active status. Freeze requires that all components be in active status before being frozen.

`CMN3067I` `UNFREEZE ERROR | Promotion rule {``promotion rule level``} requires selective demotion prior to unfreeze.`

Explanation: Displays when you try to selectively unfreeze components before selectively demoting them, when the promotion/demotion rule is set to either 1 or 2. These two rules require a selective demotion prior to a selective unfreeze.

`CMN3068I` `UNFREEZE ERROR | Promotion Rule 3 requires full package demotion.`

Explanation: The Promotion Rule becomes more liberal as the number lowers.

Solution: The global and/or application administrator can lower this rule in option 1 under the global and project parameters.

`CMN3069I` `UNFREEZE ERROR | Promotion rule 4 prohibits selective unfreeze. Use REVERT instead.`

Explanation: The Promotion Rule becomes more liberal as the number lowers.

Solution: The global and/or application administrator can lower this rule in option 1 under the global and project parameters. REVERT changes the package status to DEV.

`CMN3070I` `WORK REQUEST # MISSING | Work request number required; update package control information.`

Explanation: Displays when the work number is a required field, and you did not update it before selecting a ChangeMan ZMF function.

`CMN3075I FREEZE BLOCKED | Exit 24 stopped freeze processing. Contact Global Admin.`

Explanation: Displays when Exit 24 stops the freeze process for a change package. Exit 24 checks package installation date at freeze time to assure that specified component library types are installed at specified dates, times, or days of the week.

`CMN3076I FREEZE BLOCKED | Exit 25 stopped freeze processing. Contact Global Admin.`

Explanation: Displays when Exit 25 stops the freeze process for a change package. Exit 25 prevents freezing of a change package if specified compile and link parameters or user options have not been used.

`CMN3080I DEPT. NUMBER MISSING | Department number required; update package general information.`

Explanation: Displays when the department number is a required field, and you did not update it before selecting a ChangeMan ZMF function.

`CMN3090I FREEZE ERROR | Edit in stage is in progress for {``component.type``} by another user.`

Explanation: Displays when you try to freeze a package in batch mode or online mode, but a subsequent user is edit staging a component within the same package.

`CMN3091I Component in use | Edit in stage is in progress for {``dsn.member``} by {``userid``}.`

Explanation: Displays when you try to work with a component in a data set that is currently being used by another user. For example, this can occur when attempting to edit a component in a package when another user is already editing the component. {dsn.member} is the package staging library and member. {userid} is the user that is currently using the component. {userid} is displayed as '(unknown)' if it cannot be determined.

`CMN3095I PACKAGE FROZEN | This package has been frozen since the option was entered.`

`CMN3096I FREEZE DISALLOWED | Your ID is not authorized to freeze change packages .`

Explanation: Displays when you try to freeze a change package and security protecting freeze is defined, and your ID does not have authority.

CMN3100 Package Approval

`CMN3100I` `PACKAGE APPROVED | {``package id``} change package has been approved.`

Explanation: Displays when ChangeMan ZMF receives an approval for the change package staging libraries.

Solution: See the “Approve/Reject” section in the ChangeMan ZMF User’s Guide.

`CMN3105I` `PACKAGE REVIEWED | {``package id``} change package has been reviewed.`

Explanation: Displays when you mark a package for further review.

Solution: See the “Approving or Rejecting a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3110I` `PACKAGE REJECTED | {``package id``} change package has been rejected.`

Explanation: Displays when you reject a change package.

Solution: See the “Approving or Rejecting a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3115I` `PACKAGE RE-DISTRIBUTED | {``package id``} change package has been redistributed.`

Explanation: Displays when an authorized approver signs onto the approval list for a package whose distribution job failed.

Solution: The approver can press the ENTER key to initiate the distribution job again. There is no need to reapprove the package. See the “Approving or Rejecting a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3120A` `APPROVE ERROR | Unfrozen component found. {``component name``}`

Explanation: Displays when you try to freeze a change package containing components that have been selectively unfrozen.

Solution: See the “Approving or Rejecting a Package” chapter and the “Freezing a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3125A` `APPROVE ERROR | You have previously approved this package.`

Explanation: Displays when you try to approve a change package that you have already approved.

Solution: See the “Approving or Rejecting a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3130A` `ALREADY APPROVED | This package has already been approved.`

Explanation: Displays when you try to approve a change package that has already been approved.

Solution: See the “Approving or Rejecting a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3135A` `ALREADY APPROVED | No outstanding approval required for this package.`

Explanation: Displays when you try to approve a change package that has already been approved.

Solution: See the “Approving or Rejecting a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3140A` `NO PACKAGES FOUND | There are no packages awaiting your approval.`

Explanation: Displays when you request a list of packages waiting for approval, and none exist.

Solution: See the “Approving or Rejecting a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3145I` `SEQUENCE ERROR | Your approval/rejection is not next on the hierarchy list.`

Explanation: Displays when you try to approve a package out of sequence for a project that uses a hierarchical approval process.

`CMN3150I` `{``nnn``} APPROVAL(S) STAMPED | {``nnn``} approval(s) have been stamped with your TSOID.`

Explanation: Informs approvers of the number of entities stamped with their TSOID when the rubber stamp approval option is selected from the approval package list.

`CMN3155I` `INCOMPLETE LIST | Maximum number of packages pending approval has been reached.`

Explanation: Displays when the approval list of pending packages to display exceeds the 2600 limit.

`CMN3160A` `APPROVE ERROR | Package creator cannot approve the package.`

Explanation: Displays when you who created a change package try to approve the package.

`CMN3161A` `APPROVE ERROR | Approval is not allowed when approver worked on a component.`

Explanation: Displays when you who worked on a change package component try to approve the package.

`CMN3162A` `APPROVE ERROR | Multiple approvals per user prohibited - contact Admin.`

`CMN3170A` `APPROVE ERROR | Not all approvals have been given for this package.`

Explanation: There are some required approvals for this package that have not yet been processed.

`CMN3180I` `APPROVE STARTED | Package {``package name``} final approval process already in progress.`

Explanation: Displays when the final approver of a change package has elected to approve the package.

`CMN3185A` `INVALID LINE COMMAND | Valid line commands are: Q (query), A (approve), or S (select).`

`CMN3190I` `INDICATOR RESET | Approval in progress indicator reset.`

Explanation: Displays when you opt to reset the “final approval in progress” indicator for a change package.

`CMN3191A` `'PROCESS ERROR' | This package needs to be re-audited.`

`CMN3194I` `Shutdown in progress | ChangeMan ZMF is shutting down, Try later.`

`CMN3195I` `APPROVE DISALLOWED | Your ID is not authorized to approve change packages.`

Explanation: Displays when you try to approve a change package and security protecting approve is defined, and your ID does not have authority.

CMN3200 Package Promote

`CMN3200A` `DEMOTION CANCELLED | Request for demotion has been cancelled.`

Explanation: Displays when you opt to cancel and exit from the series of panels used to demote a change package.

Solution: See the “Promoting and Demoting Changes” section in the ChangeMan ZMF User’s Guide.

`CMN3202A` `DEMOTE REQUIRED | Demotion from {``site``} required before promotion allowed`

Explanation: You must demote from the promotion site displayed in the message before promoting to the site you selected.

`CMN3205I` `INVALID PROMOTION LEVEL | C'I - Selected component(s) not at requested demotion level.`

`CMN3210A PROMOTION CANCELLED | Request for promotion has been cancelled.`

Explanation: Displays when you opt to cancel and exit from the series of panels used to promote a change package.

Solution: See the “Promoting and Demoting Changes” section in the ChangeMan ZMF User’s Guide.

`CMN3215A` `RECOMPILE CANCELLED | Request for Recompile has been cancelled.`

Explanation: Informs you that the Recompile request has been successfully cancelled.

`CMN3216I` `RESTRICTED OPTION | Application restricted from site promotion contact Admin.`

Explanation: Displays when you attempt to do a remote promote for a change package. Remote promotion has been disallowed by either the local or global administrator.

Solution: You should contact the appropriate administrator.

`CMN3220A` `NO ACTIVE COMPONENTS | No active components were found to promote.`

Explanation: Displays when you try to promote a change package but the project’s application administrator has not set up the component types to be promoted.

Solution: See the “Promoting and Demoting Components” section in the ChangeMan ZMF User’s Guide and the “Configuring Promotion Environments and Libraries” section in the ChangeMan ZMF Administrator’s Guide.

`CMN3221I RESTRICTED OPTION | Application is restricted from selective promotion or demotion.`

Explanation: Displays when you try to selectively promote or demote a change package, but the project is restricted from selective promotion or demotion.

`CMN3222I` `UNDEFINED LEVEL | Undefined promotion level; contact Application ADMIN.`

Explanation: Displays when you try to promote a change package, but no promotional environment is defined for the project.

`CMN3224A` `INVALID SCHEDULE DATE | Schedule Date is beyond Install Date.`

Explanation: Correct the promotion schedule date.

`CMN3225A` `PROMOTION ERROR | The highest level of promotion has been reached.`

Explanation: Displays when you try to promote a change package for which there are no more levels of promotion. The levels of promotion libraries have been set up by the project’s application administrator.

Solution: See the “Promoting and Demoting Changes” section in the ChangeMan ZMF User’s Guide and the “Configuring Promotion Environments and Libraries” section in the ChangeMan ZMF Administrator’s Guide.

`CMN3226I` `PROMOTION ERROR | Full promotion to package level is prohibited, use selective promotion.`

Explanation: There are package and component promotion levels. If the package promotion level is higher than the component level, only a selective promotion can be done. The package promotion level is set after a full promotion, not after a selective promotion.

Solution: Re-staging a component sets the component promotion level to 0 (zero). The package promotion level is unchanged. Full promotion or demotion is not allowed unless all components of a package are at the same level.

`CMN3228I` `NOT AT PACKAGE LEVEL | Components found at lower promotion level, demote these first.`

Explanation: Displays when you try to demote a change package with some of its components not at the package promotion level.

Solution: You must selectively demote the remaining promoted components from the level to which they are promoted.

`CMN3230A` `NO COMPONENTS | No components were found to demote.`

Explanation: Displays when you try to demote a change package for which all the components have been previously demoted.

Solution: See the “Promoting and Demoting Components” section in the ChangeMan ZMF User’s Guide.

`CMN3232A` `NO COMPONENTS | {``is not a candidate for {``.`

`CMN3235A` `NOT PROMOTED | This package has no components promoted to this site.`

Explanation: Displays when you try to demote a change package for which there are no lower levels of promotion. The levels of promotion libraries have been set up by the project’s application administrator.

Solution: See the “Promoting and Demoting Changes” section in the ChangeMan ZMF User’s Guide and the “Configuring Promotion Environments and Libraries” section in the ChangeMan ZMF Administrator’s Guide.

`CMN3240A` `DEMOTION ERROR | This package was demoted but was never reverted.`

Explanation: Displays when you try to promote a change package for which all the components have been previously demoted, but not reverted to development status. The package is then refrozen and approved.

Solution: See the “Promoting and Demoting Changes” section in the ChangeMan ZMF User’s Guide.

`CMN3242I` `PROMOTION ERROR | This package was never fully promoted.`

Explanation: Displays when you try to demote a package that has never been promoted.

`CMN3250A` `NO COMMON MODULES | No modules were found that are in common within {``package id``}.`

Explanation: Displays when you try to check for common modules between the current level of promotion for a change package and the next level, but ChangeMan ZMF can find no modules in common.

Solution: See the “Promoting and Demoting Changes” section in the ChangeMan ZMF User’s Guide.

`CMN3252A` `PROMOTION OVERLAY | {``component``} exists in target promotion library, attempt to overlay.`

`CMN3255I` `PROMOTION RESTRICTED | Liberal rule must be specified to promote packages in DEV status.`

Explanation: Displays when you try to promote a package in DEV status, but the project promotion rule has been set to restrict promotion of unfrozen packages.

`CMN3260I` `{``nnn``} COMPONENT(S) DEMOTED | {``nnn``} component(s) demoted from {``promotion library``}.`

Explanation: Displays when you opt to demote any of a change package’s components (as a batch job), and ChangeMan ZMF has submitted the batch job.

`CMN3261I` `REQUEST SUBMITTED | {} request submitted for demotion from {}.`

`CMN3265A` `PROMOTION BLOCKED | Promotion blocked by Exit 27. Contact Global Admin.`

Explanation: Displays when Exit 27 blocks promotion because an administrator has customized it to stop promotion of unplanned packages, override promotion/demotion rules by promotion level or nickname, or override promotion/demotion type (online/ batch) by promotion.

`CMN3270I` `JOB SUBMITTED | The job to {``variable``} this package has been submitted.`

Explanation: Displays when you opt to promote/demote or freeze a change package’s components (as a batch job), and ChangeMan ZMF has submitted the batch job.

`CMN3280I` `{``nnn``} COMPONENT(S) PROMOTED | {``nnn``} component(s) promoted to {``promotion library``}.`

Explanation: Informs you how many components are selected to be promoted.

`CMN3281I` `{}REQUEST SUBMITTED | {} request submitted for promotion to {}.`

`CMN3285A` `AUTHORIZATION FAILED | Not authorized to promote/demote this package. Contact Admin.`

Explanation: Displays when you try to promote or demote a change package, but does not have promotion or demotion authority for the application.

Solution: You should contact the application administrator for promotion/demotion authority.

`CMN3286I` `INACTIVE MEMBERS | Warning - Not all promotion candidates are in active status.`

Explanation: There are package components in promotable library types that are not in ACTIVE status. These components cannot be promoted. Components in ACTIVE status in promotable library types will be promoted.

`CMN3288I` `PACKAGE UPDATED | Demotion found no components but the package level was updated.`

`CMN3289I` `DEMOTION ERROR | Demotion Level can only be as high as the current package level.`

`CMN3290A` `INVALID REQUEST | Enter one of the listed actions.`

Explanation: Displays when you enter an invalid option during the promotion/demotion function.

`CMN3291I` `MEMBER NOT FROZEN | Component {``component name``} must be frozen for promotion rule {``rule``}.`

Explanation: Displays when you try to promote an unfrozen component, and the administrator has defined a promotion rule rule. You can only promote unfrozen components when the administrator has defined a promotion rule of rule.

`CMN3292I PROMOTION ERROR | Component is currently promoted to this level.`

`CMN3293I` `PROMOTION ERROR | Level skipped, not allowed for promotion rule greater than 0.`

Explanation: Displays when you attempt to promote directly to some level but the promotion rule does not allow skipping a level. See your administrator for the rules on promotion in this file.

`CMN3294I` `PROMOTION ERROR | All components must be frozen for promotion rule greater than 0.`

Explanation: Displays when you try to promote a change package that contains one or more unfrozen components, and the administrator has defined a promotion rule greater than 0. You can only promote packages that contain unfrozen components when the administrator has defined a promotion rule of 0.

`CMN3295I` `PROMOTION ERROR | Selective demotion prohibited when demotion rule is 3 or 4.`

Explanation: Displays when the global administrator or the application administrator has defined a promotion rule greater than 2.

Solution: You should perform a full demotion only for rule 3 or 4, or the administrator should change the rule to 0, 1, or 2, which allows selective promotion and demotion.

`CMN3296I` `PROMOTION ERROR | Selective promotion beyond the package level is prohibited.`

Explanation: Displays when you try to promote a component to a higher promotion level than the level defined for the package.

Solution: You should re-promote the package to a higher level, or specify a level lower than the current package level.

`CMN3297I` `COMPONENT ERROR | Mixed promotion level prohibited, components not at the same level.`

Explanation: Displays when you try to promote a change package whose components are not all at the same level.

`CMN3298I` `DEMOTION ERROR | Full demotion only allowed from package level.`

Explanation: Displays when you try to demote a change package whose components are not all at the same level.

`CMN3299I` `PROMOTE DISALLOWED | Your ID is not authorized to promote change packages.`

Explanation: Displays when you try to promote a change package and security protecting promote is defined, and your ID does not have authority.

CMN3300 Package Revert

`CMN3300I` `PACKAGE REVERTED | Package has been reverted to development.`

Explanation: Confirms that the package was reverted from FRZ or BAK status to DEV status.

`CMN3310A` `REVERT ERROR | Approval process is under way or you have already given your approval.`

Explanation: Displays when you try to revert a change package that is already approved by you to development status.

Solution: See the “Reverting a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3311I` `REVERT ERROR | Package has already been reverted.`

`CMN3315A` `REVERT ERROR | Revert authority needed to revert packages with {``status``} status.`

Explanation: Displays when you, with insufficient authority, try to revert a change package to development status.

Solution: See the “Reverting a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3320A` `REVERT ERROR | Packages in {``status``} status cannot be reverted. Use Backout.`

Explanation: Displays when you try to revert a change package that has already been installed in Production back to development status.

Solution: See the “Reverting a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3321A` `'REVERT ERROR' | Package already installed at this site, backout package first.`

`CMN3322A` `'REVERT ERROR' | Package installed at {, REVERT disallowed at this time.`

`CMN3325A` `REVERT ERROR | Package must be demoted before it can be reverted.`

Explanation: Displays when you try to revert a change package that has been promoted back to development status.

Solution: See the “Reverting a Package” chapter in the ChangeMan ZMF User’s Guide.

`CMN3330A` `REVERT ERROR | Reverting a package with DIS status in DEV environment is disallowed.`

Explanation: Displays when you try to revert a change package and either does not have revert authority, or is not attempting the revert in the production environment. Someone with revert authority must revert a package in DIS status at the remote site.

`CMN3335A` `REVERT ERROR | Package needs to be reverted or selectively unfrozen.`

Explanation: Displays when you attempt a function on a change package, but that function is not allowed unless the package is either reverted or selectively unfrozen.

`CMN3340I` `REVERT DISALLOWED | Post rejected packages must be backed out from production.`

Explanation: Displays when an unplanned change package that has been moved into production fails to receive post-install approval.

Solution: You must back out the package from production.

`CMN3345I` `NOT INSTALLED | Package not installed at this site - {``site name``}.`

Explanation: Displays when you try to revert a package at one site, but the package actually belongs to another site.

`CMN3350I` `Package {``package name``} reverted by {``userid``} on {``date``}.`

Explanation: Informs you who created the package name that userid reverted the package on date.

`CMN3355I` `REVERT DISALLOWED | Package {``package``} installation process has already started.`

CMN3400 Package Delete

`CMN3400I` `PACKAGE MEMO DELETED | {``package id``} change package has been memo deleted.`

Explanation: Displays when you set up a memo to delete a change package.

Solution: See the “Deleting and Undeleting Packages” chapter in the ChangeMan ZMF User’s Guide.

`CMN3405I` `PACKAGE UNDELETED | {``package id``} package - memo delete status has been removed.`

Explanation: Displays when you request ChangeMan ZMF to remove the Delete Memo from a change package.

Solution: See the “Deleting and Undeleting Packages” chapter in the ChangeMan ZMF User’s Guide.

`CMN3420A` `NO PACKAGES FOUND | No memo deleted packages found in the Package Master.`

Explanation: Displays when you request a list of change packages that have been set up with a Delete Memo, but none exist.

Solution: See the “Deleting and Undeleting Packages” chapter in the ChangeMan ZMF User’s Guide.

`CMN3425A` `MEMO DELETE ERROR | {``package id``} package is already in memo deleted status.`

Explanation: Displays when you attempt to memo delete a package already in DEL status.

Solution: See the “Deleting and Undeleting Packages” chapter in the ChangeMan ZMF User’s Guide.

`CMN3430A` `UNDELETE ERROR | {``package id``} package is not in memo deleted status.`

Explanation: Displays when you try to remove a change package Delete Memo for a package that has no Delete Memo placed on it.

Solution: See the “Deleting and Undeleting Packages” chapter in the ChangeMan ZMF User’s Guide.

`CMN3435I` `MEMO DELETE ERROR | Package must be fully demoted before package can be memo deleted.`

Explanation: Displays when you try to memo delete a package that contains at least one component that is promoted.

Solution: Fully demote the package in all sites, then memo delete the package.

`CMN3440I` `MEMO DELETE ERROR | Package still contains one or more components.`

Explanation: Displays when the MEMO DELETE EMPTY PACKAGES ONLY parameter is set in Application Administration and you attempt to memo delete a package that contains components. (You may memo delete a package with scratch or rename utility requests.)

Solution: Delete all components in the package, and then memo delete the package.

`CMN3450I` `DELETE ERROR | {``package name``} package is not in DEV or memo deleted status.`

Explanation: Displays when you try to physically delete a change package that is not in DEV or Memo Delete status.

`CMN8767I` `Delete prohibited | Linked package cannot be deleted. Please unlink the package first.`

Explanation: The package is linked in TeamTrack.

Solution: Unlink the package in TeamTrack and reissue the delete request in ChangeMan ZMF

CMN3500 Package Backout

`CMN3500I` `BACKOUT JOB SUBMITTED | The job to back out this package has been submitted.`

Explanation: Displays when you opt to back out a change package’s components from production and ChangeMan ZMF has submitted the batch job.

`CMN3510I` `FULL BACKOUT ERROR | Package staging data sets aged or backup library overlaid.`

Explanation: Displays when you try to back out a change package in Production, but the package’s staging data sets have already been deleted by housekeeping tasks. This message also displays if you attempt to backout a change package that contains components that have been installed more recently by another change package, and have overlaid the contents of the specified package.

`CMN3520I` `SELECTIVE BACKOUT ERROR | Selective backout of aged or overlaid component is disallowed.`

Explanation: Displays when the following situations occur. This message also displays as a result of the package being aged.

Package A is installed into production.
Package B, which contains some of the same components as package A, is subsequently installed.
Package A is backed out.

`CMN3530I` `NO COMPONENTS FOUND | No components found to list for this package.`

Explanation: Displays when you select the List option from the main Backout panel for packages installed in production, and there is no backup component information in the package master.

`CMN3540A` `UNDEFINED BKUP LIBRARY | Backup libraries undefined. Contact Local Admin.`

Explanation: The application administrator must define the backup production libraries in the project parameters option B, BASELINE.

`CMN3550I` `BACKOUT DISALLOWED | Your ID is not authorized to backout change packages.`

Explanation: Displays when your TSOID lacks authority to back out a change package.

Solution: You should contact the systems security administrator for backout authority. The proper entity is CMNBKOUT.

`CMN3560I` `BACKOUT DISALLOWED | Package with REJ status can only be backed out if post rejected.`

Explanation: Occasionally, emergency change packages are installed that require later approval. If the package is not approved (post rejected) it has to be backed out. Unless this scenario occurs, you cannot back out the package.

`CMN3570I` `BACKOUT DISALLOWED | Package backout process already started.`

CMN3600 List

`CMN3600A` `INVALID LINE COMMAND | {``command``} line command is invalid - valid line commands are {``list of valid line commands``}`

Explanation: Displays when you enter an invalid line command from the package list panel.

Solution: You should enter one of the line commands displayed in the list of valid commands.

`CMN3610A` `INVALID SELECTION CODE | S (Select) is the only valid selection code.`

Explanation: Displays when you enter an invalid selection code.

Solution: You should enter S, the only valid selection code.

CMN3611 IMS Option

`CMN3611A` `IMS System Lib Gen''d | {``imsid``} IMS System Libraries generated.`

`CMN3612A` `UNDEFINED IMS SYSTEM' | IMS global system libraries are not defined.`

`CMN3613I` `INFORMATION SAVED | Package IMS system information saved.`

`CMN3614I` `INFORMATION SAVED | Package ACB statement information saved.`

`CMN3615I` `INFORMATION SAVED | Package DBD statement information saved.`

`CMN3616I` `INFORMATION SAVED | Package PSB statement information saved.`

`CMN3617I` `IMS IS NOT LICENSED | IMS is not licensed for this sub-system.`

`CMN3618A` `NO IMS LIBRARY TYPES | No IMS Library Types have been defined by Global Admin.`

Explanation: Displayed when you attempt to select option 2 Library Types on the GLOBAL IMS ADMINISTRATION panel (CMNIGGEN) when no library type is defined in global administration with SEL. OPT. set to I.

Solution: Define a global IMS library type by setting the SEL. OPT. to I on the GLOBAL LIBRARY TYPES PART 1 OF 2 panel (CMNCGLT0).

`CMN3619A` `NO IMS LIBRARY TYPES | No IMS Library Types have been defined by Application Admin.`

Explanation: Displayed when you attempt to select option 2 Library Types on the application - IMS ADMINISTRATION panel (CMNILGEN) when no library type is defined in application administration with SEL. OPT. set to I.

Solution: Define an IMS library type for this application by setting the SEL. OPT. to I on the application - LIBRARY TYPES PART 1 OF 2 panel (CMNCLLT0).

`CMN3620A` `UNDEFINED IMS SYSTEMS | IMS application system libraries are not defined.`

Solution: Contact ChangeMan ZMF Administrator.

`CMN3621I` `UPDATE SUCCESSFUL | Global IMS library subtypes updated successfully.`

Explanation: IMS global library sub-types on the GLOBAL IMS LIBRARY SUBTYPES panel (CMNIGLT0) are updated successfully.

Solution: No action required.

`CMN3622I` `UPDATE SUCCESSFUL | Application IMS library subtypes updated successfully.`

Explanation: IMS application library sub-types on the application - IMS LIBRARY SUBTYPES panel (CMNILLT0) are updated successfully.

Solution: No action required.

`CMN3625A` `Y/N on IMS Activation | IMS Activation field takes Y/N as values.`

`CMN3626A` `Y/N on IMS DBD | IMS DBD Processing field takes Y/N as values.`

`CMN3627A` `Y/N on IMS MFS | IMS MFS Processing field takes Y/N as values.`

`CMN3628A` `Y/N on IMS PSB | IMS PSB Processing field takes Y/N as values.`

`CMN3629A` `Y/N on IMS ACB | IMS ACB Processing field takes Y/N as values.`

`CMN3630I` `DBD Overrides Gen''d | {``dbd``} DBD override statements generated.`

`CMN3635I` `PSB Overrides Gen''d | {``psb``} PSB override statements generated.`

...

`CMN3636I` `MISSING CONTROL STMT | {``statement``} Control statement is a required field.`

`CMN3640I` `MISSING SOURCE NAME | {``name``} Source name is a required field.`

`CMN3641I` `MISSING LIBRARY TYPE | Library type is a required field.`

`CMN3642A` `IMS ID UNDEFINED | IMS ID {``imsid``} is undefined.`

`CMN3643I` `IMS System Lib Gen''d | Global IMS System Library generated.`

`CMN3644I` `MISSING ORIGINAL STMT | {``statement``} Original statement is a required field.`

`CMN3645I` `MISSING OVERRIDE STMT | {``statement``} Override statement is a required field.`

`CMN3646A` `UNDEFINED IMS TYPES | {``library_type``} IMS library sub-types are undefined, contact the Admin.`

`CMN3647A` `IMS CONTROL REGION ERROR | Global IMS Control Region Undefined.`

`CMN3648A` `IMS CONTROL REGION ERROR | Application IMS Control Region Undefined.`

`CMN3649A` `IMS CONTROL REGION ERROR | Package IMS Control Region Undefined.`

`CMN3654A` `IMS ID missing | IMS ID is a required field`

`CMN3655A` `IMS ID invalid | IMS ID must start with alpha character.`

`CMN3671A` `INVALID IMS TYPE | Library type specified is not an IMS type.`

`CMN3672A` `INVALID IMS TYPE | Library type is not a {``library-type``} source type.`

`CMN3675A` `INVALID DEVCHAR | DEVCHAR can not be blank and is a required field.`

`CMN3680A` `INVALID SITE ID | IMS Site ID does not match the Remote Site.`

`CMN3685A` `INVALID REMOTE SITE | Remote Site does not match the IMS Site ID.`

`CMN3689A` `INVALID IMS REFERAL LIB | IMS REFERAL data set is undefined.`

`CMN3690A` `INVALID IMS BACKUP | IMS backup high level node is undefined.`

`CMN3691A` `INVALID IMS GEN LIB | IMS GEN MACRO data set is undefined.`

`CMN3692A` `INVALID IMS GEN MEMBER | IMS GEN MACRO member is undefined.`

`CMN3693A` `INVALID IMS RESLIB | IMS RESLIB data set is undefined.`

`CMN3694A INVALID IMS MODSTAT | IMS MODSTAT data set is undefined.`

`CMN3695A` `INVALID IMS MACLIB | IMS MACLIB data set is undefined.`

`CMN3696A` `INVALID IMS PSBLIB | IMS PSBLIB data set is undefined.`

`CMN3697A` `INVALID IMS DBDLIB | IMS DBDLIB data set is undefined.`

`CMN3698A` `INVALID IMS ACBLIB | IMS ACBLIB data set is undefined.`

`CMN3699A` `INVALID IMS FORMAT LIB | IMS FORMAT data set is undefined.`

CMN3700 Browse Log

`CMN3700I` `LIST PRINTED | List {``list name``} printed.`

Explanation: Confirms that the requested browse list has been printed.

`CMN3710I` `LIST DELETED | List {``list name``} deleted.`

Explanation: Confirms that the requested browse list has been deleted.

`CMN3715I` `LIST KEPT | List {``list name``} kept.`

Explanation: Confirms that the requested browse list has been kept.

`CMN3720I` `PRINT JOB SUBMITTED | Job to print list {``list name``} submitted.`

Explanation: Confirms that the job to print the requested browse list has been submitted.

`CMN3725I` `INVALID BASELINE | Baseline library type is not a compressed listing library.`

`CMN3800A` `INVALID LINE COMMAND | “S” is the only valid line command.`

Explanation: Currently, S (select) is the only valid line command for the Log Browse function.

CMN3900 Monitor

`CMN3900A` `INVALID INSTALL TIME | Install time must be current or in the future.`

Explanation: Displays when you request a time that has passed, instead of a current or future time.

`CMN3905I` `DATA SET NOT ALLOCATED | Distribution library for this package has not been allocated.`

Explanation: Displays when you try to submit a job, but the distribution library for that package has not been allocated.

`CMN3910I` `JOB SUBMITTED | Job {``job name``} submitted from {``library name``}.`

Explanation: Displays so that you can determine the library from which a specified job was submitted. You can manually resubmit a job that has failed and ended up in limbo status.

`CMN3915I` `STATUS CHANGED | Status for package {``package name``} has been changed to {``package status``}.`

Explanation: Displays when the package status is successfully changed.

`CMN3920A` `UNKNOWN STATUS | Status to be changed is unknown for this package type.`

Explanation: Displays when the package status is unknown.

`CMN3925I` `INSTALL DATE CHANGED | Install date for package {``package name``} has been changed to {``install date``}.`

Explanation: Displays when the installation date has been changed to the newly requested installation date.

`CMN3930I` `PACKAGE DELETED | The requested packages have been deleted.`

Explanation: Displays when the requested change packages have been deleted from the package master.

`CMN3935I` `NO PACKAGE IN LIMBO | There are no packages currently in limbo.`

Explanation: Informs you that there are no change packages in limbo at this moment.

`CMN3940A` `LINE COMMAND REQUIRED | Line command required to change status or date/time.`

Explanation: Displays when you try to change the package status or installation date and time, in the monitor packages in the limbo option of ChangeMan ZMF, without specifying the line command that directs the change that should take place.

`CMN3950A` `INVALID PACKAGE LEVEL | Super/Complex packages do not have an install date.`

Explanation: Displays when you try to change the installation date for super/complex packages.

Solution: Super/complex packages do not use installation date and time information.

`CMN3955A` `INVALID OPTION | Super/Complex packages do not have any jobs to submit.`

Explanation: Displays when you try to submit a job for super/complex packages. Super/complex packages do not submit jobs.

`CMN3960I` `INVALID STATUS | Status change invalid participating packages still in motion.`

Explanation: Displays when you try to close a super or complex package, and one or more of its associated participating packages is still in motion.

Solution: You should either baseline the participating package or delete it from the super or complex package.

`CMN3965I` `INVALID STATUS | DEL status change invalid; participating packages still attached.`

Explanation: Displays when you try to delete a super or complex package that has participating packages still attached.

Solution: You should remove all associations before deleting a super/complex package.

`CMN3970I` `INVALID STATUS | DEL status change invalid; still attached to a Super/Complex pkg.`

Explanation: Displays when you try to delete a participating package that is still attached to a super/complex package.

Solution: You should remove all associations before deleting a participating package.

CMN4000 Query

`CMN4000A` `INVALID SELECT CMD | Enter ‘S’ to select package(s) to query.`

Explanation: Displays when you enter a line command that ChangeMan ZMF does not recognize.

Solution: You should review the panel options and enter S, or cancel and exit.

`CMN4005A` `INVALID DATE RANGE | FROM install date is more current than TO install date.`

Explanation: Displays when you enter a FROM installation date that is closer to the current date than the TO installation date.

Solution: See the “Querying Packages and Components” chapter in the ChangeMan ZMF User’s Guide.

`CMN4010A` `INVALID DATE RANGE | FROM creation date is more current than TO creation date.`

Explanation: Displays when you enter a FROM creation date that is closer to the current date than the TO creation date.

Solution: See the “Querying Packages and Components” chapter in the ChangeMan ZMF User’s Guide.

`CMN4015A` `INVALID DATE RANGE | FROM query date is more current than TO query date.`

Explanation: Displays when you enter a FROM Query date that is closer to the current date than the TO Query date. See the “Querying Packages and Components” chapter in the ChangeMan ZMF User’s Guide.

`CMN4020A` `END OF PACKAGE LIST | All packages have been displayed.`

Explanation: Displays when you request to view more packages that meet the selection criteria, but there are no more.

`CMN4025A` `END OF COMPONENT LIST | All components have been displayed.`

Explanation: Displays when you request to view more components that meet the selection criteria, but there are no more.

`CMN4030A` `NO PACKAGES FOUND | No package(s) to list.`

Explanation: Displays when you request to view more packages that meet the selection criteria, but there are no more.

`CMN4035A` `INVALID COMMAND | For valid commands, enter ‘COMMANDS’.`

Explanation: Displays when you enter an invalid command.

Solution: You should type commands to display a list of valid commands.

`CMN4040A` `COMPONENT NOT FOUND | Component is not in the Package Master.`

Explanation: Displays when you request to view a specific component’s history, but there is no historical information for the component.

`CMN4045A` `NO LIBRARIES FOUND | No staging libraries found for this package.`

Explanation: Displays when you request to view change package staging information, but there is no more information on your request.

`CMN4050A` `NO INFORMATION FOUND | No revert reasons found for this package.`

Explanation: Displays when you request to view change package revert reasons, but none exist.

`CMN4055A` `NO INFORMATION FOUND | No backout reasons found for this package.`

Explanation: Displays when you request to view change package backout reasons, but none exist.

`CMN4058A` `NO INFORMATION FOUND | No reject reasons found for this package.`

Explanation: Displays when you request to view package reject reasons, but none exist.

`CMN4060A` `NO INFORMATION FOUND | No on site information found for this package.`

Explanation: Displays when you request to view change package on site information, but none exists.

`CMN4065A` `NO INFORMATION FOUND | No non-source component found for this package.`

Explanation: Displays when you request to view non source change package components, but none exist.

`CMN4070A` `NO INFORMATION FOUND | No source and load component found for this package.`

Explanation: Displays when you request to view change package source and load components, but none exist.

`CMN4075A` `NO INFORMATION FOUND | No utilities component found for this package.`

Explanation: Displays when you request to view package utility requests, but none exist.

`CMN4080A` `NO INFORMATION FOUND | No production libraries found for this application.`

Explanation: Displays when you request to view project information, but none exists.

`CMN4085A` `NO INFORMATION FOUND | No baseline libraries found for this application.`

Explanation: Displays when you request to view project information, but none exists.

`CMN4090A` `NO INFORMATION FOUND | No promotion/demotion history found for this package.`

Explanation: Displays when you select promotion history from query, but the change package has never been promoted before; therefore, it has no history.

Solution: You should promote the change package and give it a history.

`CMN4092A` `NO INFORMATION FOUND | No promotion libraries found for this application.`

Explanation: Displays when the application administrator has not defined any promotion libraries for this application.

Solution: You should contact the application administrator.

`CMN4095A` `INVALID PACKAGE LEVEL | Package level must be “Super” or “Complex”.`

Explanation: Displays when you request to view participating package information, but the reference package is not the level-type that would have such information.

`CMN4100A INVALID PATTERN | Valid patterns are X* or XXXXXX*.`

Explanation: Displays when you request to view components whose names follow a certain pattern, but the pattern entered is not a valid one.

`CMN4102A INVALID PATTERN | {``pattern``} must be * or explicit, not partially wildcarded.`

`CMN4105A INVALID PATTERN | Valid patterns are X* or XX*.`

Explanation: Displays when you request to view components whose library types follow a certain pattern, but the pattern entered is not a valid one.

`CMN4110A NO APPROVAL LIST | Super/Complex package does not have an approval list.`

Explanation: Displays when you request to view the approval list for a super or complex package type.

`CMN4120I NO RELATIONSHIPS | No relationship found for criteria.`

Explanation: Displays when no relationship is found for the requested criteria.

`CMN4130I BROWSE ERROR | Staging data set is either Archived or Aged.`

Explanation: Displays when you try to browse a staging library member that has either been archived or aged.

Solution: You should restore the member if it has been archived. If the member has been aged, it has either been deleted or moved.

CMN4200 Browse Log

`CMN4200I` `END OF LOG | You have reached the end of the log file.`

Explanation: Displays when you request to view more log entries that meet the selection criteria, but there are no more.

`CMN4205A` `INVALID DATE RANGE | FROM date is more current than the TO date.`

Explanation: Displays when you enter a FROM date that is closer to the current date than the TO date.

`CMN4210A` `INVALID DATE {``date``} is an invalid Gregorian date.`

Explanation: Displays when you enter a log date range that is not in the same format (YY/MM/DD) as shown on the Browse Activity Log Facility panel, CMNLOGEX.

Solution: You should review and reenter the date range, or cancel and exit.

`CMN4215I` `EMPTY LOG FILE | No activities found in the Log file.`

Explanation: Displays when you request to view more log entries that meet the selection criteria, but there are no more.

CMN4300 Internal Scheduler Monitor

`CMN4300A` `NO SCHEDULING DATA | No scheduling information found in the package master.`

Explanation: Displays when you try to obtain a list of change packages scheduled to be installed into production by the internal scheduler, but none exist.

`CMN4310A` `PACKAGE NOT INSTALLED | Submit is for de-installing installed temporary packages only.`

Explanation: Displays when you try to submit a job that cycles a temporary change package into production, but the temporary package was never installed.

`CMN4320A` `INVALID PACKAGE TYPE | Submit request only valid for installed temporary packages.`

Explanation: Displays when you try to submit a job that cycles a temporary change package into production, but the package is a permanent package.

`CMN4330I` `INFORMATION SAVED | The requested changes have been saved.`

CMN4400 Query Monitor

`CMN4400A` `INVALID FIELD | First character cannot be an asterisk.`

Explanation: Displays when the first character of the component field is an asterisk. The first character must be an alphabetic character.

`CMN4401I` `Release Detach Error | Package {``package``} Still has components not retrieved from Release.`

`CMN4402I` `Release Update Error | Use ATTACH/DETACH to change package release or area.`

`CMN4420A` `INVALID FIELD | First character cannot be numeric.`

Explanation: Displays when the first character of the component field is a numeric character. The first character must be an alphabetic character.

`CMN4430I` `QUERY ERROR | Unique baseline number table not loaded.`

`CMN4435I` `QUERY ERROR | Unique baseline number not found in table.`

Explanation: Displays when another baseline was defined that is not part of a user’s table.

Solution: You should run Impact Analysis Data Extract and Load.

`CMN4440I` `QUERY ERROR | Invalid query criteria.`

Explanation: Displays when you enter invalid information in the Query panel.

Solution: You should check the entered fields and correct the entries.

`CMN4445I` `Restricted Query | The query criteria are too generic - see help panel for details.`

`CMN4446I` `Invalid Value | The relationship value is not valid - see help panel for details'.`

CMN4500 Impact Analysis Table Generation

`CMN4500I` `No applications have been defined in the Package Master.`

Explanation: There are no applications defined in application administration, so there are no baseline libraries for the impact analysis data extract program CMNIA000 to process.

Solution: Add applications and define baseline libraries in application administration, then initiate impact analysis synchronization again, either online (=A.G.I) or in batch (sample job IMPACT).

`CMN4501A` `Output Task initiation failed.`

Explanation: This message is issued when an attempt was made to initiate the Output Subtask and a bad return code was returned from the ATTACH macro. The job is terminated with a return code of 24, indicating a severe error.

`CMN4502A` `No PARM= parameters were supplied.`

Explanation: This message is issued when no parameter information was specified on the EXEC JCL card. A minimum of the SUBSYS= and USER= must be specified to run Assist. The job is terminated with a return code of 12.

`CMN4503A` `SUBSYS= parameter was not specified.`

Explanation: This message is issued after parsing the PARM= parameter on the EXEC JCL card and it is found that the SUBSYS= parameter was not specified. This parameter is required to run Assist. The job is terminated with a return code of 12.

`CMN4504A` `USER= parameter was not specified.`

Explanation: This message is issued after parsing the PARM= parameter on the EXEC JCL card and it is found that the USER= parameter was not specified. This parameter is required to run Assist. The job is terminated with a return code of 12.

`CMN4505A` `BUNSPACE DD statement missing.`

Explanation: The DD statement BUNSPACE is missing from your JCL.

Solution: Correct JCL and resubmit.

`CMN4507A` `Unable to initialize the I/A dataspace, Terminating.`

Explanation: Check that the //CMNIMPCT DD statement is present, and pointing to the correct dataset (CMNTP.SERT3.CMNZMF.IADSP for example). Check that the I/A dataset has been initialized by LDSINIT or similar utility.

`CMN4508A` `Max. excluded libtypes (1360) reached - Please contact Micro Focus Customer Care`

`CMN4509A` `Max. no. of copybooks (4096) in a source component reached - Please contact Micro Focus Customer Care.`

`CMN4510I` `Unable to allocate {``library type``} baseline data set.`

Explanation: Displays when there is an invalid library name. This is probably caused by a syntax error.

`CMN4511I` `Warning - copybook record already exists for {``member``}.`

`CMN4516A` `Dataspace error | return code is {``return code``}.`

`CMN4517I` `Create disallowed | BUN entry already exists for {``entry``}.`

...

`CMN4518I` `Update disallowed No BUN entry found for {``entry``}.`

`CMN4519I` `Delete disallowed BUN entry for {``bun#``} is in use.`

`CMN4520I` `SERIFACE encountered problem processing {``component name``}.`

Explanation: This program cannot read a CA-Panvalet or CA-Librarian data set. This problem can occur for a number of reasons, such as a missing library access number or no authority.

`CMN4521I` `Delete failed | BUN entry for {``entry``} was not found.`

`CMN4522I` `Create failed | Unable to insert component entry {``component``}.`

`CMN4523I` `Update failed | Component entry {``component``} not found.`

`CMN4524I` `Create failed | Unable to insert relationship entry for {``relationship``}.`

`CMN4525I` `Update failed | relationship entry for {``relationship``} not found.`

`CMN4526I` `Delete failed | Relationship entry for {``relationship``} not found.`

`CMN4527I` `Create failed | Failure in baseline update for {``component``}.`

...

`CMN4528I` `Delete failed | Failure in baseline delete for {``component``}.`

`CMN4529I` `Commit failed | Dynamic baseline update commit failed.`

Explanation: Program CMNDSPTM in the CMN30 job attempted to update the impact analysis data space, and the attempt failed, usually because of an overflow condition. Baseline ripple is allowed to complete, but step DSPTM in the CMN30 job gives RC=04.

Solution: Follow the instructions displayed with the message: Run the Impact Analysis Data Extraction to synchronize your impact analysis data with your baselines, then run your LDSLOAD job to resize the impact analysis data space and load the new BUNSPACE, CMPSPACE, and RELSPACE sequential files.

`CMN4530A` `CMNDSPTM has detected possible I/A dataspace corruption`

Explanation: This message is displayed when program CMNDSPTM in an install job detects possible data corruption in the impact analysis data space. Note: The maximum return code for a DSPTM step in an installation job is 4 because package installation should not fail because of a problem in updating impact analysis data. Message CMN4530A is written to the operator console (WTO) so that it can be detected by automated data center tools.

Solution:

For analysis and diagnosis, retain a copy of the install job output, and make a copy of the impact analysis LDS with sample JCL member LDSBKUP (IDCAMS).
Be prepared to recover the data space with sample JCL member LDSFWDR by retaining LDS backups from before the failed update and all IALOG backups from that point until the present.
Contact Micro Focus Customer Care.

`CMN4531A` `Library Task initiation failed.`

Explanation: This message is issued when an attempt was made to attach a Library Processing Subtask and a bad return code was returned from the ATTACH macro. The job is terminated with a return code of 24.

`CMN4532A` `CMNDSPTM/CMNIAIXC has abended - possible I/A dataspace corruption.`

`CMN4533A` `Release audit subtask abended, unable to continue.`

Explanation: See above.

`CMN4534A` `CMNIA000 subroutine {``subroutine``} is at the wrong level. Please ensure your software mix is consistent.`

Explanation: STEPLIB/JOBLIB concatenations must be the same for the ChangeMan ZMF started procedure, the TSO CLIST used to access the started task, the TSO CLIST used to access XML SERVICES, and the CMNxADSP file tailoring procedures.

`CMN4536A` `CMNIA000 the APPL sysin parameter is mutually exclusive with the EXCL parameter.`

Explanation: Use either APPL or EXCL, not both.

`CMN4537A` `CMNIA000 the XTYP keyword can not be specified for an excluded application.`

Explanation: See above.

`CMN4540I` `Unable to get record from SERBSAM.`

Explanation: This program cannot read a PDS data set. This problem can occur for a number of reasons, such as a missing library access number or no authority.

`CMN4570A` `{ is defined as {and {.`

Explanation: The baseline library is defined with different storage means in two applications. Impact Analysis bypasses any baseline library that is defined with more than one storage means.

CMN4571 CMNBAT90

For a detailed description of utility program CMNBAT90, see the ChangeMan ZMF Customization Guide.

`CMN4571A` `Unable to open SYSIN input file.`

Explanation: No SYSIN DD statement was found. Keyword statements required for the execution of program CMNBAT90 are input at the SYSIN DD statement.

Solution: Ensure that the CMNBAT90 JCL includes a SYSIN DD statement. See the description of utility CMNBAT90 in the ChangeMan ZMF Customization Guide.

`CMN4572A` `Unable to open BAT90IN file.`

Explanation: No BAT90IN DD statement was found. The library containing the new module to be registered in the package master is input to program CMNBAT90 at the BAT90IN DD statement.

Solution: Ensure that the CMNBAT90 JCL includes a BAT90IN DD statement. See the description of utility CMNBAT90 in the ChangeMan ZMF Customization Guide.

`CMN4573A` `Unable to open BAT90OUT file.`

Explanation: No BAT90OUT DD statement was found. Program CMNBAT90 writes transactions for program CMNBATCH to the BAT90OUT DD statement.

Solution: Ensure that the CMNBAT90 JCL includes a BAT90OUT DD statement. See the description of utility CMNBAT90 in the ChangeMan ZMF Customization Guide.

`CMN4574A` `Unable to open BAT90LST file, subroutine analysis will continue by scanning BAT90LIB only.`

Explanation: No BAT90LST DD statement was found. The BAT90LST DD statement allocates the binder SYSPRINT listing for input to program CMNBAT90. If no binder listing is allocated, CMNBAT90 sets RC=4 and uses the load module scan method to analyze subroutine-to-load relationships.

Solution: The solution depends on the kind of module from the build that is being processed by CMNBAT90.

If the build output module is a load module created by the binder, add a BAT90LST DD statement to the CMNBAT90 job step.
If the build output module is not a true load module created by the binder (such as DBRM, CICS MAP, IMS MFS format), ignore this message. See the description of utility CMNBAT90 in the ChangeMan ZMF Customization Guide.

`CMN4575A` `Unable to open BAT90LIB file, subroutine analysis is incomplete, this may affect audit results.`

Explanation: No BAT90LIB DD statement was found for program CMNBAT90. The BAT90LIB DD statement allocates a library concatenation that matches the SYSLIB concatenation in the binder step. CMNBAT90 searches this library concatenation to determine the library where each statically linked subprogram originated.

Solution: The solution depends on the kind of build output module that is being processed by CMNBAT90.

If the build output module is a load module that might contain statically linked subprograms, add a BAT90LIB DD statement to the CMNBAT90 job step.
If the build output module is not a load module, or if it is a load module that cannot contain statically linked subprograms, such as BMS MAP load or IMS MFS load, either ignore this message or use CMNBAT90 execution parameter PARM='BINDLIST=XLMOD' to suppress load module analysis. See the description of utility CMNBAT90 in the ChangeMan ZMF Customization Guide.

`CMN4576A` `Unable to obtain storage for IDR table, subroutine analysis is incomplete, this may affect audit results.`

Explanation: Internal IDR table storage allocation failed, which results in missing subroutine information. Audit relies on this information for accurate results. CMNBAT90 continues but ends with at least RC=4.

Solution: Increasing the REGION size for the CMNBAT90 job step may correct this problem.

`CMN4577A` `Unable to obtain storage for SYSLIB table, subroutine analysis is incomplete, this may affect audit results.`

Explanation: Internal SYSLIB table storage allocation failed, which results in missing subroutine information. Audit relies on this information for accurate results. CMNBAT90 continues but ends with at least RC=4.

Solution: Increasing the REGION size for the CMNBAT90 job step may correct this problem.

`CMN4578A` `Unable to obtain storage for IDR buffer, subroutine analysis is incomplete, this may affect audit results.`

Explanation: Internal binder buffer for IDR dialog storage allocation failed, which results in missing subroutine information. Audit relies on this information for accurate results. CMNBAT90 continues but ends with at least RC=4.

Solution: Increasing the REGION size for the CMNBAT90 job step may correct this problem.

`CMN4579A` `Unable to obtain storage for INCLIB table, subroutine analysis is incomplete, this may affect audit results.`

Explanation: Internal INCLIB table storage allocation failed, which results in missing subroutine information. Audit relies on this information for accurate results. CMNBAT90 continues but ends with at least RC=4.

Solution: Increasing the REGION size for the CMNBAT90 job step may correct this problem.

`CMN4580A` `Problem reading the Binder Listing (BAT90LST), subroutine analysis will continue by scanning BAT90LIB only.`

Explanation: There is a logical error trying to read the dataset allocated to DDname BAT90LST, which is the the binder listing. CMNBAT90 sets RC=4 and changes to the load module scan method for analyzing subroutine-to-load relationships.

Solution: Verify that the binder step writes the SYSPRINT binder listing to a data set with RECFM=FBA, LRECL=121. Verify that this is the same data set that is input to CMNBAT90 at DDname BAT90LST. See the description of utility CMNBAT90 in the ChangeMan ZMF Customization Guide.

`CMN4581A` `Binder processing options MAP and LIST are missing, subroutine analysis will continue by scanning BAT90LIB only.`

Explanation: Binder options MAP and LIST must be in effect for CMNBAT90 to extract subroutine-to-load relationship information from the binder listing. CMNBAT90 sets RC=4 and changes to the load module scan method for analyzing subroutine-to-load relationships.

Solution: Add options MAP and LIST to binder steps in ChangeMan ZMF build skeletons. See the description of utility CMNBAT90 in the ChangeMan ZMF Customization Guide.

`CMN4582A` `{``name``} is an unsupported binder version, subroutine analysis will continue by scanning BAT90LIB only.`

Explanation: The version of the program binder that was executed is not supported by the current level of CMNBAT90. CMNBAT90 sets RC=4 and changes to the load module scan method of analyzing subroutine-to-load relationships.

Solution: Contact Micro Focus Customer Care.

`CMN4583A` `Unable to find stored member name in binder listing, subroutine analysis will continue by scanning BAT90LIB only.`

Explanation: CMNBAT90 could not locate the load module or program object name in the binder listing. CMNBAT90 sets RC=4 and changes to the load module scan method for analyzing subroutine-to-load relationships.

Solution: Contact Micro Focus Customer Care.

CMN4600 Notification

`CMN4600I` `Change Man package {``package id``} awaits your approval.`

Explanation: Displays when there is a change package awaiting a user’s approval.

`CMN4610I` `Package Information:`

Explanation: Displays change package information, such as installation date, level, type, short title, and approvers to date.

CMN4700 Online Forms

`CMN4700A` `NO GLOBAL OFM | No Global Online Forms are defined in the Package Master.`

Explanation: Displays when you try to access online forms in the package master or from panel CMNGOOFM (Option 1-Maintain on the Online Forms Options panel), but none exist. (This error message can also occur when moving test package master forms to production.)

Solution: To load the definition records into the package master:

Locate the FORMS member in the somnode.SAMPLES library. It contains the form definition records that are inserted into the package master.
Run the delivered JCL from the bottom of the $$$INDEX member from the somnode.SAMPLES library, using the SYSIN DD information from FORMS member. This imports the form definition records into the package master.

`CMN4710A` `INVALID FORM ID | FORM ID must be numeric between 0 - 999 or valid pattern.`

Explanation: Displays when you enter a form identifier that has an invalid pattern.

`CMN4720A` `FORM DOES NOT EXIST | The specified FORM ID is not globally defined.`

Explanation: Displays when you enter a form identifier that is not globally defined.

`CMN4730A` `INVALID STATUS | Form {``form``} has invalid status for this request.`

Explanation: The package status for the online form request is invalid.

Solution: Check the package status allowed for the online form you have selected.

CMN5000 Administration Messages

`CMN5000A` `INVALID RECORD FORMAT | RECFM must be “F,FB,FM,FA,FBM,FBA,V,VB,VM,VA,VBM,VBA, U”.`

Explanation: Displays when an administrator enters a record format type, during the configuration of global or local staging libraries, that ChangeMan ZMF does not recognize.

Solution: See panels CMNCGLT0 and CMNCLLT0 in the ChangeMan ZMF Administrator’s Guide.

`CMN5005A` `INVALID RECORD FORMAT | RECFM must be “F or FB” for this library type.`

Explanation: Displays when an administrator enters a record format type, during the configuration of global or local staging libraries, that does not match that library type. Record format must be fixed or fixed block for all library types except LOD.

Solution: See panels CMNCGLT0 and CMNCLLT0 in the ChangeMan ZMF Administrator’s Guide.

`CMN5006A` `INVALID RECORD FORMAT | RECFM must be “F, FB, V, or VB”.`

Explanation: Displays during JCL creation when the ISPFILE data set does not have a fixed record format.

`CMN5010A INVALID RECORD FORMAT | RECFM must be “U” for this library type.`

Explanation: Displays when an administrator enters a record format type, during the configuration of global or local staging libraries, that does not match that library type. Record format must be undefined for library type LOD.

Solution: See panels CMNCGLT0 and CMNCLLT0 in the ChangeMan ZMF Administrator’s Guide.

`CMN5015A` `INVALID RECORD FORMAT | RECFM “U” is disallowed for this library type.`

Explanation: Displays when an administrator enters a record format type, during the configuration of global or local staging libraries, that does not match that library type. Record format can be undefined for library type LOD or like-LOD only.

Solution: See panels CMNCGLT0 and CMNCLLT0 in the ChangeMan ZMF Administrator’s Guide.

`CMN5020A` `INVALID RECORD LENGTH | LRECL is inconsistent with BLKSIZE for this format.`

Explanation: Displays when the administrator, during the configuration of global or local staging libraries, enters a logical record length and block size that violates one of the following rules:

If the record format is fixed, the block size must equal the logical record length.
If the record format is fixed block, the block size must be a multiple of the logical record length.
If the record format is variable, there is one record per block, and the block size must be greater than the logical record length.
If the record format is variable block, the block size must be at least 4 bytes larger than the logical record length.
If the record format is undefined, the block size must be greater than the logical record length.

Solution: See panels CMNCGLT0 and CMNCLLT0 in the ChangeMan ZMF Administrator’s Guide.

`CMN5025A` `INVALID RECORD LENGTH | LRECL must be {``number``} for this library type.`

Explanation: Displays when an administrator, during the configuration of global or local staging libraries, enters a logical record length other than 80 for library type source (SRC) or copy (CPY).

Solution: See panels CMNCGLT0 and CMNCLLT0 in the ChangeMan ZMF Administrator’s Guide.

`CMN5040A` `INVALID SPACE TYPE | Space type must be in terms of TRK, CYL or BLK.`

Explanation: Displays when an administrator enters a space type, during the configuration of global or local staging libraries, that ChangeMan ZMF does not recognize.

Solution: See panels CMNCGLT0 and CMNCLLT0 in the ChangeMan ZMF Administrator’s Guide.

`CMN5045A` `INVALID BLOCK SIZE | Inconsistent BLKSIZE for this record format.`

Explanation: The block size must be consistent with the record format:

RECFM=fixed, BLKSIZE=LRECL
RECFM=variable, BLKSIZE=LRECL+4
RECFM=undefined, LRECL=0.

`CMN5050A` `INVALID DIR BLOCKS | DIRB must be at least 1 for this library type.`

Explanation: Displays when an administrator enters a directory block value less than 1 for any of the following reserved library types during the configuration of global or local staging libraries: SRC, CPY, LOD, JCL, LCT, CTC, DOC, PRC, and VLD.

Solution: See panels CMNCGLT0 and CMNCLLT0 in the ChangeMan ZMF Administrator’s Guide.

`CMN5051A` `Versions not allowed | Save staging versions not allowed for RECFM "U" library types.`

Explanation: Displays when an administrator enables staging versions during the configuration of global or application library types for a library type that is has undefined record format.

Solution: Staging versions may not be enabled for library types that are configured with undefined record format or are defined as like-other.

`CMN5055A` `MAX BYTES EXCEEDED | Maximum bytes that can be used have been exceeded.`

Explanation: Displays when an administrator enters more items than fits in 4000 bytes. Each list of items is allowed up to 4000 bytes. These lists are: compiling procedures, language names, library types, remote sites, change reason codes, component general information, approval lists.

Solution: See the ChangeMan ZMF Administrator’s Guide for more information.

`CMN5060A` `INVALID NAME | Name must differ from our logical or system name.`

Explanation: Displays when an administrator tries to define a remote site with the same logical or system name as the current site.

Solution: See the “Setting Up Remote Sites for Applications” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5065A` `NO PROCEDURES FOUND | No members found in the directory.`

Explanation: Displays when an administrator tries to define compiling procedures, and ChangeMan ZMF does not locate the SKELS library.

Solution: See the “Implementing the Skeleton Library” chapter in the ChangeMan ZMF Customization Guide and the “SKELS - File Tailoring” section in the ChangeMan ZMF Installation Guide.

`CMN5070A` `INVALID ENTITY NAME | Entity name is not a valid security system resource.`

Explanation: Displays when an administrator enters an approver entity name on the Complete Approval List panel (CMNCAPLD) or Abbreviated Approval List panel (CMNAAPLD) that was not previously defined to the security system.

Solution: See the ChangeMan ZMF Administrator’s Guide for the panels mentioned above.

`CMN5075A` `INVALID MODEL DSNAME | Invalid staging model data set name.`

Explanation: Displays when an administrator enters a data set name that does not follow the standard naming conventions.

Solution: See panel CMNGGP03 in the ChangeMan ZMF Administrator’s Guide.

`CMN5080A` `MAXIMUM EXCEEDED | Only 46 description lines are allowable.`

`CMN5082A` `MAXIMUM EXCEEDED | Only 46 instruction lines are allowable.`

`CMN5085A` `INCOMPLETE LIST | entity name is missing from the list.`

Explanation: Where xxxxxxxx is the name of the entity. Displays when attempts to define either the Planned or Unplanned approval list are unsuccessful due to exit

`CMNEX005` `requiring a specific entity be present on the approval list.`

Solution: See the “User Exits” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5090A` `INVALID BASELINE | No library types specified to be installed in production.`

Explanation: Displays when an administrator configures baseline libraries for a project without specifying any of them to be installed in production. For each baseline library type specified to be installed in production, the administrator must define the actual production library names during the Configure Production Libraries function. If no baseline libraries are specified to be installed in production, the administrator is not allowed to configure production for the project.

Solution: See panels CMNCBAS1 and CMNCPRDL in the ChangeMan ZMF Administrator’s Guide.

`CMN5100A` `INVALID PROCEDURE NAME | Procedure must have the language as part of the name.`

Explanation: Displays when an administrator defines a compiling procedure name in an invalid format. In a valid format, the middle three characters reflect the language name associated with the procedure.

Solution: See panel CMNPRCNM in the ChangeMan ZMF Administrator’s Guide.

`CMN5105A` `INVALID PROCEDURE NAME | Undefined procedure - contact Global Admin.`

Explanation: Displays when an application administrator tries to define a compiling procedure name for a project that has not been set up in the global administrative functions.

Solution: See panels CMNPRCNM and CMNCLPRC in the ChangeMan ZMF Administrator’s Guide.

`CMN5110A` `INVALID STORAGE MEANS | Storage means must be PDS or zFS for library type {``library type``}.`

Explanation: Displays when an administrator tries to configure a baseline library with a storage means that is inappropriate for the library type.

Solution: Change the storage means for the baseline to match the library type of the library. For example, if the library type is like-load, then the storage means must be P for MVS load libraries or Z for zFS directories. See panel CMNCBAS1 in the ChangeMan ZMF Administrator’s Guide.

`CMN5115A` `INVALID STORAGE MEANS | Undefined storage means. Contact Global Admin.`

Explanation: Displays when an administrator tries to configure a baseline library for a project with a storage means that was restricted during global parameter generation.

Solution: See panels CMNCBAS1 and CMNGGP02 in the ChangeMan ZMF Administrator’s Guide.

`CMN5116A` `INVALID STORAGE MEANS | Stacked reversed delta baseline must be RECFM=FB and LRECL=80.`

Explanation: The application administrator must change the file attributes of the stacked reverse delta baseline in the project parameters option 2, LIBRARY.

`CMN5117A` `INVALID STORAGE MEANS | Stacked reversed delta is invalid for library type {``library type``}.`

Explanation: Displays when stacked reverse delta is used on invalid library types. Libraries configured as load, like load, compressed listings, or DBRM, are not allowed to be organized as stacked reverse delta.

`CMN5118A` `INVALID STORAGE MEANS | Command valid for stacked reverse delta baseline only.`

Explanation: Displays when you try to issue the View Stack command from panel CMNBRWB0 or panel CMNBRWB1 and the baseline library is not defined as stacked reverse delta (SRD). The View Stack command is valid for SRD format only.

`CMN5120A` `INVALID STORAGE MEANS | Subsystem LAM must be generated for Librarian CPY.`

Explanation: Displays when an administrator tries to configure a CPY Baseline library for a project with a storage means of LIB or LIBARCHIE, but LAM was not specified during global parameter generation.

Solution: See panels CMNCBAS1 and CMNGGP02 in the ChangeMan ZMF Administrator’s Guide.

`CMN5125A` `INVALID LIKE VALUE | Like value must be {``recfm``} for this library type.`

Explanation: Displays when an administrator enters a record format type, during the configuration of global or local staging libraries, that does not match the library type. The record format must be undefined for library type like-LOD.

Solution: See panels CMNCGLT0 and CMNCLLT0 in the ChangeMan ZMF Administrator’s Guide.

`CMN5128A` `ENTER REQUIRED FIELD | Enter required Part 2 “{``library type``}” field.`

Explanation: Displays when an administrator enters a library type during part 1 (enter descriptions) of global or application staging libraries configuration without selecting the library type and entering specifications on part 2 of this function.

Solution: See panels CMNCGLT0 and CMNCLLT0 in the ChangeMan ZMF Administrator’s Guide.

`CMN5130A` `RESTRICTED VALUE | This value has been restricted by your Global ADMIN.`

Explanation: Displays when an administrator tries to allow an option that the global administrator has restricted, such as a more liberal audit return code or demotion rule.

`CMN5133A` `INVALID TARGET TYPE | Source type {``type``} has invalid target type {``TYPE``}.`

Explanation: Displays when the target load library type, xxx, in column “TARGET LOD TYPE,” panel CMNCGLT0 or CMNCLLT0, is not defined; or the target load library type is not of like-LOD characteristic.

`CMN5134A` `STORAGE AREA EXHAUSTED | Insufficient area for target load type.`

Explanation: Displays when the number of load library types in an installation exceeds 1365, the maximum number that can normally be stored in memory.

Solution: If there is a need for an unusually large number of load library types, the administrator should call Micro Focus Customer Care and ask to modify module CMNADMIN at label TLOD0000.

`CMN5135A GETMAIN/FREEMAIN ERROR | GETMAIN/FREEMAIN error for target load type.`

Explanation: Displays when module CMNADMIN issues macro GETMAIN or FREEMAIN and fails.

Solution: The administrator should increase the size of the JCL region parameter.

`CMN5140A NAME ALREADY USED | Promotion name was previously defined.`

Explanation: Displays when an administrator tries to configure a promotion level for a project with a nickname that has already been used.

Solution: See panel CMNCPRO1 in the ChangeMan ZMF Administrator’s Guide. The administrator should configure the promotion level with a nickname that has not been used before.

`CMN5150A INVALID SITE NAME | For this environment, site node name cannot be used.`

Explanation: Displays in an ALL environment when you attempt to define a global site with a SITE NAME that is the same as the SITE NODE NAME in global administration parameters. (This is not an error in a DP environment.)

Solution: Choose a SITE NAME that is not the same as the SITE NODE NAME in global administration parameters.

`CMN5165A INVALID LIBRARY TYPE | Undefined library type; check library type configuration.`

Solution: Displays when the target load library type for xxx is not defined for this application. You should ask the application administrator to verify the existence of the target load library type in panel CMNCLLT0.

`CMN5166A INVALID LIBRARY TYPE | No library type defined for {``type``}.`

`CMN5170A INVALID LANGUAGE NAME | Undefined language name; check language list.`

Explanation: Displays when an administrator tries to specify a language name that was not previously set up on the global language name list.

Solution: See panel CMNGGLNG in the ChangeMan ZMF Administrator’s Guide.

`CMN5173I INVALID PROCEDURE NAME | Undefined procedure name; member must exist in ISPSLIB.`

Explanation: Displays when you specify an invalid procedure name during the package stage. Examples of invalid procedures are: assemble; compile.

Solution: You should check the procedure list to determine the valid procedure names.

`CMN5175I APPLICATION LOCKED | Application parameters globally locked for update.`

Solution: Displays when an application administrator performs any kind of project definitions for a project locked for update by the global administrator.

`CMN5176I` `APPLICATION IN USE | Application parameters currently being updated by {``userid``}.`

Explanation: Displays when an administrator chooses an Application Administration Option at the same time that another administrator is updating the same application. Administration panels for an application are available in browse mode when another administrator is updating the application.

Solution: If this message displays when no other administrator is updating the same application, use the Lock function in Global Administration to reset the lock.

`CMN5177I` `APPLICATION IN USE | {``appl``} application parameters currently being updated by {``userid``}.`

Explanation: Displays when an administrator chooses an Application Administration Option at the same time that another administrator is updating the same application. Administration panels for an application are available in browse mode when another administrator is updating the application.

Explanation: If this message displays when no other administrator is updating the same application, use the Lock function in Global Administration to reset the lock.

`CMN5180A` `APPLICATION NOT FOUND | Project to delete does not exist in the Package Master.`

Explanation: Displays when an administrator tries to delete a project that does not exist.

Solution: See panel CMNDPROJ in the ChangeMan ZMF Administrator’s Guide.

`CMN5181A` `ALREADY DEFINED | {``application name``} already defined, cannot overlay parms.`

Explanation: Displays when you try to copy forward parameters from an existing application to one that already has defined parameters.

Solution: You should create a new application and should not define any parameters before copying forward parameters from an existing application.

`CMN5185I` `APPLICATION DELETED | Application deleted.`

Explanation: Displays when an administrator opts to delete a project, and ChangeMan ZMF has successfully performed the task.

Solution: See panel CMNDPROJ in the ChangeMan ZMF Administrator’s Guide.

`CMN5190A` `DELETE CANCELED | Request to delete an application has been canceled.`

Explanation: Displays when an administrator opts to cancel and exit from the panel used to delete a project.

Solution: See panel CMNDPROJ in the ChangeMan ZMF Administrator’s Guide.

`CMN5195A` `DELETE ERROR | There are more packages under this application.`

Explanation: Displays when an administrator attempts to delete a project that still has change packages. All packages must be deleted or aged before a project can be deleted.

Solution: See panel CMNDPROJ in the ChangeMan ZMF Administrator’s Guide.

`CMN5196A` `DELETE ERROR | Application still joined to a Release.`

`CMN5200A` `NO APPLICATION FOUND | No applications found in the Package Master.`

Explanation: Displays when an administrator opts to view a list of projects by leaving a blank in the Project Name field on panel CMNLAMEN, but there are no projects to list.

Solution: See the ChangeMan ZMF Administrator’s Guide for the panel mentioned.

`CMN5205A` `INVALID APPLICATION | Invalid application name; examples: XXXX,XXX, XXX1.`

Explanation: Displays when an administrator tries to define, review or update a project using a mnemonic that does not conform to the standard naming conventions.

Solution: See panel CMNLAMEN in the ChangeMan ZMF Administrator’s Guide.

`CMN5210I` `PARAMETERS GENERATED | Global parameters have been generated.`

Explanation: Displays when an administrator successfully completes the series of panels required to generate the global parameters.

Solution: See the chapter on “Setting up Global Administration” in the ChangeMan ZMF Administrator’s Guide.

`CMN5215I` `PARAMETERS GENERATED | {``mnemonic``} application parameters have been generated.`

Explanation: Displays when an administrator successfully completes the series of panels required to generate the local parameters for a specified project.

Solution: See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5220I` `LIBRARY TYPES GEN’D | Global staging library types have been generated.`

Explanation: Displays when an administrator successfully completes the panel required to specify global staging library allocation information.

Solution: See the “Setting Up Global Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5225I` `LIBRARY TYPES GEN’D | {``mnemonic``} application library types have been generated.`

Explanation: Displays when an administrator successfully completes the panel required to specify local staging library allocation information.

Solution: See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5226I` `LIBRARY TYPES UPDATED | Application library types have been updated.`

`CMN5230I` `LANGUAGE NAMES GEN’D | Global language names have been generated.`

Explanation: Displays when an administrator successfully completes the panel required to specify global language names.

Solution: See the “Setting Up Global Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5235I` `LANGUAGE NAMES GEN’D | {``mnemonic``} application language names have been generated.`

Explanation: Displays when an administrator successfully completes the panel required to specify local language names.

Solution: See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5240I` `PROCEDURE LIST GEN’D | Global compiling procedure list has been generated.`

Explanation: Displays when the administrator successfully completes the panel required to specify global compiling procedure names.

Solution: See the “Setting Up Global Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5245I` `PROCEDURE LIST GEN’D | {``mnemonic``} application Compile procedure list has been generated.`

Explanation: Displays when the administrator successfully completes the panel required to specify local compiling procedure names.

Solution: See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5250I` `SITE GEN’D | Global site names have been generated.`

Explanation: Displays when an administrator successfully completes the panel required to specify global site information.

Solution: See the “Setting Up Global Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5255I` `SITE GEN’D | {``mnemonic``} application site names have been generated.`

Explanation: Displays when an administrator successfully completes the panel required to specify application site information.

Solution: See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5260I` `REASON CODES GEN’D | Reason code list has been generated.`

Explanation: Displays when an administrator successfully completes the panel required to specify unplanned change package reason code information.

Solution: See the “Setting Up Global Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5265I` `APPROVAL LIST DEFINED | {``mnemonic``} application complete approval list has been defined.`

Explanation: Displays when an administrator successfully completes the panel required to specify project approver information.

Solution: See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5270I` `APPROVAL LIST DEFINED | {``mnemonic``} application abbreviated approval list has been defined.`

Explanation: Displays when an administrator successfully completes the panel required to specify project approver information for unplanned change packages created outside normal business hours.

Solution: See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5273I` `UNDEFINED VEHICLE | Notification vehicle undefined - contact Global Admin.`

Explanation: The notification vehicle is defined in the global parameters option 1, GEN PARMS; PART 1 OF 5.

`CMN5275I` `LIBRARIES DEFINED | {``mnemonic``} application promotion libraries have been defined.`

Explanation: Displays when an administrator successfully completes the series of panels required to configure the levels of promotion for the specified project.

Solution: See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5280I` `LIBRARIES DEFINED | {``mnemonic``} application baseline libraries have been defined.`

Explanation: Displays when an administrator successfully completes the series of panels required to configure the levels of baseline for the specified project.

Solution: See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5281I` `LIBRARIES UPDATED | Application baseline libraries have been updated.`

`CMN5285I` `LIBRARIES DEFINED | {``mnemonic``} application production libraries have been defined.`

Explanation: Displays when an administrator successfully completes the panel required to configure the production libraries for the specified project.

Solution: See the “Setting Up Application Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5286I` `LIBRARIES UPDATED | Application production libraries have been updated.`

`CMN5287A` `UNDEFINED LIBRARY TYPE | Library type {``type``} not defined for application {``appl``}.`

Explanation: Define library type to the application before using it.

`CMN5290A` `INVALID LOGICAL NAME | Logical unit name must be same as this site's logical unit name.`

Explanation: Displays when an administrator tries to define the production remote site in a DEV-PROD environment without using the same logical or system name as the current development site.

Solution: See the “Setting Up Remote Sites for Applications” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5295A` `INVALID DELAY FILE | Delay file must be similar to our site delay file.`

Explanation: Displays when an administrator tries to define the production remote site in a DEV-PROD environment without using the same delay file name as the current development site.

Solution: See the “Setting Up Remote Sites for Applications” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5296I` `INVALID MODEL DATA SET | PRD staging model DSN must be similar to DEV staging model DSN.`

Explanation: Displays when an administrator tries to specify a production model data set name different from a development model data set name for a DEV-PROD remote site.

`CMN5300A` `INVALID TRANSMISSION | Transmission type must be IEBCOPY.`

Explanation: Displays when an administrator tries to define the production remote site in a DEV-PROD environment without using IEBCOPY as the transmission.

Solution: See the “Setting Up Remote Sites for Applications” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5301A` `INVALID TIME DIFFERENCE | Time difference format: +HHMM or -HHMM, hours 00-23, minutes 00-59`

Explanation: You entered an invalid time difference. Enter a time difference in the format defined in the long error message.

`CMN5310I` `LCMD DISALLOWED | Allocate and Verify not available for Panvalet and Librarian.`

Explanation: Displays when an administrator tries to use the allocate option during the configuration of a baseline library that is maintained through CA-Librarian or CA-Panvalet.

Solution: See the “Configuring Baseline Libraries” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5320A` `LEVEL TOO HIGH | Baseline level too high for specified storage means.`

Storage means = LIBRARIAN, Lib Archie, level=2-255.
Storage means = PANVALET, PDS, Delta Deck, level=2-10.

Solution: See the “Configuring Baseline Libraries” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5340I` `PROMOTION LEVEL ERROR | Promotion levels and/or libraries not specified.`

Explanation: Displays when an application administrator fails to specify at least one promotion level in a site or at least one library type in a promotion level.

Solution: The administrator must make these minimum entries to exit the Promotion Levels panel and the Promotion Site List panel.

`CMN5345I` `Promotion nickname cannot be the same as a sitename.`

Explanation: Displays when you have entered a site name and it matches the promotion name. The two names differ.

`CMN5350I` `NO PROD SITE GEN’D | Application parameters can only be sent to PROD sites.`

Explanation: Displays when an application administrator tries to transmit project parameters to a DEV-PROD site.

`CMN5355I` `NO OPTIONS TO DISPLAY | There are no selectable options to display at this site.`

Explanation: Displays when you select option O, but have not installed any of the ChangeMan ZMF selectable options.

`CMN5360I` `INVALID PROCESS OPTION | {``option``} selectable option must be licensed to use this option.`

`CMN5365I` `INVALID PROCESS OPTION | {``option``} selectable option is not recognized by Change Man.`

`CMN5370I` `PROCESS ERROR | {``Production|Promotion``} site information must be deleted first.`

Explanation: You tried to delete a site in application administration that is used in a promotion library definition or a production library definition for the application.

Solution: In application administration, delete promotion library definitions and/or production library definitions that use the site, then delete the site. Caution: Demote packages promoted to a site before you delete the promotion library definitions for the site.

`CMN5372I` `zFS RESTRICTED | zFS not enabled in Global Administration.`

`CMN5373I` `USER VARS RESTRICTED | Component user variables not enabled in Global Administration.`

CMN5400 CMNWRITE

For a detailed description of utility program CMNWRITE, see the ChangeMan ZMF Customization Guide.

`CMN5400I` `Time of day at end of job: {``time``}. Condition Code on exit: {``return code``}.`

Explanation: Some ChangeMan ZMF programs display this message just before they terminate.

`CMN5410I` `Unable to open SYSUT3 for non-expanded copy libraries.`

Explanation: Displays when the DDNAME SYSUT3 is not specified in the CMNWRITE skeleton, or it is not pointing to the correct volume.

`CMN5420I` `Member {``member name``} expanded into SYSUT3.`

Explanation: Displays in SYSPRINT for CMNWRITE when it does not expand a copybook inline into source code and writes the member to SYSUT3 instead. The non-expanded status of the component is also indicated by an "N" preceding the level number in the SYSRINT report.

Solution: No action required.

`CMN5430I` `Member {``member name``} not expanded into SYSUT3.`

Explanation: Displays when ChangeMan ZMF cannot find or cannot access a nonexpanded member.

`CMN5440A` `Filename SYSUT3 not defined.`

Explanation: Displays when the filename has not been defined for SYSUT3.

`CMN5445A` `Detected at least 99 levels of nested copy.`

Explanation: Displays when CMNWRITE reaches its limit of 99 levels of nested copy. This usually indicates a recursive nested copy.

`CMN5450I` `Empty source member cannot be staged.`

Explanation: Displays when you stage an empty source member, causing a SOC4. The system returns an error code of 8, and the other steps are stopped.

Solution: You should stage a member that contains actual source code.

`CMN5455A` `Too many synonyms specified.`

CMN5500 Implementation Calendar

`CMN5500I` `CALENDAR UPDATED | Implementation calendar updated.`

Explanation: Displays when an administrator successfully completes the panel required to initialize or update the Planned Installation Calendar.

Solution: See the “Global Administrative Functions” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5510A` `INVALID VALUE | This value is not a positive number.`

Explanation: Displays when an administrator tries to initialize or update the Planned Installation Calendar with a non positive numeric value.

Solution: See the “Setting Up Global Administration” chapter in the ChangeMan ZMF Administrator’s Guide.

`CMN5520I` `CALENDAR NOT FOUND | Calendar for site {``site``} not defined.`

Explanation: Contact ChangeMan ZMF Global Administrator.

`CMN5530A` `INVALID DATE FIELD | Date is beyond max number of days in calendar.`

Explanation: Correct date field.

`CMN5540A` `INVALID NUMBER OF DAYS | Number of days is beyond max number of days in calendar.`

Explanation: You have exceeded the max number of (1820) days allowed in calendar.

Solution: Correct and resubmit.

`CMN5550A` `CALENDAR ERROR | Calendar for {``task``} already defined.`

`CMN5560I` `INSTALL DATE ERROR | Install date is beyond number of days in calendar.`

CMN5600 Component Information

`CMN5600I` `NO INFORMATION FOUND | No general information found in the Package Master.`

Explanation: Displays when an administrator tries to view general information driven by the contents of the package master, but there is none to view.

Solution: See the “Defining Optional Component Descriptions, Procedure or Security” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5605I` `NO INFORMATION FOUND | No designated procedure information in the Package Master.`

Explanation: Displays when an administrator tries to view designated procedure information driven by the contents of the package master, but there is none to view.

Solution: See the “Defining Optional Component Descriptions, Procedure or Security” section in ChangeMan ZMF Administrator’s Guide.

`CMN5610I` `NO INFORMATION FOUND | No security information found in the Package Master.`

Explanation: Displays when an administrator tries to view component level security information driven by the contents of the package master, but there is none to view.

Solution: See the “Defining Optional Component Descriptions, Procedure or Security” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5611I` `NO INFORMATION FOUND | No component application information found in the package master.`

`CMN5615I` `INVALID PATTERN | Too vague, asterisk cannot be first character.`

Explanation: Displays when an administrator tries to view component information based on a pattern that is not specific enough.

Solution: See the “Defining Optional Component Descriptions, Procedure or Security” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5630I` `PROCEDURE PROCESSED | Designated procedure requests processed.`

Explanation: Displays when an administrator successfully updates a component’s designated procedure.

Solution: See the “Defining Optional Component Descriptions, Procedure or Security” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5635A` `INVALID LANGUAGE | Language not valid for this procedure.`

Explanation: Displays when the language entered has not been defined in Global Administration for the procedure selected.

Solution: Enter a valid language for the selected procedure.

`CMN5636A` `INVALID PROCEDURE | Procedure not valid for this language.`

Explanation: Displays when the procedure entered has not been defined in Global Administration for the language selected.

Solution: Enter a valid procedure for the selected language.

`CMN5640I` `INFORMATION CHANGED | {``component type``}’s general information record has been changed.`

Explanation: Displays when an administrator successfully updates a component’s general information.

Solution: See the “Defining Optional Component Descriptions, Procedure or Security” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5645I` `INFORMATION DELETED | {``component type``}’s general information record has been deleted.`

Explanation: Displays when an administrator successfully deletes a component’s general information.

Solution: See the “Defining Optional Component Descriptions, Procedure or Security” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5650I` `INFORMATION CHANGED | {``component type``}’s security information record has been changed.`

Explanation: Displays when an administrator successfully updates a component’s security information.

Solution: See the “Defining Optional Component Descriptions, Procedure or Security” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5655I` `INFORMATION DELETED | {``component type``}’s security information record has been deleted.`

Explanation: Displays when an administrator successfully deletes a component’s security information.

Solution: See the “Defining Optional Component Descriptions, Procedure or Security” section in the ChangeMan ZMF Administrator’s Guide.

`CMN5656I` `INFORMATION CHANGED | {``application``}'s application information record has been changed.`

`CMN5657I` `INFORMATION DELETED | {``application``}'s application information record has been deleted.`

`CMN5660A` `INVALID LIBRARY TYPE | Specified library type not SRC or like-SRC.`

Explanation: Displays when an administrator requests a SRC-like library type selection list, but no SRC or SRC-like library types were generated.

`CMN5665A` `INVALID LIBRARY TYPE | {``Library type``} library type not like-LOD, NCL or OBJ.`

Explanation: Displays when an administrator requests a LOD-like library type selection list, but no LOD or LOD-like library types were generated.

`CMN5666A` `INVALID LIBRARY TYPE | {``library type``} library type must be like-LOD.`

`CMN5670A` `COMPONENT NOT FOUND | Specified component does not exist in the Package Master.`

Explanation: Displays when an administrator requests the deletion of a component’s compiling procedure, but that component is not in the package master.

`CMN5671I` `USER WARNING | Component general information crosses application boundaries.`

Explanation: Warns you that the general information defined locally for this application applies globally to all other applications.

`CMN5672I` `USER WARNING | Component security information crosses application boundaries.`

Explanation: Warns you that the security information defined locally for this application applies globally to all other applications.

`CMN5673I` `USER WARNING | Component designated procedure crosses application boundaries.`

Explanation: Warns you that the designated procedure defined locally for this application applies globally to all other applications.

CMN5700 Report

`CMN5700I` `UNDEFINED REPORTS | Reports are undefined or restricted - contact Administrator.`

`CMN5710I` `GLOBAL REPORTS DEFINED | Global report definitions have been generated.`

`CMN5720I` `APPL. REPORTS DEFINED | {``appl``} application report definitions have been generated.`

`CMN5730A` `UNDEFINED REPORT ID | Report {``report``} is undefined or restricted - contact Global Admin.`

`CMN5740I` `INVALID REPORT ID | Report ID must be a 3-digit number from 000 to 999.`

`CMN5750I` `Invalid report type | Report type required, G-global, A-application or U-user.`

Explanation: This message is issued from panel CMNREPT1 when defining global reports and an invalid or blank entry is put into the report type field. The only valid entries are G, A, or U.

`CMN5752I` `INVALID REPORT TYPE | Report type restricted by global admin.`

`CMN5755I` `Invalid report type | Report type required, A-application or U-user.`

Explanation: This message is issued from panel CMNREPT2 when defining application reports and an invalid value is entered in the REPORT TYPE field. The only valid entries are A or U.

`CMN5760I` `DESCRIPTION REQUIRED | Report description is a required field.`

`CMN5770I` `Invalid number | Package number can not be mask and is a 1 to 6-digit number.`

Explanation: This message is issued from panel CMNREPT6 when submitting reports and an invalid package number is entered.

CMN6000 Skeleton

`CMN6000I` `RELEASE ID NOT FOUND | No information found for release ID {``release id``} in the Package Master.`

Explanation: Displays when you try to update a release ID that does not exist.

`CMN6010I` `{``release``} ID ALREADY EXISTS | Release ID already exists in the Package Master.`

Explanation: Displays when you try to rename a release ID to an existing release ID.

`CMN6020I` `RELEASE ID RENAMED | Release ID {``release id``} renamed to release ID {``release id``}.`

Explanation: Informs you that the release ID has been successfully renamed.

`CMN6030I` `RELEASE ID DELETED | Release ID {``release id``} deleted from the Package Master.`

Explanation: Informs you that the release ID has been successfully deleted.

`CMN6040I` `DELETE CANCELED | Request to delete release ID {``release id``} has been canceled.`

Explanation: Informs you that the release ID has been successfully canceled.

`CMN6050I` `NO ENTRIES FOUND | No release ID entries found to list.`

Explanation: Displays when you try to list a release ID selection list, but no release IDs exist in the package master.

`CMN6060I` `RELEASE ID NOT FOUND | Release ID {``release id``} to copy was not in the Package Master.`

Explanation: Displays when you try to copy release ID information into another release ID, but the ID does not exist in the package master.

`CMN6070I` `{``variable``} ID CREATED | Release ID 3-Dimensional skeleton variables created.`

Explanation: Informs you that the 3-Dimensional skeleton variable for a release ID has been successfully created.

`CMN6080I` `{``variable``} ID SAVED | Release ID 3-Dimensional skeleton variables saved.`

Explanation: Informs you that the 3-Dimensional skeleton variable for a release ID has been successfully updated.

`CMN6090I` `MAX VARIABLES EXCEEDED | Release ID 3-Dimensional skeleton variables saved with truncation.`

Explanation: Informs you that the 3-Dimensional skeleton variable for a release ID has been updated; however, you exceeded the limit of 53 variables.

`CMN6092I` `UNDEFINED RELEASE ID | Undefined 3D Skels release {``rel``}; contact Local Admin.`

`CMN6094A` `UNDEFINED RELEASE ID | Undefined 3D Skels variable {``rel``}; contact Local Admin.`

`CMN6100I` `INVALID PARAMETER | Required release ID parameter is invalid or missing.`

Explanation: Informs you that the command entered (locate, select) requires a release ID.

`CMN6110I` `INVALID PARAMETER | Required new release ID parameter is invalid or missing.`

Explanation: Informs you that either the entered rename command is missing a new release ID (rename R123), or the ID entered is invalid.

Solution: A release ID must follow the rules for a project name.

`CMN6111I` `INVALID PARAMETER | Required application mnemonic parameter is invalid or missing.`

Explanation: Displays when the rename command does not have a new release ID (rename R123), or you enter an invalid ID.

Solution: A release ID must follow the rules for a project name.

`CMN6120I` `INFORMATION SAVED | Release ID changes and information has been saved.`

Explanation: Informs you that change information has been saved for a release ID.

CMN6200 CMNBASLN

`CMN6200I` `JOB SUBMITTED | Job to generate Baseline Analyzer report submitted.`

`CMN6210I` `MISSING SYSIN | APPL= sysin card missing.`

`CMN6220I` `MISSING SYSIN | TYPE= sysin card missing.`

`CMN6250I` `JOB SUBMITTED | Job to perform housekeeping submitted.`

CMN6300 CMNLNKDT

`CMN6300I` `Unable to open LNKDTRPT file.`

`CMN6310I` `| No Change Man components to list within {``library``}.`

`CMN6320I` `JOB SUBMITTED | Job to generate Link Date report submitted.`

`CMN6330I` `JOB SUBMITTED | DB2 object dependency report submitted.`

`CMN6333I` `NO COMPONENTS | No relevant DB2 components found in package.`

...

CMN6500 Library Scan Utility

`CMN6501I` `INVALID ENTRY | TO displacement may not be less than FROM.`

Explanation: Displays when the DISPLACEMENT field of the CMNSCN01 panel has a larger TO record number than the FROM record number.

Solution: Correct the panel entry.

`CMN6502I` `UNDEFINED BASELINE | No Baseline library found for this library type.`

Explanation: Displays when no baseline libraries exist for the LIBRARY TYPE and/or the application you entered on the CMNSCN01 panel.

Solution: You should use the function QUERY PACKAGE to see if any baseline libraries exist for the specified application.

`CMN6503I` `NOT SUPPORTED | Scan of this baseline storage means is not supported.`

Explanation: Displays when a scan is requested of a CA-Panvalet or CA-Librarian library type.

`CMN6504I` `NO INFORMATION | No information found for this request.`

Explanation: ChangeMan ZMF cannot find a match for the conditions you specified. This is a standard message used in many ZMF functions.

Solution: If you think matches should have been returned, check the conditions you specified. Verify that you typed the correct case in case-sensitive fields or XML tags.

`CMN6505I` `TABLE OVERFLOW | Application table overflow max = 255..`

`CMN6506I` `TABLE OVERFLOW | Library type table overflow max = 255.`

`CMN6507I` `PNL$RESP ERROR | Data error in PNL$RESP. Contact ChangeMan Support.`

`CMN6550I` `NOT SUPPORTED | Scan of RECFM=U library is not supported.`

Explanation: Displays when you enter the library type LOD or Like LOD. Libraries of this type cannot be scanned.

`CMN6551I` `OUT OF ORDER | Enter components in alphabetical order.`

Explanation: Displays when you enter BEGIN and END components out of alphanumeric order. You should switch BEGIN and END components.

`CMN6552I` `INVALID STRING SIZE | String exceeds end of record using this starting point.`

Explanation: Displays when you enter a DATA STRING of length that exceeds the record length specified in the DISPLACEMENT field.

`CMN6570I` `PNL$RQST ERROR | Data error in PNL$RQST. Contact Change Man Support.`

Explanation: Displays when ChangeMan ZMF encounters an error in program CMNPANEL.

Solution: You should contact a ChangeMan ZMF support representative.

CMN6801 CMNCLNUP Utility

Following are the messages issued by program CMNCLNUP. For a functional description of utility program CMNCLNUP, see topic Clean Up Production Backup Libraries in the ChangeMan ZMF Administrator’s Guide.

`CMN6801I` `Unable to open SYSIN file.`

Explanation: Displays when a SYSIN DDname statement was coded in the JCL, and program CMNCLNUP attempted to open a data set specified by the SYSIN DDname or for the data set created for the input stream.

`CMN6802I` `Unable to open SYSUT1 file.`

Explanation: Displays when program CMNCLNUP attempted to open a data set specified by the SSUT1 DDname, and performed it unsuccessfully. SYSUT1 represents the input to program CMNCLNUP, and failure to perform a successful open causes program CMNCLNUP to terminate.

`CMN6803I` `Unable to open SYSUT2 file.`

Explanation: Displays when program CMNCLNUP attempted to open a data set specified by the SYSUT2 DDname, and performed it unsuccessfully. SYSUT2 represents the output to program CMNCLNUP, and failure to perform a successful open causes program CMNCLNUP to terminate.

`CMN6804I` `Unable to read directory for SYSUT1 file.`

Explanation: Displays when program CMNCLNUP attempted to read the directory for a PDS specified by the SYSUT1 DDNAME. CMNCLNUP was unable to read the directory information to build a list of all members residing in the SYSUT1 library. Before program CMNCLNUP performs any operation on a member in the SYSUT1 input library, CMNCLNUP verifies whether the member is in the member names list created from the directory. Failure to perform a successful read of the SYSUT1 directory prevents program CMNCLNUP from verifying the members, causing CMNCLNUP to terminate.

`CMN6805I` `Unable to read directory for SYSUT2 file.`

Explanation: Displays when program CMNCLNUP attempted to read the directory for a PDS specified with the SYSUT2 DDname. CMNCLNUP was unable to read the directory information to build a list of all members that reside in the SYSUT2 library. Before program CMNCLNUP performs any operation on a member in the SYSUT2 output library, CMNCLNUP verifies whether the member is in the member names list created from the directory. Failure to perform a successful read of the SYSUT2 directory prevents program CMNCLNUP from verifying the members, causing CMNCLNUP to terminate.

`CMN6806I` `Member not found in SYSUT1: {``member``}`

Explanation: Displays when program CMNCLNUP attempted to verify whether the specified member actually resides in the SYSUT1 library. Program CMNCLNUP checks the member names list generated from reading the SYSUT1 directory for the specified member name. If the member name is not found in the list, the member does not reside in the SYSUT1 library. Failure to find the specified member in the SYSUT1 library causes CMNCLNUP to skip to the next member specified from the input member list.

`CMN6807I` `Member not found in SYSUT2: {``member``}`

Explanation: Displays when program CMNCLNUP attempted to verify whether the specified member actually resides in the SYSUT2 library. Program CMNCLNUP checks the member names list generated from reading the SYSUT2 directory for the specified member name. If the member name is not found in the list, the member does not reside in the SYSUT2 library. Failure to find the specified member in the SYSUT2 library causes CMNCLNUP to skip to the next member specified from the input member list.

`CMN6808I` `Member not deleted in SYSUT2 {``member``}`

Explanation: Displays when program CMNCLNUP attempted to delete the specified member from the SYSUT2 output library, and was unable to successfully perform the member deletion. An I/O error might be the cause. Failure to delete the specified member in the SYSUT2 library causes CMNCLNUP to skip to the next member specified from the input member list.

Solution: Check the job or message log for possible error messages issued by the operating system for the SYSUT2 library.

`CMN6809I` `Member in SYSUT1 and SYSUT2 same. Member deleted from the SYSUT2 library: {``member``}`

Explanation: Displays when program CMNCLNUP deletes the specified member from the SYSUT2 output library. Program CMNCLNUP compares the directory entry for the samenamed member in both the SYSUT1 and SYSUT2 libraries. If the directory entries match, program CMNCLNUP deletes the member from the SYSUT2 library.

`CMN6810I` `Alias entry not deleted from SYSUT2 library: Alias= {``member``}`

Explanation: Alias is the alternate member name for the load module in the SYSUT2 output library that was assigned by the linkage editor. member is the member name for the load module in the SYSUT2 output library. Displays when program CMNCLNUP detects an unequal directory condition on a SYSUT2 library that contains load modules. This message is issued together with message CMN6812I explaining the unequal condition. Program CMNCLNUP compared the member directory entry in both the SYSUT1 and SYSUT2 libraries, and found that the entries did not match. Because the load module represented by name member was not deleted, program CMNCLNUP searched the directory of the SYSUT2 library for any alternate names alias associated with the load module. Message CMN6812I might be issued because an additional alias has been found for the load module member. This additional alias remains intact, thereby preserving the integrity of the load module.

`CMN6811I` `Alias entry was deleted from SYSUT2 library: Alias={``member``}`

Explanation: Alias is the alternate member name for the load module in the SYSUT2 output library that was assigned by the linkage editor. member is the member name for the load module in the SYSUT2 output library. Displays when program CMNCLNUP deletes the specified alias name from the SYSUT2 output library. This message is issued together with message CMN6809I to indicate that the member (associated with this alias) was deleted from the SYSUT2 load module library. Program CMNCLNUP compared the directory entry for member in both the SYSUT1 and SYSUT2 libraries, and found a match. Because the load module represented by name 'member' was deleted from the SYSUT2 library, program CMNCLNUP searched the directory for an alternate name alias associated with the load module. This message was displayed because an additional alias exists for the load module member, and that this alias was deleted from the SYSUT2 library.

`CMN6812I` `Directory not equal; member not deleted in SYSUT2: {``member``} {``reason``}`

Explanation: member is the member name in the SYSUT2 output library. reason is the explanation indicating the field in the directory entry that did not match. Displays when program CMNCLNUP detects an unequal directory condition on a SYSUT2 library. Program CMNCLNUP compared the directory entry for 'member' in both the SYSUT1 input library and the SYSUT2 output library, and found that the entries did not match. Because the member was not deleted, program CMNCLNUP determines the exact field in the directory entry that was different, and explains that difference in this message.

`CMN6813I` `An internal call was made to program CMNCLNUP and no ddnames were included in passed parameter list.`

Explanation: Displays when program CMNCLNUP determines that it is being called from another program, and detects no DDNAMEs. Program CMNCLNUP parses the input parameter list (passed from the calling program) to CMNCLNUP. During this process, a list of DDNAMEs to be used by program CMNCLNUP was not found, indicating that an invalid parameter list was created by the calling program. Failure to find this list prevents program CMNCLNUP from verifying the data set names, causing CMNCLNUP to terminate.

`CMN6814I` `No second ddname was included in ddname list, required ddnames are SYSUT1 and SYSUT2.`

Explanation: Displays when program CMNCLNUP determines that it is being called from another program, and detects only one DDNAME. Program CMNCLNUP parses the input parameter list (passed from the calling program) to CMNCLNUP. During this process a list of DDNAMEs to be used by program CMNCLNUP was found to contain only one DDNAME, indicating that an invalid parameter list was created by the calling program. Failure to find all required DDNAMEs prevents program CMNCLNUP from verifying the data set names, causing program CMNCLNUP to terminate.

`CMN6815I` `Required ddname SYSUT1 not included in ddname list.`

Explanation: Displays when program CMNCLNUP determines that it is being called from another program, and detects no SYSUT1 DDNAME. Program CMNCLNUP parses the input parameter list (passed from the calling program) to CMNCLNUP. During this process, a list of DDNAMEs to be used by program CMNCLNUP was found, but this list did not include the required DDNAME SYSUT1. This might be due to an invalid parameter list that was generated by the program calling CMNCLNUP. (SYSUT1 represents the input library used by program CMNCLNUP to compare directory entries.) Failure to find the required DDNAME SYSUT1 prevents program CMNCLNUP from comparing directory entries, causing CMNCLNUP to terminate.

`CMN6816I` `Required ddname SYSUT2 not included in ddname list.`

Explanation: Displays when program CMNCLNUP determines that it is being called from another program, and detects no SYSUT2 DDNAME. Program CMNCLNUP parses the input parameter list (passed from the calling program) to CMNCLNUP. During this process, a list of DDNAMEs to be used by program CMNCLNUP was found, but the list of DDNAMEs did not include the required DDNAME SYSUT2. This might be due to an invalid parameter list that was generated by the program calling CMNCLNUP. (SYSUT2 represents the output library from which members are deleted by the CMNCLNUP program.) Failure to find the required DDNAME SYSUT2 prevents program CMNCLNUP from deleting a member, causing CMNCLNUP to terminate.

`CMN6817I` `CMNCLNUP-execution parameters:`

Explanation: Displays when program CMNCLNUP determines that it is being run in batch. Program CMNCLNUP examines the run-time options being passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step, and displays the information. This either verifies the options requested, or assists you in correcting any syntax error errors that might be detected.

`CMN6818I` `Invalid syntax because no value is allowed to be specified with keyword, keyword = {``keywd``}`

Explanation: Displays when program CMNCLNUP determines that it is being run in batch, and detects a syntax error. Program CMNCLNUP examines the run-time options being passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step, and validates keyword values. In this instance a value was included (with a keyword) that requires no value. The valid keywords are:

ABEND Keyword must be specified with no value
ALLMEM Keyword must be specified with no value
COMMIT Keyword must be specified with no value
MEMBER Keyword must be specified with a value that is a list of member names, as in MEMBER=ABCD or MEMBER=(XXXX,YYYY,ZZZZ)

`CMN6819I` `Specified keyword is unrecognized because it is invalid, keyword = {``keywd``}`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a keyword error. Program CMNCLNUP examines the run-time options being passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step, and validates keyword values. In this instance a keyword was specified that could not be matched to any keywords in the keyword names table. The valid keywords are:

//CMNCLEAN EXEC PGM=CMNCLNUP,PARM=
ABEND
ALLMEM
COMMIT
[MEMBER=]

`CMN6820I specified keyword is ambiguous because it is too short or conflicts with another keyword, keyword = {``keywd``}`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a keyword error. Program CMNCLNUP examines the run-time options being passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step, and validates keyword values.

Solution: In this instance a specified keyword was abbreviated, and this abbreviation could not be resolved by the keyword names table because it was too short. To properly run, fully qualify the name of the intended keyword, and rerun the program.

`CMN6821I` `Invalid syntax because keyword requires that it be specified with a value, keyword = {``keywd``}`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a keyword error. Program CMNCLNUP examines the run-time options being passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step, and validates keyword values. In this instance, a value was not included with a keyword that required one. The valid keywords are as follows:

ABEND Specify with no value
ALLMEM Specify with no value
COMMIT Specify with no value
MEMBER Specify with a value that is a list of member name(s), as in MEMBER=XYZ00 or MEMBER=(AAAA,BBBB,CCCC)

`CMN6822I` `Invalid syntax: text`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a keyword error. Program CMNCLNUP examines the run-time options being passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step, and validates the syntax for all specified run-time options. Program CMNCLNUP was unable to resolve a syntax error. This message displays the value that was specified with invalid syntax.

`CMN6823I Error on attempted read of JFCB because no data set with SYSUT1 DDNAME has a DCB allocated.`

Explanation: Displays when program CMNCLNUP attempted to access the Job File Control Block for the SYSUT1 input library prior to an open, and was unable to successfully obtain a copy of the JFCB. In MVS™, data sets can be allocated with Job Control Language or Dynamic Allocation using SVC 99. This error might happen when program CMNCLNUP is called from another program as opposed to running in batch, and the SYSUT1 data set was not allocated by the calling program prior to CMNCLNUP being called. (SYSUT1 represents the input library used by program CMNCLNUP to compare directory entries.) Failure to access the JFCB for the SYSUT1 data set prevents program CMNCLNUP from opening the SYSUT1 data set, causing CMNCLNUP to terminate.

`CMN6824I` `Error on attempted read of JFCB because no data set with SYSUT2 DDNAME has a DCB allocated.`

Explanation: Displays when program CMNCLNUP attempted to access the Job File Control Block for the SYSUT2 input library before open, and was unable to successfully obtain a copy of the JFCB. In MVS, data sets can be allocated with Job Control Language or with Dynamic Allocation using SVC 99. This error might happen when program CMNCLNUP is called from another program as opposed to running in batch, and the SYSUT1 data set was not allocated by the calling program prior to CMNCLNUP being called. (SYSUT2 represents the output library from which members are deleted by the CMNCLNUP program.) Failure to access the JFCB for the SYSUT2 data set precludes an open for the SYSUT2 data set being performed by program CMNCLNUP, and causes CMNCLNUP to terminate.

`CMN6825I` `Required ddname SYSUT1 or SYSUT2 not specified.`

`CMN6826I` `Use of left bracket not a valid parm delimiter.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a keyword delimiter error. Program CMNCLNUP examines the run-time options being passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step, and validates the delimiter characters used to enclose a list of subvalues associated with a keyword. The left bracket '[' cannot be used as a separator character.

Solution: Use the left parenthesis '(' as the prefix delimiter to indicate the beginning of a list of subvalues.

`CMN6827I` `Use of right bracket not a valid parm delimiter.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a keyword delimiter error. Program CMNCLNUP examines the run-time options being passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step, and validates the delimiter characters used to enclose a list of subvalues associated with a keyword.

Solution: The right bracket ']' cannot be used as a separator character. Use the right parenthesis ')' as the suffix delimiter to indicate the end of a list of subvalues.

`CMN6828I` `Use of colon not a valid parm delimiter.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a keyword delimiter error. Program CMNCLNUP examines the run-time options being passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step. CMNCLNUP validates the delimiter characters used to separate keywords/ subvalues, or to interrupt for continuation onto another line a list of subvalues associated with a keyword.

Solution: Use the comma ',' as the separator character, and not the colon ‘:’.

`CMN6829I` `Use of semicolon not a valid parm delimiter.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a keyword delimiter error. Program CMNCLNUP examines the run-time options passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step.

Solution: CMNCLNUP validates the delimiter characters that are used to either separate keywords/subvalues, or interrupt for continuation onto another line a list of subvalues associated with a keyword. Use the comma ',' as the separator character.

`CMN6830I` `Use of ALLMEM keyword is mutually exclusive with the MEMBER keyword.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a keyword error. Program CMNCLNUP examines the run-time options being passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step. CMNCLNUP validates all specified keywords to ensure that the specified options are not in conflict. ALLMEM and MEMBER are in conflict because an ALLMEM requests to process all members from the SYSUT1 library, and MEMBER specifies a list of members to be processed.

Solution: To properly run program CMNCLNUP, specify only one of the two options, and rerun the program.

`CMN6831I` `Use of a ddname specification not supported with the JCL parm format.`

Explanation: Displays when program CMNCLNUP determines that it is being run as a batch program, and detects a keyword error. Program CMNCLNUP validates all the keywords passed from the 'PARM=' coded on the 'EXEC=' statement of the job step. Although the keyword 'DDNAMES' is recognized, the ability to override required DDNAMEs with a site chosen DDNAME is unsupported.

`CMN6832I` `Concatenation of data sets to input ddname SYSUT1 is not allowed.`

Explanation: Displays when program CMNCLNUP detects several input data sets that can be read in sequence from a single SYSUT1 DDNAME. While validating data sets, program CMNCLNUP verifies whether a data set is the first one associated with the SYSUT1 DDNAME. If the data set being verified is part of a DD statement without a DDNAME and that DD statement has been added to SYSUT1, a concatenation to the SYSUT1 input library has occurred. Program CMNCLNUP reads from only one library in SYSUT1, and deletes from only one library in SYSUT2. Failure to maintain a one-to-one relationship for the input library in SYSUT1 to the output library in SYSUT2 compromises the integrity of the deletion process, and causes CMNCLNUP to terminate.

`CMN6833I` `Concatenation of output ddname SYSUT2 results in only the first one being used.`

Explanation: Displays when program CMNCLNUP detects that several output data sets are associated with a single SYSUT2 DDNAME. While validating data sets, program CMNCLNUP verifies whether a data set is the first one associated with the SYSUT2 DDNAME. If the data set being verified is part of a DD statement without a DDNAME and the DD statement has been added to SYSUT2, a concatenation to the SYSUT2 output library has occurred. Output concatenations are accepted syntactically from MVS, but no concatenation is used beyond the first one. Program CMNCLNUP reads from only one library in SYSUT1, and deletes from only one library in SYSUT2. JCL syntax might be acceptable to MVS but be ambiguous (i.e. unacceptable) to CMNCLNUP processing, even if the one-to-one library relationship follows the MVS convention that only the first data set is used in output concatenations. For this reason, output concatenations cause CMNCLNUP to terminate.

`CMN6834I` `Required ddname SYSUT1 was not found in ddname search.`

Explanation: Displays when program CMNCLNUP detects that no data sets are associated with a DDNAME of SYSUT1. While validating data sets, program CMNCLNUP verified the DDNAME associated with every allocated data set, and did not detect the DDNAME SYSUT1. This DDNAME represents the input library used by program CMNCLNUP to compare directory entries. Failure to find the required DDNAME SYSUT1 prevents program CMNCLNUP from comparing directory entries, causing CMNCLNUP to terminate. This might be because program CMNCLNUP is running in batch, and the SYSUT1 DDNAME was not included in the JCL.

`CMN6835I` `Required DDNAME SYSUT2 was not found in DDNAME search.`

Explanation: Displays when program CMNCLNUP detects that no data sets are associated with a DDNAME of SYSUT2. While verifying the DDNAME associated with every allocated data set, program CMNCLNUP failed to find the DDNAME SYSUT2. (SYSUT2 represents the output library from which members are deleted by the CMNCLNUP program.) Failure to find the required DDNAME SYSUT2 means that the program CMNCLNUP cannot delete a member, causing CMNCLNUP to terminate. A possible cause for this error is that program CMNCLNUP is running in batch, and the SYSUT2 DDNAME was not included in the JCL.

`CMN6836I` `Required ddname SYSIN was not found in ddname search.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and CMNCLNUP detects no data sets are associated with a DDNAME of SYSIN. During the data-set validation process, program CMNCLNUP verifies the DDNAME associated with every allocated data set, and failed to find the DDNAME SYSIN. In addition, the 'ALLMEM' keyword or the 'MEMBER=' keyword was not specified in JCL to override SYSIN. This would remove SYSIN as a required DDNAME. Failure to find the required DDNAME SYSIN in the absence of overriding keyword parameters causes CMNCLNUP to terminate. A possible cause for this error is that the SYSIN DDNAME was not included in the job step running program CMNCLNUP.

`CMN6837I` `Use of the MEMBER keyword indicated and MEMBER keyword overrides SYSIN, but no members specified.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a null list for the MEMBER= keyword specified in the 'PARM=' parameter coded in the 'EXEC=' statement of the JCL. The 'MEMBER=' keyword overrides SYSIN, whether SYSIN contains control cards, is omitted, or is dummied. If the 'MEMBER=' keyword is included in JCL to override SYSIN, at least one member must be specified.

`CMN6838I` `Internal call format detected but required list of member names was not found.`

Explanation: Displays when program CMNCLNUP is called from another program, rather than running in batch. In such instances, program CMNCLNUP parses the input parameter list (passed from the calling program) to CMNCLNUP. During this process, the address pointer to a member names list contained all zeros, indicating that an invalid parameter list was created by the calling program. Failure to obtain an address pointing to a member list area prevents program CMNCLNUP from performing any member level operation, and causes CMNCLNUP to terminate.

`CMN6839I` `Internal call format detected but designated SYSUT1 input not available by dynamic allocation.`

Explanation: Displays when program CMNCLNUP determines that it is being called from another program, and detects that SYSUT1 is a JCL allocation. When opening a data set, program CMNCLNUP verifies the attributes of the target data set. In this instance, the SYSUT1 input data set was found to be allocated dynamically, rather than permanently. In MVS, data sets might be allocated through JCL or through Dynamic Allocation using SVC 99. This might happen because program CMNCLNUP is being called from another program, and that the other program is running in batch. A job step running a program that calls CMNCLNUP might contain a SYSUT1 DDNAME coded in the JCL that has been detected by the CMNCLNUP program. (SYSUT1 is a reserved DDNAME for exclusive use by program CMNCLNUP.) Any program that calls CMNCLNUP should not code a SYSUT1 DDNAME in the JCL.

Solution: Remove the SYSUT1 DDNAME from the job step, and rerun the step.

`CMN6840I` `Internal call format detected but designated SYSUT2 output not available by dynamic allocation.`

Explanation: Displays when program CMNCLNUP determines that it is being called from another program as opposed to running in batch. When opening a data set, program CMNCLNUP verifies the attributes of the data set being opened. In this instance the SYSUT2 output data set was allocated permanently, not dynamically. In MVS, data sets can be allocated through Job Control Language, or programmatically through Dynamic Allocation using SVC 99. A possible cause for this error is that program CMNCLNUP is being called from another program, and the other program is running in batch. A job step running a program calling CMNCLNUP might contain a SYSUT2 name coded in the JCL that has been detected by the CMNCLNUP program. (SYSUT2 is a reserved DDNAME for exclusive use by program CMNCLNUP.) Another program calling CMNCLNUP should not code a SYSUT2 DDNAME in the JCL.

Solution: Remove the SYSUT2 DDNAME from the job step, and rerun the step.

`CMN6841I` `No input; MEMBER was a null list or neither MEMBER nor ALLMEM keyword found in JCL, and SYSIN was DUMMY or NULLFILE.`

Explanation: Displays when program CMNCLNUP determines that it is being run as a batch job, and no input was found to direct member processing. When opening a data set, program CMNCLNUP verifies whether DUMMY was coded as the first parameter in the SYSIN DD statement, or if DSN=NULLFILE was coded in the SYSIN DD statement. A dummy or nullfile status indicates no input originates from SYSIN. Furthermore, program CMNCLNUP detected that neither the 'MEMBER=' keyword nor the 'ALLMEM' keyword was specified in the 'PARM=' parameter coded in the 'EXEC=' statement of the JCL, or if the 'MEMBER=' keyword was specified, it had no values. In the absence of any input specifying which members to process, program CMNCLNUP does not invoke a default process to delete a member.

Solution: To properly direct the member level processing of program CMNCLNUP, either specify a correct parameter keyword or use SYSIN when CMNCLNUP is run in batch.

`CMN6842I` `JCL format detected but DDNAME SYSUT1 indicates data set not allocated with permanent attribute.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a data set attribute conflict. When opening a data set, program CMNCLNUP verifies the attributes of that data set. In this instance, the SYSUT1 input data set was allocated dynamically, rather than permanently. This might be due to an allocation error.

Solution: Check the job or message log for possible error messages issued by the operating system for the SYSUT1 library.

`CMN6843I` `JCL format detected but DDNAME SYSUT2 indicates data set not allocated with permanent attribute.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a data set attribute conflict. When opening a data set, program CMNCLNUP verifies the attributes of that data set. In this instance, the SYSUT2 output data set was allocated dynamically, rather than permanently. This error might be due to an allocation error.

Solution: Check the job or message log for possible error messages issued by the operating system for the SYSUT2 library.

`CMN6844I Member list specified in PARM= of JCL and SYSIN not DUMMY; SYSIN is ignored, PARM= list overrides.`

Explanation: Displays when program CMNCLNUP determines that it is being run as a batch job, and CMNCLNUP detects the use of the 'MEMBER=' keyword and a SYSIN DD statement. Prior to opening SYSIN, program CMNCLNUP verifies whether the 'PARM=' parameter was coded in the 'EXEC=' statement of the JCL with the 'MEMBER=' keyword specified. Use of the 'MEMBER=' keyword to specify a member list means that CMNCLNUP ignores SYSIN because the 'MEMBER=' overrides any input from SYSIN.

`CMN6845I` `Option ALLMEM to process all members specified in PARM= of JCL; SYSIN is ignored, PARM= overrides.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and CMNCLNUP detects the use of the 'ALLMEM' keyword and a SYSIN DD statement. Prior to opening SYSIN, program CMNCLNUP verifies whether the 'PARM=' parameter was coded in the 'EXEC=' statement of the JCL with the 'ALLMEM' keyword specified. Use of the 'ALLMEM' keyword results in all members from the SYSUT1 library being processed. Specifying 'ALLMEM' causes SYSIN input to be ignored because the 'ALLMEM' keyword overrides SYSIN.

`CMN6846I` `SYSUT1 input library DSN={``dsn``}`

Explanation: This message is an informational message that displays the data set name assigned to the SYSUT1 DDNAME.

`CMN6847I` `SYSUT2 output library: DSN={``dsn``}`

Explanation: This message is an informational message that displays the data set name assigned to the SYSUT2 DDNAME.

`CMN6848I` `Null data set detected for the SYSUT1 input library, Correct DD statement to specify a real data set.`

Explanation: Displays when program CMNCLNUP determines that the SYSUT1 DD statement indicates all I/O operations will be bypassed. When opening a data set, program CMNCLNUP verifies whether DUMMY was coded as the first parameter in the SYSUT1 DD statement, or if DSN=NULLFILE was coded in the SYSUT1 DD statement. A dummy or nullfile status signifies that no input originates from SYSUT1. (SYSUT1 represents the required input library used by program CMNCLNUP to compare directory entries.)

Solution: To properly direct the member level processing of program CMNCLNUP, assign a real data set to the SYSUT1 DD statement.

`CMN6849I` `Null data set detected for the SYSUT2 output library, Correct DD statement to specify real data set.`

Explanation: Displays when program CMNCLNUP determines that the SYSUT2 DD statement indicates all I/O operations will be bypassed. While opening a data set, program CMNCLNUP verifies whether DUMMY was coded as the first parameter in the SYSUT2 DD statement, or if DSN=NULLFILE was coded in the SYSUT2 DD statement. A dummy or nullfile status signifies that any write request to the SYSUT2 output library is ignored. (SYSUT2 represents the required output library from which members are deleted by the CMNCLNUP program.)

Solution: To properly direct the member level processing of program CMNCLNUP, assign a real data set to the SYSUT2 DD statement.

`CMN6850I` `Unable to open SYSPRINT file, possible SYSPRINT dd missing. All messages directed to job log.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and CMNCLNUP detects that a SYSPRINT DD statement was not coded for the job step. Output messages that would be written to SYSPRINT are routed to the job log.

`CMN6851I` `Unable to process member names. Input expected for member names and member names could not be found.`

Explanation: Displays when program CMNCLNUP detects no input member names. While deleting a member, program CMNCLNUP determines from which source the member level input originated (SYSIN, ALLMEM keyword, MEMBER= keyword, or pointer to member list area). In this instance no input source indicators for member level processing were initialized. One reason might be internal damage or an overlay to the dynamic work area of program CMNCLNUP. Failure to establish how members were specified to be deleted prevents program CMNCLNUP from performing any member level operation, and causes CMNCLNUP to terminate.

`CMN6852I` `Unable to process member names. Input expected for member names and SYSUT1 contained no members.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and CMNCLNUP detects the use of the ’ALLMEM’ keyword and a SYSUT1 input library that contained no members. When the 'ALLMEM' keyword is specified, program CMNCLNUP (prior to deleting the first member) verifies whether the first directory entry in the SYSUT1 input library contains nulls for the member name. A null entry means the SYSUT1 library is empty, and this message indicates that no action was performed by CMNCLNUP.

`CMN6853I` `Internal call format detected but unexpected mismatch on SYSUT1 data set name, DSN = {``dsn``}`

Explanation: In the message text, DSN is the data set name from the list of data sets passed by the program that calls CMNCLNUP. Displays when program CMNCLNUP determines that it is being called from another program, and CMNCLNUP detects that the data set name associated with the DCB for the SYSUT1 DDNAME was not the one that was expected. When opening a data set, program CMNCLNUP verifies that the data set name assigned to the SYSUT1 DDNAME is the same data set name passed in the data set names list from the program calling CMNCLNUP. In this instance, the data set names did not match. This might be due to an invalid parameter list generated by the program calling CMNCLNUP. Alternatively, the program calling CMNCLNUP might have allocated the wrong data set under the SYSUT1 DDNAME. (SYSUT1 represents the input library used by program CMNCLNUP to compare directory entries.) Failure to validate the data set name associated with the SYSUT1 DD statement prevents any further processing (and thereby preserve the integrity of the SYSUT2 library), causing program CMNCLNUP to terminate.

Solution: Refer to message CMN6846I to obtain the data set name that was actually allocated with the SYSUT1 DDNAME.

`CMN6854I` `Internal call format detected but unexpected mismatch on SYSUT2 data set name, DSN = {``dsn``}`

Explanation: In the message text, DSN is the data set name from the data set list passed by the program calling CMNCLNUP. Displays when program CMNCLNUP determines that it is being called from another program, and CMNCLNUP detects the data set name associated with the DCB for the SYSUT2 DDNAME was not the one expected. When opening a data set, program CMNCLNUP verifies that the data set name assigned to the SYSUT2 DDNAME is the same data set name passed in the data set names list from the program calling CMNCLNUP. In this instance, the data set names did not match. This might be due to an invalid parameter list was generated by the program calling CMNCLNUP. Alternatively, the program calling CMNCLNUP allocated the wrong data set under the SYSUT2 DDNAME. (SYSUT2 represents the output library from which members are deleted by the CMNCLNUP program.) Failure to validate the data set name associated with the SYSUT2 DD statement prevents any further processing (thereby preserving the integrity of the SYSUT2 library), causing program CMNCLNUP to terminate.

Solution: Refer to message CMN6847I to obtain the data set name which was actually allocated with the SYSUT2 DDNAME.

`CMN6855I` `| Total of all members processed =`

Explanation: Displays to indicate the total number of members that were processed from the SYSUT1 library.

`CMN6856I` `| Total of all members deleted =`

Explanation: Displays to indicate the total number of members that were deleted from the SYSUT2 library.

`CMN6857I` `| Total of all members not deleted =`

Explanation: Displays to indicate the total number of members that were not deleted from the SYSUT library.

`CMN6858I` `| Total of all member aliases deleted =`

Explanation: Displays to indicate the total number of alias entries for load modules that were deleted from the SYSUT2 library.

`CMN6859I` `| Total of all member aliases not deleted =`

Explanation: Displays to indicate the total number of alias entries for load modules which were not deleted from the SYSUT2 library.

`CMN6860I` `| Total of all members not found in SYSUT1 =`

Explanation: Displays to indicate the total number of members which were to be processed and were not found in the SYSUT1 library.

`CMN6861I` `| Total of all members not found in SYSUT2 =`

Explanation: Displays to indicate the total number of members that were to be processed and were not found in the SYSUT2 library.

`CMN6862I` `| Total of all members not found in SYSC$DSN =`

Explanation: Displays to indicate the total number of members that were to be processed and were not found in the SYSC$DSN library.

`CMN6863I` `Null data set detected for SYSC$DSN compare library, Correct DD statement to specify a real data set.`

Explanation: Displays when program CMNCLNUP determines that the SYSC$DSN DD statement indicates all I/O operations are to be bypassed. When opening a data set, program CMNCLNUP verifies whether DUMMY was coded as the first parameter in the SYSC$DSN DD statement, or if DSN=NULLFILE was coded in the SYSC$DSN DD statement. A dummy or nullfile status signifies that no input originates from SYSC$DSN. (The SYSC$DSN DDNAME represents the required compare library used by program CMNCLNUP during commit processing.)

Solution: To properly direct the member level processing of program CMNCLNUP, assign a real data set to the SYSC$DSN DD statement when commit processing is requested.

`CMN6864I` `Error on attempted read of JFCB because no data set with SYSC$DSN DDNAME has a DCB allocated.`

Explanation: Displays when program CMNCLNUP attempted to access the Job File Control Block for the SYSC$DSN input library prior to an open, and was unable to successfully obtain a copy of the JFCB. In MVS, data sets can be allocated with Job Control Language, or programatically with Dynamic Allocation using SVC 99. One reason might be that program CMNCLNUP is being called from another program as opposed to running in batch, and the SYSC$DSN data set was not allocated by the calling program prior to CMNCLNUP being called. (SYSC$DSN represents the compare library used by program CMNCLNUP during commit processing.) During commit processing CMNCLNUP compares a SYSUT1 directory entry to a SYSC$DSN directory entry, and when a match is found, the same- named member is deleted from the SYSUT2 library. Failure to access the JFCB for the SYSC$DSN data set, prevents program CMNCLNUP from opening the SYSC$DSN data set, causing CMNCLNUP to terminate when commit processing is requested.

`CMN6865I` `Internal call format detected but unexpected mismatch on SYSC$DSN data set name, DSN = {``dsn``}`

Explanation: In the message text, DSN is the data set name from the data set list passed by the program calling CMNCLNUP. Displays when program CMNCLNUP determines that it is being called from another program requesting commit processing, and CMNCLNUP detects that the data set name associated with the DCB for the SYSC$DSN DDNAME was not the one expected. When opening a data set during commit processing, program CMNCLNUP verifies the data set name assigned to the SYSC$DSN DDNAME is the same data set name passed in the data set names list from the program calling CMNCLNUP. In this instance, the data set names did not match. One reason for this error could be an invalid parameter list generated by the program calling CMNCLNUP. Another reason is that the program calling CMNCLNUP allocated the wrong data set under the SYSC$DSN DDNAME. (SYSC$DSN represents the compare library used by program CMNCLNUP during commit processing.) During commit processing, CMNCLNUP compares a SYSUT1 directory entry to a SYSC$DSN directory entry, and when a match is found, CMNCLNUP deletes the same-named member from the SYSUT2 library. Failure to validate the data set name associated with the SYSC$DSN DD statement stops any further processing (this is done to preserve the integrity of the SYSUT2 library), causing program CMNCLNUP to terminate.

Solution: Refer to message CMN6874I to obtain the data set name which was actually allocated with the SYSC$DSN DDNAME.

`CMN6866I` `Unable to open SYSC$DSN file.`

Explanation: Displays when program CMNCLNUP attempted to open a data set specified by the SYSC$DSN DDNAME, and was unable to open the file. (SYSC$DSN represents the compare library used by program CMNCLNUP during commit processing.) Failure to perform a successful open causes program CMNCLNUP to terminate.

`CMN6867I` `Unable to read directory for SYSC$DSN file.`

Explanation: Displays during commit processing when program CMNCLNUP attempted to read the directory for a data set specified by the SYSC$DSN DDNAME. CMNCLNUP was unable to read this information in order to build a list of all the members that reside in the SYSC$DSN library. Before program CMNCLNUP performs any operation on a member in the SYSC$DSN compare library, CMNCLNUP verifies whether the member name is in the member names list derived from the directory. Failure to perform a successful read of the SYSC$DSN directory prevents program CMNCLNUP from verifying the member names, causing CMNCLNUP to terminate.

`CMN6868I` `No third DDNAME was included in DDNAME list, required DDNAMEs are SYSUT1, SYSUT2, and SYSC$DSN.`

Explanation: Displays when program CMNCLNUP determines that it is being called from another program for commit processing, and detects only two DDNAMEs. Program CMNCLNUP parses the input parameter list (passed from the calling program) to CMNCLNUP. During this process, a DDNAMEs list to be used by program CMNCLNUP was found to contain only two DDNAMEs, indicating an invalid parameter list was created by the calling program. Commit processing is a three library operation. Failure to find all required DDNAMEs prevents program CMNCLNUP from running a data set names verification process, and causes CMNCLNUP to terminate.

`CMN6869I` `Required DDNAME SYSC$DSN not included in DDNAME list.`

Explanation: Displays when program CMNCLNUP determines that it is being called from another program, and detects no SYSC$DSN DDNAME. Program CMNCLNUP parses the input parameter list (passed from the calling program) to CMNCLNUP. During this process, the DDNAMEs list used by program CMNCLNUP was found, but this list did not include the DDNAME SYSC$DSN that is required for commit processing. One cause for this error is an invalid parameter list generated by the program calling CMNCLNUP. (SYSC$DSN represents the compare library used by program CMNCLNUP during commit processing.) During commit processing, CMNCLNUP compares a SYSUT1 directory entry to a SYSC$DSN directory entry, and when a match is found, CMNCLNUP deletes the samenamed member from the SYSUT2 library. Failure to find the required DDNAME SYSC$DSN prevents program CMNCLNUP from comparing directory entries, causing CMNCLNUP to terminate.

`CMN6870I` `Concatenation of data sets to input ddname SYSC$DSN is not allowed.`

Explanation: Displays when program CMNCLNUP detects several input data sets capable of being read in sequence from a single SYSC$DSN DDNAME. While validating the data sets, CMNCLNUP verifies whether a data set is the first one associated with the SYSC$DSN DDNAME. If the data set being verified is found to be part of a DD statement without a DDNAME and that DD statement has been added to SYSC$DSN, a concatenation to the SYSC$DSN input library has occurred. Program CMNCLNUP reads input from library SYSUT1 and SYSC$DSN to compare directory entries, and deletes from only one library in SYSUT2. Failure to maintain a one-to-one relationship for the input libraries in SYSUT1 and SYSC$DSN can compromise the integrity of the deletion process to the SYSUT2 library, and causes CMNCLNUP to terminate.

`CMN6871I` `Required DDNAME SYSC$DSN for commit processing was not found in DDNAME search.`

Explanation: Displays when program CMNCLNUP detects no data sets are associated with the DDNAME SYSC$DSN. While validating data sets, program CMNCLNUP verifies the DDNAME associated with every allocated data set, and DDNAME SYSC$DSN was not found. (SYSC$DSN represents the compare library used by program CMNCLNUP during commit processing.) During commit processing CMNCLNUP compares a SYSUT1 directory entry to a SYSC$DSN directory entry, and when a match is found, CMNCLNUP deletes the same-named member from the SYSUT2 library. Failure to find the required DDNAME S SYSC$DSN prevents program CMNCLNUP from comparing directory entries, and causes CMNCLNUP to terminate. One reason for this is that program CMNCLNUP is being run in batch, and the SYSC$DSN DDNAME was not included in the JCL.

`CMN6872I` `Begin COMMIT process - compare SYSUT1 members to SYSC$DSN, and if a match perform member deletion to SYSUT2.`

Explanation: Displays when program CMNCLNUP intends to perform commit processing for the cleanup of the backup libraries. (SYSC$DSN represents the compare library used by program CMNCLNUP during commit processing.) During this process, program CMNCLNUP compares directory entries from SYSUT1 and SYSC$DSN, and if a match is found, CMNCLNUP deletes the same-named member from the SYSUT2 library.

`CMN6873I` `Member in SYSUT1 and SYSC$DSN same. Member deleted from SYSUT2 library {``member``}`

Explanation: Displays when program CMNCLNUP intends to perform commit processing to cleanup the backup libraries, and deletes the specified member from the SYSUT2 output library. Program CMNCLNUP compared the SYSUT1 and SYSC$DSN libraries for the directory entry 'member'. The directory entries matched. Program CMNCLNUP then deleted the same-named 'member' from the SYSUT2 library.

`CMN6874I` `SYSC$DSN compare library: DSN= {``dsn``}`

Explanation: This message is an informational message displaying the data set name assigned to the SYSC$DSN DDNAME.

`CMN6875I` `Reserved DDNAME SYSC$DSN found as a dynamic allocation without commit processing being specified.`

Explanation: Displays when program CMNCLNUP determines that it is being called from another program, and detects a DDNAME used only in commit processing when the commit option was not specified. While validating data sets, program CMNCLNUP verifies the DDNAME associated with every allocated data set, and the data set assigned to DDNAME SYSC$DSN was available to program CMNCLNUP as a dynamic allocation. (SYSC$DSN represents the compare library used by program CMNCLNUP during commit processing.) During commit processing, CMNCLNUP compares a SYSUT1 directory entry to a SYSC$DSN directory entry, and when it finds match, deletes the same-named member from the SYSUT2 library. Failure to find the commit option specified upon an allocation of the reserved DDNAME SYSC$DSN results in conflicting options that direct the operation of the CMNCLNUP program. This conflict causes CMNCLNUP to terminate. A possible cause for this error might be an invalid parameter list generated by the program calling CMNCLNUP. Alternatively, the program calling CMNCLNUP allocated a data set under the SYSC$DSN DDNAME in error.

`CMN6876I` `Reserved DDNAME SYSC$DSN found specified in JCL without COMMIT keyword in PARM= of EXEC statement.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and CMNCLNUP detects no commit keyword was specified when the SYSC$DSN DDNAME was hard coded in the JCL for the job step. While validating data sets, program CMNCLNUP verifies the DDNAME associated with every allocated data set, and the data set assigned to DDNAME SYSC$DSN was available to program CMNCLNUP as an allocation from JCL. (SYSC$DSN represents the compare library used by program CMNCLNUP during commit processing.) During commit processing, CMNCLNUP compares the entries in the SYSUT1 and SYSC$DSN directories, and when it finds a match, deletes the same-named member from the SYSUT2 library. Failure to find the commit keyword specified when including the reserved DDNAME SYSC$DSN in JCL results in conflicting parameters that direct the operation of the CMNCLNUP program. This conflict causes CMNCLNUP to terminate. (SYSC$DSN is a reserved DDNAME for use by program CMNCLNUP when performing commit processing.) Either remove the SYSC$DSN DD statement from the job step if you plan to perform package processing, or include the commit keyword if you intend to perform commit processing with program CMNCLNUP.

`CMN6877I` `Directory not equal in SYSUT1 and SYSC$DSN: Member={``member``}{``reason``}`

member is the name of the member being compared in the SYSUT1 library and the SYSC$DSN library.
reason is the explanation indicating the field in the directory entry that did not match.

Explanation: Displays during commit processing when program CMNCLNUP detects an unequal directory condition on a SYSC$DSN library. Program CMNCLNUP compared the directory entry member in both the SYSUT1 and the SYSC$DSN input libraries. The entries did not match. Program CMNCLNUP determines the exact field in the directory entry that was different, and explains that difference in the reason message. Message CMN6878I is issued in conjunction with this message to explain the action performed on the SYSUT2 library.

`CMN6878I` `Member was not deleted from SYSUT2 library: Member={``member``}{``reason``}`

member is the member name in the SYSUT2 output library.
reason is the explanation indicating why the member was not deleted.

Explanation: Displays during commit processing when program CMNCLNUP detects an unequal directory condition. Program CMNCLNUP issues this message to identify the member in the SYSUT2 output library.

Solution: Refer to message CMN6877I for an explanation of why this member was not deleted if a reason was not supplied with this message.

`CMN6879I` `Alias entry not deleted from SYSUT2 library: Alias={``alias``}.`

alias is the alternate member name for the load module in the SYSUT2 output library which was assigned by the linkage editor.
member is the member name for the load module in the SYSUT2 output library.

Explanation: Displays during commit processing when program CMNCLNUP detects an unequal directory condition on a SYSUT2 library containing load modules. This message is issued with message CMN6877I to explain the unequal condition, and with message CMN6878I to explain the action taken on the main member. In this instance, program CMNCLNUP compared the directory entry member in both the SYSUT1 and the SYSC$DSN libraries, and found that the entries differed. Because the load member represented by the entry 'member' was not deleted from the SYSUT2 library, program CMNCLNUP searches the directory of the SYSUT2 library for any alternate names associated with the load module. If any alternate name alias is found, this message is issued indicating the alias found for the load module member. This alias remains intact, thereby preserving the integrity of the load module in the SYSUT2 library.

`CMN6880I` `Internal call format detected but zero value found for index to calculate offset into DDNAMEs table.`

Explanation: Displays when program CMNCLNUP determines that it is being called from another program, and detects an invalid entry in the DDNAMEs table. Program CMNCLNUP parses the input parameter list (passed from the calling program) to CMNCLNUP. During this process, a DDNAMEs list used by program CMNCLNUP was found, but an error occurred when the DDNAMEs list was compared to the DDNAME entries in the table maintained by CMNCLNUP. One reason for this is an invalid parameter list was generated by the program calling CMNCLNUP.

`CMN6881I` `Internal call format detected but designated SYSC$DSN input not available by dynamic allocation.`

Explanation: Displays when program CMNCLNUP determines that it is being called from another program, and detects (during commit processing) that DDNAME SYSC$DSN is a JCL allocation. When opening a data set, program CMNCLNUP verifies the attributes of that data set. In this instance, the SYSC$DSN input data set was found to be allocated permanently, rather than dynamically. In MVS, data sets can be allocated with Job Control Language, or programatically with Dynamic Allocation using SVC 99. A possible cause for this error is that program CMNCLNUP is being called from another program, and the other program is running in batch. A job step that runs a program calling CMNCLNUP might contain a SYSC$DSN DDNAME coded in the JCL that has been detected by the CMNCLNUP program. (SYSC$DSN is a reserved DDNAME for exclusive use by program CMNCLNUP for commit processing.) Another program calling CMNCLNUP should not code a SYSC$DSN DDNAME in the JCL.

Solution: Remove the SYSC$DSN DDNAME from the job step, and rerun the step.

`CMN6882I` `JCL format detected but DDNAME SYSC$DSN indicates data set not allocated with permanent attribute.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and a data set attribute conflict was detected. While opening a data set, program CMNCLNUP verifies the attributes of the data set being opened. In this instance, the SYSC$DSN input data set was not allocated permanently, rather than dynamically. One cause might be an allocation error.

Solution: Check the job or message log for possible error messages issued by the operating system for the SYSUT1 library.

`CMN6883I` `Invalid syntax due to unbalanced parentheses were found in the PARM= keyword of EXEC statement.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a syntax error. Program CMNCLNUP examines the run-time options being passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step, and validates keyword values. In this instance, an uneven number of left or right parentheses are specified in the keywords parms.

Solution: Correct the syntax and resubmit the job.

`CMN6884I` `Invalid format in specifying MEMBER keyword in JCL parms due to multiple left parentheses detected.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a format error. Program CMNCLNUP examines the run-time options being passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step, and validates keyword delimiters. In this instance the beginning of a member names list was prefixed with more than one delimiter.

Solution: Indicate the beginning of the member list with a single left parenthesis, and resubmit the job.

`CMN6885I` `Invalid format in specifying MEMBER keyword in JCL parms due to trailing comma indicates expected continuation.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a format error. Program CMNCLNUP examines the run-time options being passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step, and validates keyword separators. In this instance, the end of a member names list was suffixed with a comma indicating a continuation to another line, and the expected continuation was not received.

Solution: Indicate the end of a member list with a single right parenthesis, and resubmit the job.

`CMN6886I` `Invalid format in specifying MEMBER keyword in JCL parms due to contiguous comma separator characters detected.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a format error. Program CMNCLNUP examines the run-time options being passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step, and validates keyword separators. In this instance, more one than one comma was found between two member names indicating a positional parameter format.

Solution: Ensure all members in the list are separated by either a blank or a comma, and resubmit the job.

`CMN6887I` `Invalid format in specifying MEMBER keyword in JCL parms due to multiple right parentheses detected.`

Explanation: Displays when program CMNCLNUP determines that it is running in batch, and detects a format error. Program CMNCLNUP examines the run-time options being passed from the keyword 'PARM=' coded on the 'EXEC=' statement of the job step, and validates keyword delimiters. In this instance, the end of a member names list was suffixed with more than one delimiter.

Solution: Indicate the end of the member list with a single right parenthesis, and resubmit the job.

`CMN6888I` `Error on data set attribute validity check: DDname={``ddname``}`

`CMN6889I` `Attributes for {``see the two examples below``}`

Explanation: This is an informational message and no action is required unless the content of the message does not match your expectation of the data set mentioned. The message is issued by CMNCLNUP for informational purposes and may take the form:

CMN6889I Attributes for SYSUT1: Data set is standard PDS and is system managed
CMN6889I Attributes for SYSUT2: Data set is PDSE, is system managed, and contains no existing records.

`CMN6890I` `Processing for mixed data set types detected an invalid internal PDSEFLAG flag byte, value = {``value``}`

`CMN6891I` `Processing for mixed data set types detected compare data sets of same type, PDSEFLAG flag byte = {``value``}`

`CMN6892I` `Processing for large program object section detected invalid internal PDSOBFLG flag byte, value = {``value``}`

`CMN7000A` `Undefined Area | Area {``area``} is undefined for release {``release``}`

...

CMN7000 DB2 Messages

The following are the error messages generated by CMNDB2PL. All error messages appear in the SYSPRINT DD file. Messages are as close as possible to the input data that caused the error. In the skeleton JCL that comes with the DB2 option, all changes made by CMNDB2PL are made to temporary files. If you leave the temporary file output as is, CMNDB2PL can be rerun one or more times without ill effects.

`CMN7001A` `Memory allocation failure.`

Explanation: Displays when insufficient memory is available to allocate work space. The run terminates. CMNDB2PL dynamically assesses its requirements for memory and allocates work areas as necessary. These work areas are used to store information from the control statement input, from the PDS directories of the staging and baseline DBB and DBR files and the plan names from the DB2 catalog.

Solution: Increase the region size and rerun/restart the job. If the error occurs again and the region size is at its maximum setting, break the change package into smaller change packages and try again.

`CMN7002A` `Unable to open file: {``filename``}`

Unable to open file: WITH DDNAME={ddname}

Explanation: Displays when CMNDB2PL cannot open the file associated with the filename. Other information may be in the job log associated with this job.

Solution: Correct the JCL and rerun/restart the job.

`CMN7003A` `Read error on file: {``filename``}`

Explanation: Displays when an I/O error is encountered reading one of the control or DBB source files.

`CMN7004A` `Invalid duplicate control card keyword: {``keyword``}`

Explanation: Displays when a redundant keyword is found in control statements in the CMNPLCTL input stream.

Solution: Resolve the duplicate keyword and rerun/restart the job.

`CMN7005I` `Control file errors were encountered.`

Explanation: Displays when there are errors in the CMNPLCTL input stream.

Solution: Resolve the issues described in other error messages and rerun/restart the job.

`CMN7006A` `Missing TEMPLATE or OWNER for a DB2ID: {``db2id``}.`

Explanation: If there is no DB2 subsystem ID displayed at the end of the message, then this message indicates that no DB2ID= control statement was found in the CMNPLCTL input stream. If a DB2 subsystem ID is displayed at the end of the message, then this message indicates that no PLANTGT= was found in the set of control statements that follows the DB2ID= control statement for the displayed logical subsystem.

Solution: Add a DB2ID= control statement followed by a set of logical subsystem level control statements, or add a PLANTGT= to the indicated set of logical subsystem level control statements. A PLANTGT= statement is required, even if it defines a null template. See topic "Logical Subsystem Level Control Statements" in the ChangeMan ZMF DB2 Option Getting Started Guide.

`CMN7007A` `Found OWNER,TEMPLATE,LOGICAL or REMOTEID, but no DB2ID: {``keyword``}.`

Explanation: Displays when an OWNER=, PLANTGT=, LOGICAL= or REMOTEID= control statement is read without a preceding DB2ID= statement. The keyword in the offending control statement is displayed at the end of the message.

Solution: Ensure that there is a DB2ID= control statement preceding every set of logical subsystem level control statements. See topic "Logical Subsystem Level Control Statements" in the ChangeMan ZMF DB2 Option Getting Started Guide.

`CMN7008A` `A control card syntax error`

Explanation: Displays when a control statement in the CMNPLCTL input stream contains invalid syntax. Example:

`CMN7008A` `Control card syntax error.`

`CMN7029I` `USEREXIT FORMAT USEREXIT=(language,loadtype)`

Solution: Correct any errors and rerun/restart the job.

`CMN7011I` `CMNDB2PL is terminating due to errors.`

Explanation: Displays when errors are encountered. The run terminates.

Solution: Correct any errors encountered and rerun/restart the job.

`CMN7012A` `Missing TYPE= card.`

Explanation: Displays when a TYPE= control statement is not the first statement in the CMNPLCTL input stream.

Solution: Add a TYPE= control statement at the top of the CMNPLCTL input stream. See topic "Program Level Control Statements" in the ChangeMan ZMF DB2 Option Getting Started Guide.

`CMN7013A` `Invalid DB2 subsystem name: TOO MANY LOGICAL SUBSYSTEMS`

Explanation: The number of DB2ID= control statements exceeds the maximum of 100 for CMNDB2PL.

Solution: Contact Micro Focus Customer Care.

`CMN7014A` `Invalid PDS member name: {``invalid name``}.`

Explanation: Displays when a PDS member name in a MBR= control statement has 0 or more than 8 characters. Example: Exceeded maximum length for keyword = MBR CMN7014A Invalid PDS member name:

Solution: Code a valid name in the MBR=name control statements in the CMNPLDBR and CMNPLDBB input streams.

`CMN7015A` `Incompatible AUTHORITY=JOBID and OWNER= cards`

Explanation: Displays when an OWNER= control statement is read after an AUTHORITY=JOBID statement in the CMNPLCTL input stream. AUTHORITY=JOBID tells CMNDB2PL that the authorization ID is that of the job.

Solution: Change the AUTHORITY=JOBID to AUTHORITY=OWNER, or omit the OWNER= control statement.

`CMN7016I` `Please remove the DB2 keyword specified prior to the BIND keyword and re-run job.`

`CMN7017I` `Missing AUTHORITY= card. Using default: AUTHORITY=OWNER.`

Explanation: Displays when no AUTHORITY= control statement is read in the CMNPLCTL input stream. No default AUTHORITY= control statement is inserted, and CMNDB2PL fails with RC=12.

Solution: Add an AUTHORITY= control statement to the CMNPLCTL input stream. See topic "Program Level Control Statements" in the ChangeMan ZMF DB2 Option Getting Started Guide.

`CMN7018A` `Invalid OWNER ID: {``length``}.`

Explanation: Displays when an OWNER ID is encountered that has either 0 or more than 8 characters. Valid OWNER IDs contain from 1 to 8 characters.

`CMN7019A` `Invalid Template: {``length``}.`

Explanation: Displays when a template is encountered that has either 0 or more than 8 characters. Valid templates contain from 1 to 8 characters.

`CMN7020I` `No Change Man subsystem ID was specified, using default.`

Explanation: Displays when no CMN subsystem id has been specified in the PARM= statement. The job proceeds using the default subsystem id ‘ ’.

`CMN7021A` `Unable to connect to Change Man Started Task: {``subsystem id``}.`

Explanation: Displays when an unsuccessful attempt is made to connect to the started task represented by subsystem id. The job terminates after the three control files are checked for syntax.

`CMN7022I` `Successful connect to Change Man Started Task: {``subsystem id``}.`

Explanation: Displays when a successful connection is made to the started task represented by subsystem id. This is an informational message only.

`CMN7023A` `Invalid execution parm {``invalid parm``}.`

Explanation: Displays when an invalid parameter is found instead of SUBSYS=id. SUBSYS=id is the only valid passed parameter.

`CMN7024A` `Not communicating with Change Man Started Task.`

Explanation: Displays when a cross-memory service request is issued to the started task, but the started task appears to be down.

Solution: You should verify that the started task is still running; if not, restart it; then rerun/restart this job. There is no requirement that CMNDB2PL communicate with the started task. This capability is held over from an older version, mainly for you who used information from the started task to pass to your user exit program.

`CMN7025A` `Unable to establish connection to DB2 subsystem: {``subsystem id``}.`

Explanation: Displays when the physical DB2 subsystem is down or otherwise unavailable.

Solution: You should verify the following. This last error is likely if the package master at a remote site does not match the physical DB2 subsystem definition list at a development site.

The ChangeMan ZMF started task has established the Call Attach connection with the subsystem in question
The subsystem is running
The global administrator has defined the DB2 subsystem as a physical DB2 subsystem.

`CMN7026A` `Unexpected DB2 SQL return. {``msg``}.`

Explanation: Displays when you, upon requesting the list of plans from the DB2 catalog, encounter an SQL error code other than 0 or 100.

Solution: You should check the CMNPRINT and DSNTRACE (if allocated) filenames of the started task to determine the nature of the error.

`CMN7027A` `Your installation does not include the Change Man DB2 Support.`

Explanation: You cannot run CMNDB2PL without purchasing the DB2 support option.

Solution: You should contact a ChangeMan ZMF sales representative.

`CMN7028A` `Processing terminated by Plan Lookup User Exit.`

Explanation: Displays when Exit CMNEX101 issues a return code of 12 or 16. Both of these codes direct CMNDB2PL to end with a return code of 12. If CMNEX101 issues any messages, they are printed following the report line that shows the rejected bind control statement set member.

`CMN7029I` `{``text varies``}.`

Explanation: Shows the cause of a CMNDB2PL error. Examples:

CMN7029I DBB Member = PLANNME

CMN7029I Not found in STG or BAS concatenation.

CMN7029I PKG Member = PKGNAME

CMN7029I Not found in STG or BAS concatenation.

CMN7008A Control card syntax error.

CMN7029I USEREXIT FORMAT USEREXIT=(language,loadtype)

CMN7029I Missing ddname = DBBSSTG

Solution: Correct the problem and resubmit the CMNDB2PL job.

`CMN7030A` `Invalid value returned by Plan Lookup User Exit.`

Explanation: Displays when you pass back a value greater than the original passed value by more than 10. CMNDB2PL builds a set of bind control statements and passes them to a user exit program, CMNEX101. CMNEX101 is also passed a field that indicates the number of statements in the set. CMNEX101 can add up to 10 statements to the bind control statement. CMNEX101 then indicates the new statement count in the passed field.

`CMN7031A` `All bind control statements were rejected.`

Explanation: Displays when the user exit program CMNEX101 rejects all passed bind control statements.

`CMN7032I` `No bind statements found for this {``run type``}.`

Explanation: Run type is either BACKOUT or DEMOTE. DEMOTE deletes the staged program from the highest level promotion library, causing all promotion levels to invoke the production copy of the program. BACKOUT restores the old production copy of the program. In both of these cases, if there was no production version of the program (that is, this is new development), then CMNDB2PL finds no plans that match the associated DBRM in the production catalog. In this case, there is no bind replace required for this plan. When this is true for all of the DBRMs in a change package, message CMN7032I is issued.

`CMN7033A` `Invalid {``keyword``}`

Explanation: Displays when the value in a keyword control statement is invalid.

Solution: See the ChangeMan ZMF DB2 Option Getting Started Guide for a list of valid values for each CMNDB2PL keyword control statement.

`CMN7034A` `Staged DBRM {``dbrm name``} is not referenced by any plans.`

Explanation: Displays when a DB2 program in the change package has a DBRM that is not referenced by any plans in the staging library, nor by any plans in the DB2 catalog. This generates the NOBASEDBBRC error (q.v.).

`CMN7035I` `DB2 TABLE CREATED | Impact analysis DB2 table has been created.`

`CMN7036I` `DB2 TABLE DROPPED | Impact analysis DB2 table has been dropped (erased).`

`CMN7037I` `Successful connect to DB2 subsystem {``subsystem``}.`

Explanation: Displays when CMNDB2PL issues a DB2 Call Attach “CONNECT” request. The return code for the CONNECT was 0. Problems can still occur when an OPEN THREAD request is issued, especially if there are problems using the plan.

`CMN7038I` `PHYSICAL DB2 IDENTIFIED | Global DB2 PHYSICAL subsystems have been identified.`

Explanation: Informs a global administrator that the physical DB2 subsystems have been specified and saved in the package master.

`CMN7039I` `Invalid DB2 package type specified: {``data``}`

Explanation: Displays when you enter data for control statement BINDPACKAGETYPE=data that is not a 3-character component type.

Solution: You must enter a valid ChangeMan ZMF component type. CMNDB2PL does not verify the type. It only checks the length of the component type. Correct this error, specifying the component type for DB2 BIND PACKAGE statements.

`CMN7040I` `PHYSICAL DB2 UNDEFINED | Undefined DB2 physical subsystem information.`

Explanation: Displays when a global administrator tries to define the global logical subsystems, but has not defined the physical subsystems.

`CMN7041I` `Error encountered reading list of DB2 Packages to bind.`

Explanation: Displays when either a DB2 package member name is not a valid PDS member name, or the keyword MBR= is missing. The run halts after all syntax checking.

Solution: Correct any errors and rerun/restart the job.

`CMN7042I` `Use AUTHORITY=OWNER or AUTHORITY=OWNER,INSERT`

Explanation: Displays when the OWNER authority is requested, but the type of operation is not INSERT. The valid syntax is one of the following:

AUTHORITY=OWNER This causes any OWNER() clauses to be replaced with the OWNER from the logical subsystem.
AUTHORITY=OWNER,INSERT This works like AUTHORITY=OWNER, with the additional operation of adding an OWNER() clause to a set of bind statements if none exists.

`CMN7043A` `| Error reading component {``component``}`

`CMN7044A` `| No data records for component {``component``}`

`CMN7045A` `| Insufficient memory obtained for member {``member``}`

`CMN7046A` `| Error retrieving directory entry for member {``member``}`

`CMN7047A` `| DDNAME {``ddname``} not allocated`

...

`CMN7048A` `| Unable to open DDNAME {``ddname``}`

...

`CMN7049A | DDNAME {``ddname``} record format not fixed`

...

`CMN7050I` `| Member {``member``} already exists in temporary pds`

`CMN7051I` `| Tempds member limit exceeded. id/logical/mem: {``id``}/{``logical``}/{``mem``}`

`CMN7052A` `SVC 99 Return code = {``code``}`

`CMN7053A` `Invalid subparameter in ENABLE/DISABLE bind parm - not passed to exit'`

`CMN7054A` `| Error allocating/opening temporary parsing dataset -check joblog.`

`CMN7055I` `PHYSICAL DB2 UNDEFINED | Enter * in DB2 SUBSYS or SITE field for DB2 subsystem list.`

Explanation: Displays when you try to define a global DB2 logical subsystem with an invalid combination of physical DB2 subsystem and site.

Solution: Type * in the DB2 Subsys field of the logical subsystem (or the Site field) to see a list of valid DB2 physical subsystem and site combinations defined in global DB2 administration.

`CMN7056A` `Error in bind parameter parsing process - contact Micro Focus Customer Care.`

Explanation: Displays when there is a problem in CMNDB2PL with BIND command parsing and a more definitive message cannot be issued.

Solution: Contact Micro Focus Customer Care. The job log may contain an IKJxxxxx message that may be helpful in diagnosing the problem.

`CMN7057A` `Bind command syntax error, unparsable component {``component``}`

Explanation: IBM service routine IKJPARS, which is called by CMNDB2PL, is unable to successfully parse the input BIND command.

`CMN7058A` `Incomplete bind command in component {``component``}`

`CMN7059A` `No bind command found in component {``component``}`

`CMN7060I` `LOGICAL DB2 DEFINED | Global DB2 “LOGICAL” subsystem names have been defined.`

Explanation: Tells you that global DB2 logical subsystems have been defined and stored in the package master.

`CMN7065I` `LOGICAL DB2 UNDEFINED | Undefined global DB2 logical subsystems; contact Global Admin.`

Explanation: Displays when you try to define an application logical DB2 subsystem when no logical subsystems have been defined in DB2 global administration.

`CMN7070I` `LOGICAL DB2 UNDEFINED | Enter * in LCMD field for global DB2 logical subsystem list.`

Explanation: Displays when you try to define an application DB2 logical subsystem with an invalid logical physical DB2 subsystem.

Solution: Type * in the Logical Name field of the logical subsystem to see a list of valid DB2 logical subsystems defined in DB2 global administration.

`CMN7075I` `LOGICAL DB2 DEFINED | Local DB2 LOGICAL subsystem names have been defined.`

Explanation: Tells you that application DB2 logical subsystems have been define and saved in the package master.

`CMN7080I` `LOGICAL DB2 UNDEFINED | Undefined local DB2 logical subsystems; contact Local Admin.`

Explanation: Displays when you try to define active libraries when no logical DB2 subsystems are defined in DB2 application administration.

`CMN7085I` `LOGICAL DB2 UNDEFINED | Enter * in LOGICAL NAME field for application DB2 logical name list.`

Explanation: Displays when you try to define an DB2 active library with a logical DB2 subsystem that is not defined in DB2 application administration.

Solution: Type * in the Logical Name field of the logical subsystem to see a list of valid DB2 logical subsystems defined in DB2 application administration.

`CMN7090I` `ACTIVE LIBRARIES DEFINED | Application DB2 “ACTIVE” libraries have been defined.`

Explanation: Informs an application administrator that active libraries have been specified and stored in the package master.

`CMN7095I` `DUPLICATE ENTRY | This logical name is already defined to a physical DB2 subsystem.`

Explanation: Displays when the logical name defined has previously been defined.

`CMN7098I` `CMNDB2PL ending. Warnings issued.`

Explanation: Displays when CMNDB2PL has completed processing its input data. The WARNINGRC is issued upon exit.

`CMN7099I` `CMNDB2PL ending. No errors were encountered.`

Explanation: Displays when CMNDB2PL has completed processing its input data. The program return code is 0.

CMN7200 CICS Utility Error

`CMN7200E` `CMNCICS2 Bypassed because of errors.`

Explanation: Displays when an error occurs in processing input cards for CMNCICS1. The input file is CMNIN. Processing terminates.

Solution: You should refer to CMNOUT printer file for details.

`CMN7201E` `CMNCICS1 Unable to load CMNCICS2.`

Explanation: Displays when CMNCICS2 cannot be loaded. Processing terminates. The program may not be in the library, or the region size may be too small.

`CMN7202E` `UNKNOWN CARD | CMNCICS1 Unknown card in input member.`

Explanation: Displays when an unrecognized card is found in the input stream. Processing terminates. The only valid cards are TARGET, DFHRPL, and PROGRAM.

`CMN7203E` `NO PROGRAM CARDS | CMNCICS1 Group without any programs at all.`

Explanation: Displays when no PROGRAM statements exist for the DFHRPL card.

Solution: You should check the card for formatting errors.

`CMN7204E` `BAD PARMS-TARGET CRD | CMNCICS1 Only TARGET, PHA, NEW, CONSNAME parms allowed`

`CMN7205E` `MISSING DFHRPL | CMNCICS1 Group has no DFHRPL statements at all.`

Explanation: Displays when the DFHRPL statement is missing for the TARGET card. This statement is required when you have specified a TARGET card.

`CMN7206E` `DATA SET NOT FOUND | CMNCICS1 DFHRPL dataset does not exist.`

Explanation: Displays when the data set name found on the TARGET card does not exist.

Solution: You should check to see if the data set exists with ISPF, or if the data set name is missing or invalid.

`CMN7207E` `FAILED ALLOC: XXXX | CMNCICS1 DFHRPL dataset failed to allocate.`

Explanation: Displays when allocation fails for the data set on the DFHRPL card, although the data set’s name is valid.

`CMN7208E` `MISSING DSNAME | CMNCICS1 DFHRPL dataset missing.`

Explanation: Displays when no data set is specified on the DFHRPL card.

Solution: You should check the card.

`CMN7209E` `FAILED TO LOAD | Program xxxxxxxx was not found in DFHRPL library.`

Explanation: Displays when the load of the program on the PROGRAM card fails because RPL is not open.

`CMN7210E` `TARGET NOT FOUND | Target CICS not active on system.`

Explanation: Displays when the CICS region specified on the TARGET card is not running. NEWCOPY does not need to be performed.

`CMN7211E` `TARGET NOT READY | Target CICS Initializing or terminating.`

Explanation: Displays when the CICS region specified on the TARGET card is in initialization or termination. NEWCOPY cannot be performed.

`CMN7213E` `CICS RETURNED ERRORS | CICS regions returned errors when doing newcopy`

Explanation: ZMF attempted a CICS NEWCOPY/PHASEIN for an application program, but the application program is not found in the target region.

Solution: Create a definition for the application program in the target CICS region.

`CMN7214E` `EXCI FAILURE | Unable to establish EXCI session with target CICS`

Explanation: Displays when CMNCICS2 is unable to allocate or open an EXCI connection to the target CICS region to perform a NEWCOPY/PHASEIN. The NEWCOPY is not performed.

Solution: Ensure the target CICS region is running, and that the EXCI connection has been properly installed. See the ChangeMan ZMF Installation Guide for the steps to install the CICS EXCI facility.

`CMN7215E` `INSTALL ERROR | ZMF newcopy support not installed in target CICS`

Explanation: Displays when program CMNCICS2 is unable to start the SEML transaction in the target CICS region to perform NEWCOPY/PHASEIN. The NEWCOPY is not performed.

Solution: See the ChangeMan ZMF Installation Guide for the steps to install the SEML transaction in the target CICS region.

`CMN7250E` `FORMAT ERROR | Formatting error in SYSIN.`

Explanation: Displays when the input contains errors. The input file is CMNIN. The input stream is rejected.

Solution: You should refer to CMNOUT Print file for details.

`CMN7251E` `DFHCSD ERROR | IMPORT error processing DFHCSD dataset, code-ICGP.`

Explanation: Displays when an error occurs during DFHCSD VSAM file processing. Processing terminates.

`CMN7252E` `DFHCSD ERROR | IMPORT error processing DFHCSD dataset, code-IBGP.`

Explanation: Displays when an error occurs during DFHCSD file processing. Processing terminates.

`CMN7253E` `DATA SET FULL | DFHCSD dataset FULL condition during IMPORT operation.`

Explanation: Displays when the DFHCSD file has filled up during an IMPORT.

Solution: You should allocate more space for the DFHCSD file.

`CMN7254E` `OPEN ERROR | OPEN error for PDS dataset during IMPORT operation.`

Explanation: Displays when the input PDS fails to open.

`CMN7255E` `SEQUENCE ERROR | Sequence error in input dataset stream during IMPORT operation.`

Explanation: Displays when a sequencing error occurs on input.

Solution: You should see CMNOUT for details.

`CMN7256E` `OPEN FAILURE | Open failure of DFHCSD dataset.`

Explanation: Displays when the DFHCSD fails to open. The probable cause is contention with another batch job.

`CMN7257E` `DUP DFHCSD CARD | Duplicate DFHCSD card in this set.`

Explanation: Displays when more than one DFHCSD card has been specified in a group. The group is rejected.

`CMN7258E` `TOO MANY IGROUPS | Too many IGROUPS specified.`

Explanation: Displays when too many IGROUP cards have been specified in a group. Only 256 IGROUP cards are allowed per group. The group is rejected.

`CMN7259E` `SEQUENCE ERROR | SEQ. error - need DFHCSD/EXP card.`

Explanation: Displays when an export DFHCSD card is expected, but not found.

`CMN7260E` `IGROUP NOT FOUND | IGROUP specification not found.`

Explanation: Displays when no IGROUP specification has been provided. Only one is needed per group.

`CMN7261E` `MUST BE LAST CARD | SEQ. error - must be last card in set.`

Explanation: Displays when the OGROUP card is not the last card in a group. The OGROUP card must be the last card in a group.

`CMN7262E` `DUPLICATE OGROUP | Duplicate OGROUP specification.`

Explanation: Displays when more than one OGROUP exists in a group. Only one OGROUP is allowed per group. The group is rejected.

`CMN7263E` `DUPLICATE EXPORT | Duplicate EXPORT card for this set.`

Explanation: Displays when another export with the same name is found in an input set. The input set is rejected.

`CMN7264E` `DFHCSD REQUIRED | Required DFHCSD card must precede EXPORT card.`

Explanation: Each IMPORT card must have an accompanying and immediate previous DFHCSD card.

`CMN7265E` `DUP IMPORT CARD | Duplicate IMPORT card or required DFHCSD card missing.`

Explanation: Displays when another IMPORT card with the same name is found in an input set.

`CMN7266E` `OPEN FAILURE | Open failure for IMPORT PDS dataset.`

Explanation: Displays when the import PDS fails to open.

`CMN7267E` `ALLOC FAILURE | Dynamic allocation of {``data set``} FAILED, RC = {``return code``}.`

Explanation: Displays when the named file fails to allocate.

`CMN7268E` `E15 SORT ERROR | Unrecoverable VSAM error for MODCB in E15 SORT exit.`

Explanation: Displays when an unrecoverable error occurs in the E15 SORT exit while trying to read the DFHCSD file on behalf of SORTIN.

`CMN7269E` `E15 SORT ERROR | Unrecoverable VSAM error for POINT in E15 SORT exit.`

Explanation: Displays when the data set specified with DFHCSD keyword fails to position at the specified IGROUP.

`CMN7270E` `E15 SORT ERROR | Unrecoverable VSAM error for GET in E15 SORT exit.`

Explanation: Displays when the DFHCSD file fails to read properly in the E15 SORT exit.

`CMN7271E` `E35 SORT ERROR | Unrecoverable logic error in E35 SORT exit, code/NOWA.`

Explanation: Displays when an unrecoverable error occurs during SORT output processing.

`CMN7272E` `E35 SORT ERROR | OPEN error for OUTPUT PDS dataset in E35 SORT exit.`

Explanation: Displays when the output PDS from the SORT fails to open.

`CMN7273E` `E35 SORT ERROR | Error during PUT operation to PDS dataset in E35 SORT exit.`

Explanation: Displays when the E35 PUT operation to the output PDS fails.

`CMN7274E` `E35 SORT ERROR | Unrecoverable logic error in E35 SORT exit, code TRTE.`

Explanation: Displays when the specified data set name is full and needs to be compressed.

`CMN7275E` `CMNCICS6 TERMIN | CMNCICS6 terminated due to errors.`

Explanation: Displays when an error occurs while you try to invoke SORT.

Solution: You should contact ChangeMan ZMF Support.

`CMN7276I` `WAITING FOR LOCK | CMNCICS6 waiting for lock on DFHCSD dataset.`

Explanation: Displays when another user has the lock on the DFHCSD file. CMNCICS6 waits 10 seconds and retries.

`CMN7299E` `Unable to open {``data set``}.`

Explanation: Displays when ChangeMan ZMF tries to access either CMNLIB, CMNIN (SYSIN file for CICS jobs), or CMNMSGCD (Messages and Codes file), but cannot open these data sets.

Solution: You should verify the following:

The DD statement in the CICS1 JCL is valid.
CMNMSGCD is the ChangeMan ZMF STEPLIB concatenation.

CMN7500 Application Interface

`CMN7500I` `Attempting to initiate dialog with started task.`

Explanation: Displays when your batch job tries to establish contact with the started task in another address space. This is a CMNAPI initialization message. When the connection is established correctly, you receive the CMN7510I return message.

`CMN7506I` `Package Delete Error | Package {``package``} is still attached to release {``release``}.`

`CMN7507I` `Command Not Allowed | I - Package {``package``} is attached to a release, command not allowed.`

`CMN7508I` `Command Not Allowed | Package {``package``} is not attached to a release.`

`CMN7510I` `| Session established with Change Man started task.`

Explanation: Displays when your batch job has successfully established contact with the started task in another address space. This is a CMNAPI initialization message, and it is a companion message to CMN7500I.

`CMN7512I` `| Parsing error | “FUNCTION=” keyword missing.`

Explanation: Displays when the “FUNCTION=function name” keyword is missing from the control card currently being parsed by CMNAPI.

`CMN7513I` `| Parsing error | function to execute is invalid or missing.`

Explanation: Displays when the “FUNCTION=function name” keyword is incorrect on the control card currently being parsed by CMNAPI. The function name is incorrect. Valid function names are freeze and promote.

`CMN7514I` `| Parsing error | “PACKAGE=” keyword missing.`

Explanation: Displays when the “PACKAGE=package name” keyword is missing from the control card currently being parsed by CMNAPI.

Solution: You should specify a package name.

`CMN7515I` `| Parsing error | length of mnemonic name not 3 or 4 bytes.`

Explanation: Displays when the “PACKAGE=package name” keyword is incorrect on the control card currently being parsed by CMNAPI. A package mnemonic must be either 3 or 4 bytes, followed by the numeric package number.

`CMN7516I` `| Parsing error | package number is not numeric.`

Explanation: Displays when the “PACKAGE=package name” keyword is incorrect on the control card currently being parsed by CMNAPI. Only numbers 0 through 9 are allowed for the package number.

`CMN7517I` `| Parsing error | invalid SYSIN statement.`

Explanation: Displays when the SYSIN DD card is either missing or invalid. This is a batch stage control card error.

`CMN7518I` `| Invalid option. ‘OPT=‘ must be ‘DEV’ or ‘stg’.`

Explanation: You must stage from either the development libraries or package driven lists. Anything else is invalid for this required parameter.

`CMN7520I` `| End of data on SYSIN - terminating.`

Explanation: Displays when CMNAPI has finished reading all the SYSIN control cards, and it is starting its end-of-job processes. This is a CMNAPI end-of-job message.

`CMN7521I` `| End of data on SYSIN.' (FastAudit Msg)`

`CMN7530I` `| Session terminated with ChangeMan started task.`

Explanation: Displays when CMNAPI has finished processing and has released its link with the ChangeMan ZMF started task. This is a CMNAPI end-of-job message.

`CMN7540I` `| End of job; RC = {``nnn``}.`

Explanation: Displays when CMNAPI has finished processing, nnn is the return code from the ChangeMan ZMF started task. This is a CMNAPI end-of-job message.

`CMN7550I` `| Unable to open SYSIN file.`

Explanation: Displays when CMNAPI attempts to open the SYSIN data set to read the control cards for this run. An error occurs opening the SYSIN data set, that can be caused by a missing DD card.

`CMN7560I` `| Invalid JOB statement, application interface terminated.`

Explanation: Displays when promotion has been called from CMNAPI, and is attempting to build and submit a JCL to run a full promotion in batch mode. The package master is read to obtain the JOB control statements, and these JOB control statements are validated. The validation check fails.

`CMN7570I` `INVALID OPTION | Option not available in batch mode.`

Explanation: Displays when you try to perform an invalid process using the CMNAPI member.

`CMN7572I` `INVALID PARAMETER | Parsing error {``keyword``} keyword has invalid parameter {``parameter``}.`

Explanation: Displays when you enter an invalid parameter for an API2 keyword.

Solution: See the ChangeMan ZMF Administrator’s Guide for the set of API2 parameters that ChangeMan ZMF supports.

`CMN7573I` `INVALID KEYWORD | Parsing error {``keyword``} is an invalid keyword.`

Explanation: Displays when you enter an invalid keyword for an API2 keyword.

Solution: See the ChangeMan ZMF Administrator’s Guide for the set of API2 parameters that ChangeMan ZMF supports.

`CMN7590I` `PROMOTION ERROR | Promotion following freeze disallowed. Contact Local Admin.`

Explanation: Displays when you try to run a full promotion following a successful batch freeze. (You replied YES to the auto promotion message on the CMNFRZ01 panel). The project parameter BATCH PROMOTION FOLLOWING FREEZE has been set to NO, and this action is prohibited.

Solution: See the “Promoting and Demoting Changes” section of the ChangeMan ZMF User’s Guide for more information.

`CMN7591I` `PROMOTION ERROR | Promotion has returned a non-zero return code.`

Explanation: Displays when you try to run a full promotion following a successful batch freeze. (You replied YES to the auto promotion message on the CMNFRZ01 panel). An error occurs in CMNPROMO that aborts the promotion and returns an error code to CMNFREEZE.

Solution: See the “Promoting and Demoting Changes” section of the ChangeMan ZMF User’s Guide for more information.

`CMN7592I` `SELECTION ERROR | Global parameters require promotion following freeze.`

Explanation: Displays when the global parameter BATCH PROMOTION FOLLOWING FREEZE has been set to YES, and forces promotion to follow freeze. (You replied NO to the auto promotion message on the CMNFRZ01 panel).

Solution: You must run promotion following freeze. See the “Promoting and Demoting Changes” section of the ChangeMan ZMF User’s Guide for more information.

`CMN7593I` `UNMATCHED PKG NAME | {``package name``} - Package name mismatch.`

Explanation: Displays when you have selected freeze option 3 (submit a batch job to run a batch promotion) following a successful batch freeze. CMNFREEZE attempts to create and submit the JCL for this job, but the package name is corrupted. CMNFREEZE exits without submitting the job.

Solution: See the “Promoting and Demoting Changes” section of the ChangeMan ZMF User’s Guide for more information.

`CMN7600I` `INVALID PARM LIST | Invalid parm list supplied.`

`CMN7610I` `| Unable to process baseline library {``library``}.`

`CMN7620I` `| Missing APPL= sysin card`

`CMN7630A` `| APPL= {``appl``} sysin does not match any application defined.`

`CMN7640A` `| Unable to open BASLNRPT file.`

`CMN7650A` `| Unable to open SUMRYRPT file.`

...

`CMN7660A` `| Invalid sysin card.`

          *-----------------------------------------------------------------*
          *         Reserved for AUDIT 7800 - 8000                          *
          *-----------------------------------------------------------------*

`CMN7800I` `| No component history record found for component {``component name``}`

`CMN7801A` `| Audit discovered too many integrity errors in the package to continue.`

`CMN7802A` `| For details, run the package integrity service against {.`

`CMN7803I` `| AUDIT30 not allocated, audit will not report zFS component information.`

`CMN7805I` `Package packageid components failed integrity checking.`

Explanation: The package freeze function calls the ZMF package, cmponent, integrty service to check that no orphaned components appear in a package during the packagefreeze function. If orphaned components are found, this message is issued and the package freeze is not performed

CMN8000 Information/System

`CMN8000I` `INFO SUBSYSTEM ERROR | INFO rule is set for INFO to pre-authorize all package creation.`

`CMN8010I` `INFO SUBSYSTEM ERROR | Unable to locate INFO change record {``record name``}.`

`CMN8020A` `INFO SUBSYSTEM ERROR | Function terminated; INFO down - contact Global Admin.`

...

`CMN8040I` `INFO SUBSYSTEM ERROR | INFO record {``record name``} already referred to by package {``package name``}.`

`CMN8050I` `INFO SUBSYSTEM ERROR | Package INFO record {``record name``} rejected; contact INFO approver.`

`CMN8060I` `INFO PARMS GENERATED | Global INFO/SYS parameters generated.`

`CMN8065I` `INFO PARMS GENERATED | {``application``} application INFO/SYS parameters generated.`

`CMN8099I` `INFO/SYS message.`

CMN8200 Remote Procedure Call (RPC)

`CMN8200I` `Allocate error | Record format parameter not supplied.`

`CMN8201I` `Allocate error | Invalid record format supplied.`

`CMN8202I` `Allocate error | Invalid terms of space supplied.`

`CMN8203I` `Allocate error | Invalid dataset organization supplied.`

`CMN8204I` `Dataset RPC error. | Dataset RPC encountered a problem.`

`CMN8205I` `Allocate error. | User not authorized to allocate dataset.`

`CMN8206I` `Dataset RPC error. | Dataset name not supplied.`

...

`CMN8210I` `Update error | Source and load record update error.`

`CMN8211I` `Update error | Copies record update error.`

`CMN8212I` `Update error | Package name not specified.`

`CMN8213I` `Update error | Target name not specified.`

`CMN8214I` `Update error | Library type not specified.`

`CMN8215I` `Update error | Problem encountered updating the package library record.`

`CMN8216I` `{ UPDATED | { for { has been updated.`

`CMN8217I` `{ UPDATE ERROR | { for { encountered update errors.`

`CMN8220I` `Package Allocation error | Package name not specified.`

`CMN8221I` `Package Allocation error | Library type not specified.`

`CMN8222I` `Package Allocation error | Library type not deferred.`

`CMN8223I` `Package Allocation error | Library type {``type``} was not allocated.`

`CMN8224I` `Component Activity File type {``type``} not defined; contact ADMIN.`

Explanation: You tried to check out a component type with an application library type definition that specifies:

    CHECKOUT COMPONENT ACTIVITY FILE ===> YES (Y/N)
    COMPONENT ACTIVITY FILE TYPE ===> ttt

...where library type ttt is not defined.

Solution: Your application administrator must either define library type ttt or change the CHECKOUT COMPONENT ACTIVITY FILE field to NO for the library type that you tried to check out.

`CMN8225I` `Record not found | Global record not found in package master record for {``type``}.`

`CMN8226I` `Update Error | Problem encountered updating global library type record for {``type``}.`

`CMN8227A` `Requested routine has not been found in the target Db2 catalog.`

Explanation: Probably due to the relevant installation binds not having been done or execute permission not granted. If anything of this nature goes wrong then the UI or service will be returned a 'not found' condition.

Solution: Look also at SERPRINT output for more information.

`CMN8230I` `Update Error | Problem encountered updating component history for {``component``}.`

`CMN8231I` `Update Error | Component history load section full, data not added for {``component.libtype``}.`

Explanation: A component history update could not add new associated load information as the record is full. Any other fields in the update are completed successfully, and the return code is zero.

Solution: Contact Micro Focus Customer Care.

`CMN8235A` `Copy Error | Problem encountered copying component.`

`CMN8236A` `Copy Error | Source and target names are the same.`

`CMN8237I` `Component Copied | Component(s) copied to output dataset.`

`CMN8238A` `Component activity file type must be different from source type type.`

`CMN8240I` `Process Error | {``is already linked to {``.`

`CMN8242I` `Process Error | Error encountered deleting load records for {.`

`CMN8245I` `Component Locked | Component locked successfully.`

`CMN8250I` `Lock Failed | Component is already locked by {``id``}.`

`CMN8251I` `Lock Failed | Component to be locked is not specified.`

`CMN8252I` `Lock Failed | Component to be locked is not found.`

`CMN8255I` `Component Unlocked | Component unlocked successfully.`

`CMN8256I` `Unlock Failed | Recompiled component can not be unlocked.`

`CMN8257I` `Unlock Failed | Relinked component can not be unlocked.`

`CMN8258I` `Lock Failed | Recompiled component can not be locked.`

`CMN8259I` `Lock Failed | Relinked component can not be locked.`

`CMN8260I` `Unlock Failed | Component to be unlocked is not specified.`

`CMN8261I` `Unlock Failed | Component to be unlocked is not found.`

`CMN8262I` `Component is locked | Component to be staged is locked by {``id``}.`

`CMN8263I` `Process Error | Component is already locked by {``id``}.`

`CMN8270I` `Component Deleted | {``component``} has been deleted.`

`CMN8271I` `Delete Error | Component delete function encountered a problem deleting component(s).`

`CMN8272I` `Delete Error | Component to be deleted is not specified.`

`CMN8273I` `Delete Error | Dataset to be deleted from is not specified.`

`CMN8280I` `Process error | This component is already in the package as an output of a source component.`

`CMN8281I` `Process error This component is already in the package as a SCRATCH/RENAME.`

`CMN8285I` `NO REMOTE SITES | Remote sites are prohibited for the ''ALL'' environment.`

`CMN8290I` `Update Error | Problem encountered updating work information for {.`

`CMN8292I` `Update Error | Work Information processing not turned on.`

`CMN8295I` `Process Error | Source language name not supplied for validation.`

`CMN8296I` `Process Error | Compile procedure not supplied for validation.`

`CMN8297I` `Invalid option | Valid options are UPDATE, STAGE, SUBMIT or FULL.`

`CMN8300I` `RPC message | General use message for RPCs.`

`CMN8301A` `SCC not found | Source Code Control for this application not found.`

`CMN8302A` `SCC found | Source Code Control record for this application found.`

`CMN8303A` `SCC create error | Unable to create Source Code Control record for this application.`

`CMN8304A` `SCC created | Source Code Control record created for this application.`

`CMN8305A` `Replica not found | No Replica found for this application.`

`CMN8306A` `Replica found | Replica found for this application.`

`CMN8307A` `Replica create error | Unable to create Replica record for this application.`

`CMN8308A` `Replica created | Replica record created for this application.`

`CMN8309A` `Replica deleted | Replica record deleted from this application.`

`CMN8310A` `Package Create Error | Invalid work request number supplied.`

`CMN8312A` `Package Create Error | Invalid department number supplied.`

`CMN8314I` `Package Created | Package general parameters have been created`.

`CMN8315I` `Global Parms updated | Global Parameters record has been updated.`

`CMN8320A` `Missing field | Schedule date is missing for calendar update.`

`CMN8321A` `Missing field | Schedule count is missing for calendar update.`

`CMN8322A` `Invalid date field | Schedule date must be in YYYYMMDD format.`

`CMN8323A` `Invalid date field | Schedule date is beyond our 1 year calendar.`

`CMN8324A` `Missing field | Maximum date is missing for calendar update.`

`CMN8325A` `Missing field | Maximum count is missing for calendar update.`

`CMN8326A` `Invalid date field | Maximum date must be in YYYYMMDD format.`

`CMN8327A` `Invalid date field | Maximum date is beyond our 1 year calendar.`

`CMN8328I` `Global Site updated | Global Site record has been updated.`

`CMN8329A` `Update error | Site name not supplied, cannot continue with update.`

`CMN8330A` `Update error | Schedule count beyond allowed maximum of 255.`

`CMN8331A` `Update error | Maximum count beyond allowed maximum of 255.`

`CMN8332A` `Update error | Schedule count is greater than maximum count.`

`CMN8333A` `Update error | Maximum count is less than scheduled count.`

`CMN8334A` `Invalid date field | Peg date must be in YYYYMMDD format.`

`CMN8340I` `Package site list | Package site list returned.`

`CMN8341I` `Package site list | No package site list to return.`

`CMN8342I` `Dataset migrated | {``data set``} is in migration status.'`

`CMN8345I` `Source component list | Source component list returned for package {``package``}.`

`CMN8346I` `Copy component list | Copy component list returned for package {``package``}.`

`CMN8347I` `Source to Includes list | Source to Includes/Copies list returned for component {``component``}.`

`CMN8348I` `Source to Includes list | There are no Source to Includes/Copies list to return for component {``component``}.`

`CMN8350I` `Component deleted | Component {``component``} deleted from package {``package``}.`

`CMN8351I` `Package not found | Package {``package``} not found.`

`CMN8352I` `Component not found | Component {``component``} not found in package {``package``}.`

`CMN8353I` `Problem encountered | Problem encountered deleting component {``component``}.`

`CMN8354I` `Component delete error | Package name not specified for delete.`

`CMN8355I` `Component delete error | Component name not specified for delete.`

`CMN8356I` `Component delete error | Library type not specified for delete.`

`CMN8357I` `Component delete error | Package is not in DEV status, delete not allowed.`

`CMN8358I` `Invalid userid | Userid must be specified for security check.`

`CMN8359I` `Client/Server Version Error | Client version = {``version``}, Server version = {``version``}.`

`CMN8360I` `Component record deleted | Component {``component``} record deleted from package {``package``}.`

`CMN8361I` `Component delete error | Component {``component``} record not found in package {``package``}.`

`CMN8362I` `Component delete error | Problem encountered deleting {``component``} record from package {``package``}.`

`CMN8363I` `Log Record(s) Found | Log record(s) requested found.`

`CMN8364I` `Log Record(s) Not Found | Log record(s) requested not found.`

`CMN8365I` `Log Update Error | There was an error in updating the Log file.`

`CMN8370I` `Library type updated | Library type record for {``library``} have been updated.`

`CMN8375I` `Global record updated | Global library type record for {``library``} have been updated.`

`CMN8380I` `Appl record updated | Application library type record for {``library``} have been updated.`

`CMN8381I` `Update Error | Problem encountered updating application library type record for {``library``}.`

`CMN8382I` `Record not found | Application record not found in package master.`

`CMN8383I` `Record not found | Package user record not found in package master.`

`CMN8385I` `Baselines listed | Baseline library(ies) listed for application {``application``}.`

`CMN8390I` `Update error | {``component``} was not specified.`

`CMN8391I` `Update Error | Problem encountered updating application baseline library record for {.`

`CMN8392I` `Appl record updated | Application baseline library record for {``component``} have been updated.`

`CMN8393I` `Update error | Baseline level must be between 2 - 9 for storage means of {.`

`CMN8394I` `Update error | Baseline level must be between 2 - 255.`

`CMN8395I` `Active libraries listed | I - Application DB2 'ACTIVE' libraries listed for {``type``}.`

`CMN8396I` `Library types listed | Global library type(s) listed.`

`CMN8397I` `Library types listed | Application library type(s) listed for {``application``}.`

`CMN8398I` `Language names listed | Application language names listed for {``application``}.`

`CMN8400I` `Language name updated | Application language name record for {``application``} have been updated.`

`CMN8401I` `Update Error | Problem encountered updating application language name record for {``application``}.`

`CMN8410I` `Global_IMS record listed | The Global_IMS record was listed.`

`CMN8411A` `Global_IMS record not found | The Global_IMS record was not found.`

`CMN8412I` `Local_IMS record listed | The Local_IMS record was listed.`

`CMN8413A` `Local_IMS record not found | The Local_IMS record was not found.`

`CMN8414A` `Update Error | Problem encountered updating the Global_IMS record.`

`CMN8415A` `Update Error | Problem encountered updating the Local_IMS record.*`

`CMN8416I` `Record Updated | GLOBAL_IMS record updated.`

`CMN8417I` `Record Updated | LOCAL_IMS record updated.`

`CMN8418I` `Record Listed | Package_IMS record Listed.`

`CMN8419A` `Record Not Found | Package_IMS record not Found.`

`CMN8420I` `Record Updated | Package_IMS record updated.`

`CMN8421A` `Problem Encountered | Problem Encountered Updating Package_IMS record.`

`CMN8422I` `Record Created | Package_IMS Control Region Record Created.`

`CMN8423I` `Record not Created | IMS Global Activation of Packages set to no.`

`CMN8424I` `Record Already Exists | Package_IMS record already exists.`

`CMN8425A` `Error Creating Record | Error Creating Package_IMS record.`

`CMN8426I` `Record Listed | IMS DBD Record Listed.`

`CMN8427A` `Record Not Found | Global DBD Record not found.`

`CMN8428I` `Record Listed | Global PSB Record Listed.`

`CMN8429A` `Record Not Found | Global PSB Record not found.`

`CMN8430I` `Record Listed | Local DBD Record Listed.`

`CMN8431A` `Record Not Found | Local DBD Record not found.`

`CMN8432I` `Record Listed | Local PSB Record Listed.`

`CMN8433A` `Record Not Found | Local PSB Record not found.`

`CMN8434A` `Record Not Found | Package PSB Record not found.`

`CMN8435I` `Record Updated | Local DBD record updated.`

`CMN8436A` `Update Failed | Problem encountered updating Local DBD record.`

`CMN8437I` `Record Updated | Local PSB record updated.`

`CMN8438A` `Update Failed | Problem encountered updating Local PSB record.`

`CMN8439I` `Record Updated | Global DBD record updated.`

`CMN8440A` `Record Not Found | Global DBD record not found.`

`CMN8441A` `Update Failed | Problem encountered updating Global DBD record.`

`CMN8442I` `Record updated | Global PSB record updated.`

`CMN8443A` `Update Failed | Problem encountered updating Global PSB record.`

`CMN8444I` `Record updated | Package PSB record updated.`

`CMN8445A` `Update Failed | Problem encountered updating Package PSB record.`

`CMN8446I` `Record Listed | Package IMS PSB record listed.`

`CMN8450I` `Designated procedure | Designated procedure for component {``component``} listed.`

`CMN8451I` `Designated procedure | Designated procedure for component {``component``} not defined.`

`CMN8455I` `Process error | Source component is present in the package, it must be staged not recompiled.`

Explanation: Displays when you attempt to recompile a source component from baseline into a package where the component is already present.

Solution: You must either stage the source component which is already in the package or, if the source component is there in error, delete the component from the package before attempting to recompile from baseline.

`CMN8456I` `Process error | Recompile from SRC or like-src library type only.`

`CMN8457I` `Process error | Designated procedure enforced, use {``procedure``} procedure.`

`CMN8458I` `Process error | Designated procedure enforced, use {``option``} compile options.`

`CMN8459I` `Process error | Designated procedure enforced, use {``option``} user options.`

`CMN8460I` `Process error | Designated procedure enforced, use {``link option``} link options.`

`CMN8461I` `Process error | Designated procedure enforced, use {``language``} language.`

`CMN8462I` `Process error | Designated procedure enforced, use {``procedure``} for DB2 precompile.`

`CMN8463I` `Process Warning | Staging dataset has record format U.`

`CMN8464I` `Process Warning | {``component``} is not a component within the package.`

`CMN8465I` `Process Complete | Component {``component``} has passed the checkout validation RPC.`

`CMN8466I` `Process Complete | Component {``component``} has passed the stage validation RPC.`

`CMN8467I` `Process Complete | Component {``component``} has passed the recompile validation RPC.`

`CMN8468I` `Process Error | Component {``component``} already resides in the package, use component update RPC.`

`CMN8469I` `Recompile Submitted | Recompile job submitted for component {``component``}.`

Explanation: This information message is displayed when the final Recompile panel has been displayed and the user has pressed enter to process the Recompile.

...

`CMN8470I` `Global DB2 record listed | The Global DB2 Physical Subsystem record listed.`

`CMN8471I` `Global DB2 not defined | The Global DB2 Physical Subsystem record was not defined; contact Global Admin.`

`CMN8472I` `'Validation Successful' | Approval list update request for entity {``entity``} has been validated.`

`CMN8473I` `No jobs submitted | No sites found that match criteria.`

`CMN8474I` `No notifications | No outstanding approval notifications.`

`CMN8475I` `Update error | Record not found in package master, update bypassed.`

`CMN8476I` `Log Request Complete | Log record has been written to the Log File.`

`CMN8477I` `Submit Request Complete | Member {``member``} submitted from package {``package``}.`

`CMN8478I` `INFO Not applicable | Site INFO rule does not request INFO/MAN approval.`

...

`CMN8479I` `User notified | {``user``} has been sent the requested message.`

`CMN8480I` `Record updated | Package promote component {``component``} has been updated.`

`CMN8481I` `Update error | Problem encountered updating package promote component {``component``}.`

`CMN8482I` `Request processed | {``APPROVE,REJECT,REVIEW,CHECKOFF``} update request for entity {``entity``} is complete.`

`CMN8483I` `Validation Successful | Package {``package``} validation successful.`

`CMN8490I` `Process error | {``MISSING PARAMETER``} was not specified.`

`CMN8492I` `Security error | {``COMPONENT``} is secured by rule {``rule``}.`

`CMN8493I` `Process complete | {``member``} passed member level security check.`

`CMN8495A` `Cannot approve | Package has activity since freeze - use online Approve function.`

`CMN8500I` `Process error | {``process``} request data required but not found.`

`CMN8501I` `Process error | The user supplied number of members to be copied is zero.`

`CMN8502I` `Process error | {``invalid parameter``} is invalid.`

`CMN8600I` `List complete | The {``list``} list is complete.`

Explanation: Displays when the list is complete. This message issues when a LIST RPC request has been made, the list is returned, then the list is complete. It is issued by several components, which is why you see the ’{’ which is variable, depending on the function that issues it.

...

`CMN8602I` `Problem encountered | Problem encountered {.`

`CMN8605I` `List continuing | The {``list``} list is continuing.`

`CMN8610I` `Authorization error | User needs {``access``} access to {``global admin``}.`

`CMN8620I` `Record deleted | Component description for {``component``} within package {``package``} have been deleted.`

`CMN8622I` `Record not found | Component description for {``component``} within package {``package``} could not be found.'`

`CMN8624I` `Problem encountered | Problem encountered processing component description for {``component``} within package {``package``}.`

`CMN8626I` `Record listed | Component description for {``component``} within package {``package``} list.`

...

`CMN8628I` `Record updated | Component description for {``component``} within package {``package``} have been updated.`

...

`CMN8630I` `Dataset not found | DDNAME {``ddname``} was not found within Started Task procedure.`

...

`CMN8640I` `Problem encountered | Application {``application``} already defined.`

...

`CMN8642I` `Application created | Application {``application``} created.`

`CMN8644I` `Application deleted | Application {``application``} deleted.`

`CMN8646A` `Duplicate Record | Package Master record already exists.`

`CMN8648I` `Undefined Record | Undefined approval entity {``entity``} - contact Local Admin.`

`CMN8650I` `Create/add error | {``component security record/scheduling record``} is full.`

`CMN8652I` `'Process error' | {``userid``} is already defined in the {``component security record``}.`

`CMN8656I` `SERBSAM problem | Problem encountered processing the {``function``} function.`

`CMN8658A` `Process error | Problem encountered processing dataset directory.`

`CMN8660I` `Process error | Baseline definition and library type definition out of synch.`

CMN8700 ChangeMan ZMF Extended Services

MESSAGES 8700 - 9000 are reserved for CMN SERVICES ONLY!

`CMN8700I` `Service completed | {``service``} service completed`

`CMN8701I` `Request pending | {``service``} service request pending`

...

`CMN8702I` `Request Cancelled | {``service``} service request cancelled`

...

`CMN8703I` `Service failed | {``service``} service failed`

`CMN8704I` `Service submitted | {``service``} service submitted`

`CMN8705I` `Full CMAST traversal | {``service``} service completed at the cost of reading every component master record.`

`CMN8710A` `Restricted Value | {``value``} is restricted by Global Option`

`CMN8711I` `Service error | Save staging version error; Function = {``function``}, Reason code = {``reason code``}`

Explanation: Displays when an error occurs creating or accessing a staging version of a component. The internal function and reason code are displayed for help in problem resolution.

Solution: Messages in the started task SYSPRINT may provide additional information.

`CMN8712I` `Service completed | Save staging version bypassed.`

Explanation: Displays when a user updates a component in a package and requests that the version of the component currently in the staging library not be saved as a staging version.

`CMN8714A` `Invalid line command | Commands: B(rowse), C(ompare), D(elete), M(erge), R(ecover), V(iew)`

Explanation: Valid commands: B(rowse), C(ompare), D(elete), M(erge), R(ecover) or V(iew). Displays within the component Version Control function when one or more component versions have been selected with an invalid line command.

Solution: Correct the invalid line command or clear all pending line commands by entering the RESET command in the primary command field.

`CMN8715A` `Invalid request | Select 2 versions for a compare.`

Explanation: Displays within the component Version Control function when an invalid number of staging versions are selected with the C (compare) line command.

Solution: Type line command C by two staging versions on the Version Control panel to compare them. More than two versions cannot be compared at one time.

`CMN8716A` `Not authorized | Admin authority is required to delete saved staging versions.`

Explanation: Displays when a user attempts to delete a staging version on the Version Control panel. Staging versions may only be deleted by users who have update authority to global or application administration and update authority to the application.

`CMN8718A` `Delete not allowed | Only saved staging versions may be deleted.`

Explanation: Displays when a user attempts to delete a staging (STG) or baseline (BAS) version from the Version Control panel. Staging and baseline versions of components may not be deleted from within this function.

`CMN8719A` `Invalid line command | Valid commands: B(rowse), C(ompare) or V (View)`

Explanation: Displays from the Version Control panel within the Query Package function when one or more staging versions have been selected with an invalid line command.

Solution: Correct the invalid line command or clear all pending line commands by entering the RESET command in the primary command field.

`CMN8720I` `Fingerprints same | Fingerprint matches - service abandoned`

`CMN8721I` `Source is older | Source is older - FGP={``DATSET/MEMBER FINGERPRINT HASH TOKEN``}/STP={``DATASET/MEMBER TIME STAMP``}`

`CMN8722I` `Request dataset locked | Request locked (serialization) by UID={``id``}`

`CMN8723I` `Dataset is empty | Requested dataset contains no data`

`CMN8724I` `Dataset in use | Dataset is allocated to another user`

`CMN8725I` `Versions not installed | Save staging versions is not installed.`

...

`CMN8726I` `M+R is not licensed | M+R must be licensed to merge versions.`

Explanation: You have attempted to merge staging versions using the ChangeMan ZMF M+R Option, but a license for that option has not been applied. You must license the M+R Option to merge staging versions.

...

`CMN8727A` `Invalid request | Select 3 to 8 versions for a merge.`

`CMN8730I` `Invalid input | Input field {``field``} has invalid data: {``data``}.`

`CMN8732I` `Service error | Data set information not available.`

`CMN8734I` `Service error | Unable to delete data set; Reason code = {``reason code``}`

`CMN8736I` `Service error | {``online form``} does not exist in package master.`

...

`CMN8738I` `Load failed | Failed to load I/O service, abend code= {``code``}`

...

`CMN8740I` `Service error | I/O routine under construction.`

...

`CMN8742A` `Service error | {``copy forward/super complex/participating package``} package {``package``} does not exist.`

...

`CMN8744A` `Service error | Invalid request block length for {``package description/participating package/affected application/remote site``}.`

...

`CMN8746A` `Service error | Affected application {``application``} does not exist.`

...

`CMN8748A` `Service error | Affected application {``application``} must be different from your application.`

...

`CMN8749I` `Service error | File Tailoring Program {``program``} was not found.`

...

`CMN8750A` `Service error | Address space creation failed.`

...

`CMN8752I` `Record not found. | {``affected application/package link/package scheduling/release link``} record not found.`

...

`CMN8754I` `Process Error | CMNUPDAT encountered a problem processing an SRD component.`

...

`CMN8755I` `Version not found | Specified previous version does not exist.`

...

`CMN8756A` `Function restricted | Package LINKs restricted; contact Local Admin.`

`CMN8758A` `Already Linked | LINK error - package is already LINKed.`

`CMN8760A` `Not Linked | UNLINK error - package is not LINKed.`

`CMN8762A` `Service Error | No update request field was specified.`

`CMN8764A` `Not Linked | Package is not Linked.`

`CMN8766A` `Linked Package | Package is Linked, process restricted.`

...

`CMN8767A` `Delete Prohibited | Linked package cannot be deleted. Please unlink the package first.`

...

`CMN8768A` `Service Error | Component Build for like-src and like-oth library types only.`

`CMN8770A` `Service Error | Component Build not allowed for inactive components.`

`CMN8772A` `Service Error | User must supply language name and compile procedure as a set.`

`CMN8774A` `Service Error | No compile parms found for {``component``} in package master.`

`CMN8776A` `Service Warning | Component was not locked`

`CMN8778A` `Unlock Failed | Component locked by {``id``}.`

`CMN8780A` `Delete Error | Component delete failed ; { - {.`

`CMN8781A` `Invalid Input Lib Type | {``type``} is not a valid relink input library type.`

Explanation: The INPUT LIBRARY TYPE for relink is not like-object, like-NCAL, likeload, or LCT.

Solution: Use a like-object, like-NCAL, like-load, or LCT library type for relink INPUT LIBRARY TYPE.

`CMN8782I` `Delete Error | Component delete failed ; {``component``} - {.`

Explanation: SERNET Member Level Security in SEREX005 prevented the deletion of a library member. See the description of exit program SEREX005 in the ChangeMan ZMF Customization Guide.

Solution: Change the access rules in your security system for the library.name.member DSN constructed by SEREX005, or disable SEREX005 with one of the following:

Use SERNET keyword parameter EX005=NO.
Customize the exit as described in source code comments at the top of the program.

`CMN8784A` `Service Error | Selected baseline level not defined - {``level``}.`

`CMN8786I` `Service Error | Baseline Stats only supports PDS and SRD storage means.`

Explanation: The DSS SERVICE BASESTAT service only supports PDS and stacked reverse delta (SRD) members.

`CMN8787I` `Service Error | Baseline Stats encountered problem processing {``component``}.`

Explanation: The DSS SERVICE BASESTAT service encountered a problem processing the named component.

`CMN8800I` `Invalid DSN Pattern | {``pattern``} is an invalid DSN pattern for release datasets.`

`CMN9000` `ChangeMan ZMF Network`

`CMN9000I` `Undefined request message unit code; @MU={``code``}.`

`CMN9001I` `Invalid userid specified.`

...

`CMN9002I` `Invalid password specified.`

...

`CMN9003I` `Password specified has expired.`

...

`CMN9004I` `Logon authorization failed; RC= {``return code``}.`

`CMN9005I` `Logon accepted for userid={``user id``}.`

...

`CMN9020I` `Invalid message header; starting record does not exist.`

...

`CMN9021I` `Invalid message header; unspecified record request number parameter.`

...

`CMN9022I` `Levels maintained invalid (1st byte + or -; followed by 3 numerics).`

...

`CMN9023I` `Invalid name specified (enter 8 alphamerics; 1st byte alphabetic).`

`CMN9024I` `Undefined baseline data set for level {``level``}; contact Local Admin.`

`CMN9025I` `Data set level selected does not contain any components.`

`CMN9026I` `The specified pattern produced no matching components.`

`CMN9027I` `No component history found to list.`

`CMN9028I` `Undefined promotion data set for level {``level``}; contact Local Admin.`

`CMN9029I` `No data set names found to list.`

`CMN9030I` `No package staging information found to list.`

`CMN9031I` `Stage disallowed; component must be checked out to CMNNET.`

...

`CMN9032I` `Component was successfully staged from CMNNET.`

...

`CMN9033I` `System error; invalid pacing reply.`

...

`CMN9034I` `Staging disallowed; component must be checked out to CMNNET.`

...

`CMN9035I` `D/A HISTORY USED | History obtained from a deleted/archived package.`

Explanation: Component history was obtained from the deleted/archived package with the latest component history changed date and time. This is usually the latest baselined package that has been deleted from the package master, by housekeeping, due to aging.

...

`CMN9036I` `ACTIVE HISTORY USED | History obtained from a package in motion.`

Explanation: Component history was obtained from the package in motion with the latest component history changed date and time.

`CMN9037I` `CURRENT HISTORY USED | History obtained from the current package.`

Explanation: Component history was obtained from the current package.

...

`CMN9038I` `BASELINED HISTORY USED | History obtained from baselined package.`

Explanation: Component history was obtained from the baselined package with the latest package baselined date and time.

...

`CMN9100I` `UNDEFINED LIBRARY TYPE | Library type for APS entity {``name``} not defined.`

`CMN9101I` `APS PARTS LIST ERROR | RC = {``error``} from APS Parts List interface.`

...

`CMN9102I` `APS INTERFACE READ ERROR | ERROR reading CMN/APS interface A2VEPL file.`

`CMN9105I` `MEMBER NOT FOUND | Unable to find member {``member``} in {``dsn``} dataset.`

...

`CMN9110I` `APSLIBTB TABLE ERROR | ERROR building APSLIBTB/baseline table.`

`CMN9111I` `APSLIBTB TABLE ERROR | ERROR building APSLIBTB/libtype table.`

...

`CMN9112I` `ENTITY TYPE NOT FOUND | No entity type {``type``} found in APSLIBTB table.`

...

`CMN9113I` `NO MAP NAME AVAILABLE | Map name for the DC target is not in APSSCRN.`

...

`CMN9114I` `READ ERROR | SERBSAM module encountered a READ error.`

`CMN9115I` `ALLOCATION FAILURE | Allocation failure for DSN='proj.grp.APSSCRN'.`

...

`CMN9116I` `OPEN FAILURE | Open failure for DSN='proj.grp.APSSCRN'.`

`CMN9117I` `CLOSE FAILURE | Close failure for DSN='proj.grp.APSSCRN'.`

...

`CMN9118I` `UNALLOCATION FAILURE | Unallocation failure for DSN='proj.grp.APSSCRN'.`

`CMN9119I` `APSLIBTB TABLE ERROR | ERROR processing APSLIBTB table.`

...

`CMN9120I` `CMNAPLTB TABLE ERROR | ERROR processing CMNAPLTB parts list table.`

`CMN9121I` `CMNAPLTS TABLE ERROR | ERROR processing CMNAPLTS parts list table.`

...

`CMN9130I` `APS RULES VIOLATION | Invalid APS type specified for this rule.`

`CMN9140I` `APS COMPONENT NOT FOUND | Component { - Lib type { not found.`

...

`CMN9141I` `APS COMPONENT NOT FOUND | Component { - Lib type { not found in this baseline library.`

`CMN9150I` `INVALID APS FUNCTION | Function is not allowed for the APS option.`

...

`CMN9155I` `APS NOT LICENSED | APS option not licensed, but exit CMNEX019 invoked with APS exit turned on.`

`CMN9160I` `REQUEST TERMINATED | Remaining checkout requests have been terminated.`

...

`CMN9165I` `APS CHECKOUT ERROR | Checkout to personal library disallowed; contact Admin.`

`CMN9199I` `APS STAGING ERROR | A staging error has occurred.`

...

`CMN9850E` `Specify search string | At least one search string necessary to scan.`

`CMN9999A` `MESSAGE NOT FOUND | message ID does not exist.`

Explanation: Type PANELID at the command line, and note the panel name.

Solution: Contact ChangeMan ZMF support and explain the circumstances leading up to the message.

...

CMNUP00 CMNUPnna

`CMNUP00I` `CMNUPDAT EXECUTION PARAMETERS: {``list``}.`

Explanation: Informational message that displays when the CMNUPDAT module completes, listing the parameters in effect for this run.

`CMNUP01E` `INVALID FUNCTION CODE`

Explanation: Informational message that displays when an invalid function code has been entered.

Solution: Change to valid code and rerun.

`CMNUP02E` `UNRECOGNIZED KEYWORD: {``badkeyword``}.`

Explanation: Informational message that displays when there is an unrecognized keyword in the parameter list.

Solution: Check for typographical errors and/or compare to list in the execution parameters, correct and rerun.

`CMNUP03E` `AMBIGUOUS KEYWORD: {``list``}.`

Explanation: Informational message that displays when there is a keyword in the list that is in contention with another.

Solution: Verify you are using the correct keywords for this run and rerun.

`CMNUP04I` `KEYWORD REQUIRES VALUE: {``list``}.`

Explanation: Informational message that displays when there is a keyword that requires a value that is not present.

Solution: Enter the required value and rerun.

`CMNUP05E` `INVALID SYNTAX: {``location``}.`

Explanation: Informational message that displays when a syntax error is present.

Solution: Validate, modify where necessary and rerun.

`CMNUP06E` `TERM LENGTH ERROR: {``list``}.`

Explanation: Informational message that displays when a term entered is either too long or too short.

Solution: Validate, correct and rerun.

`CMNUP07E` `VALUE NOT NUMERIC:`

Explanation: Informational message that displays when a non-numeric number is entered where a numeric is required.

Solution: Validate, correct, and rerun.

`CMNUP08E` `VERSION NUMBER EXCEEDS MAXIMUM.`

Explanation: Informational message that displays when the version number exceeds the maximum level expected.

`CMNUP09E` `DDNAME NOT FOUND: {``list``}.`

Explanation: Informational message that displays when the CMNUPDAT module cannot complete, because there is a DDNAME either missing or misspelled.

Solution: Correct and rerun.

`CMNUP10E` `DATASET NOT FOUND: {``list``}.`

Explanation: Informational message which displays when the CMNUPDAT module cannot complete, because one or more data set names listed in the JCL is not in the catalog; generally mistyped or archived.

`CMNUP11E` `DATASET HAS INVALID DSORG: {``list``}.`

Explanation: Informational message that displays when the CMNUPDAT module cannot complete, because one or more data sets has an invalid data set organization for the function being performed.

`CMNUP12E` `OPEN FAILED FOR DDNAME {``list``}.`

Explanation: Informational message that displays when the CMNUPDAT module cannot complete, because one or more input files could not be opened.

`CMNUP13E` `NO MEMBERS SELECTED - PROCESSING TERMINATED`

Explanation: Informational message that displays when no members met the selection criteria and the program run was terminated.

`CMNUP14I` `APPLY FUNCTION SELECTED.`

Explanation: Informational message notifying you that the APPLY function was selected for this run.

`CMNUP15I` `RESTORE FUNCTION SELECTED`

Explanation: Informational message notifying you that the RESTORE function was selected for this run.

`CMNUP16I` `DELETE FUNCTION SELECTED`

Explanation: Informational message notifying you that the DELETE function was selected for this run.

`CMNUP17I` `COPY FUNCTION SELECTED.`

Explanation: Informational message notifying you that the COPY function was selected for this run.

`CMNUP18I` `BASELINE LIBRARY: DD= {``list``}.`

Explanation: Informational message that displays to indicate which DD statement contains the baseline library.

`CMNUP19I` `DELTA LIBRARY: DD={``ddname``}`

Explanation: Informational message that displays to indicate which DD statement contains the DELTA library.

`CMNUP20I` `STAGING LIBRARY: DD={``ddname``}`

Explanation: Informational message that displays to indicate which DD statement contains the Staging library.

`CMNUP21I` `BASELINE LIBRARY: DSN={``dsname``}`

Explanation: Informational message that displays to indicate the data set name of the baseline library.

`CMNUP22I` `DELTA LIBRARY: DSN={``dsname``}`

Explanation: Informational message that displays to indicate the data set name of the Delta library.

`CMNUP23I` `STAGING LIBRARY: DSN={``dsname``}`

Explanation: Informational message that displays to indicate the data set name of the Staging library.

...

`CMNUP24I` `APPLY PROCESSING STARTED FOR MEMBER`

`CMNUP25I` `RESTORE PROCESSING STARTED FOR MEMBER`

`CMNUP26I` `DELETE PROCESSING STARTED FOR MEMBER`

`CMNUP27I` `COPY PROCESSING STARTED FOR MEMBER`

`CMNUP28I` `BASELINE MEMBER NOT FOUND - ADD ASSUMED:`

`CMNUP29E` `BASELINE MEMBER NOT FOUND - REQUEST TERMINATED`

`CMNUP30E` `DELTA MEMBER NOT FOUND - REQUEST TERMINATED`

...

`CMNUP31E` `STAGING MEMBER NOT FOUND - REQUEST TERMINATED`

...

`CMNUP32I` `NO DIFFERENCES FOUND - NULL DELTA GENERATED`

...

`CMNUP33I` `COMPARE OPERATION SUCCESSFUL - DELTA GENERATED`

...

`CMNUP34E` `COMPARE OPERATION FAILED: RC={``return code``}`

`CMNUP35I` `SPECIFIED PREVIOUS VERSION DOES NOT EXIST - MEMBER BYPASSED`

`CMNUP36I` `DELTA DECK SPECIFIES BASELINE MEMBER IS TO BE DELETED`

`CMNUP37I` `ALL DELTA DECK LEVELS EXHAUSTED: DELTA DECK TO BE DELETED`

`CMNUP38I` `REVERSE UPDATE OPERATION SUCCESSFUL`

`CMNUP39E` `REVERSE UPDATE OPERATION FAILED: RC={``return code``}`

`CMNUP40E` `MAXIMUM ARCHIVE LEVELS REACHED - OLDEST LEVEL(S) DROPPED`

`CMNUP41I` `UNABLE TO READ DIRECTORY IN {``something``}`

`CMNUP42E` `DIRECTORY FULL IN {``something``}`

`CMNUP43E` `INSUFFICIENT SPACE IN {``ddname``}`

Explanation: Displays when there is insufficient space in the dataset allocated to {ddname}.

Solution: Increase the available space in the dataset allocated to the ddname specified. The dataset name can be determined by reviewing messages CMNUPD18I thru CMNUPD23I, which are displayed prior to this message. See "CMNUP18I" on page 198.

...

`CMNUP44I` `PDS COMPRESS AND RETRY WILL BE ATTEMPTED`

`CMNUP45I PDS COMPRESS SUCCESSFUL`

...

`CMNUP46E PDS COMPRESS FAILED`

`CMNUP47I DATA SET REALLOCATION WILL BE ATTEMPTED`

...

`CMNUP48I BASELINE DATA SET SUCCESSFULLY REALLOCATED TO DDNAME`

`CMNUP49I DELTA DATA SET SUCCESSFULLY REALLOCATED TO DDNAME`

...

`CMNUP50I STAGING DATA SET SUCCESSFULLY REALLOCATED TO DDNAME`

`CMNUP51E DATA SET REALLOCATION FAILED`

...

`CMNUP52E I/O ERROR LOADING MEMBER`

`CMNUP53E I/O ERROR SAVING MEMBER`

...

`CMNUP54I MEMBER NOT FOUND:`

`CMNUP55I LOADED MEMBER`

...

`CMNUP56I SAVED MEMBER`

`CMNUP57E STOW ERROR: FAILED TO DELETE {``member``}`

...

`CMNUP58E STOW ERROR: FAILED TO RENAME *component TO component IN DELTALIB`

Explanation: Displays when a space problem is encountered while processing a stacked reverse delta (SRD) component from baseline. The name of the component being processed at the time of failure is referenced within the message. The name of the baseline library experiencing the space problem is referenced by the DD name within the message. Solution: You should check to ensure that the data set referenced by the DD above, is adequately allocated, specifically the directory blocks and extents.

...

`CMNUP59E STOW ERROR: FAILED TO UPDATE ISPF STATS FOR {``member``}`

`CMNUP60I DELETED MEMBER {``member``}`

...

`CMNUP61I RENAMED MEMBER {``member``}`

`CMNUP62I NULL UPDATE | ISPF STATS UPDATED FOR {``member``}`

...

`CMNUP63E ERROR COMPRESSING NEW BASELINE MEMBER: REASON={``reason``}`

`CMNUP64E ERROR COMPRESSING NEW DELTA DECK: REASON={``reason``}`

...

`CMNUP65E ERROR DECOMPRESSING BASELINE MEMBER: REASON={``reason``}`

`CMNUP66I ERROR DECOMPRESSING DELTA DECK: REASON={``reason``}`

...

`CMNUP67E APPLY FAILED FOR MEMBER {``member``}`

`CMNUP68E RESTORE FAILED FOR MEMBER {``member``}`

...

`CMNUP69E DELETE FAILED FOR MEMBER {``member``}`

`CMNUP70E COPY FAILED FOR MEMBER {``member``}`

...

`CMNUP71I` `APPLY SUCCESSFULLY COMPLETED FOR MEMBER {``member``}`

`CMNUP72I` `RESTORE SUCCESSFULLY COMPLETED FOR MEMBER {``member``}`

...

`CMNUP73I` `DELETE SUCCESSFULLY COMPLETED FOR MEMBER {``member``}`

`CMNUP74I` `COPY SUCCESSFULLY COMPLETED FOR MEMBER {``member``}`

...

`CMNUP95I` `NUMBER OF MEMBERS UPDATED: {``number``}`

`CMNUP96I` `NUMBER OF MEMBERS IN ERROR: {``number``}`

...

`CMNUP97E` `PROCESSING TERMINATED DUE TO ERRORS`

`CMNUP98E` `PROCESSING COMPLETED WITH ERRORS`

...

`CMNUP99I` `PROCESSING SUCCESSFULLY COMPLETED`

CMNDSPTM

These messages from batch impact analysis update program CMNDSPTM have no message numbers.

2010060415461096 GBE SRE GBESRE05 CPY 9999 999 GBECOPY5 01A917B4(029A97D8) has stale UD flag

Explanation: The stale UD flags are probably the result of a previously cancelled CMNDSPTM step. This program uses a special update protocol that flags a set of obsolete relation rows as deleted-for-update. Deleted-for-update operations are followed by insert-for- update operations, and the process is completed by an end-of-update operation. Insert-for-update operations replace the memo-deleted rows where possible, and the end-of-update operation physically deletes remaining rows marked deleted-for-update.

If a delete-for-update, insert-for-update, end-of-update sequence is interrupted, some rows may be left with deleted flags still set, which is what is meant by stale UD flag.

Solution: The quickest repair is a reorganization of the the I/A data space (unload the LDS, delete, redefine, reload the LDS), but a complete rebuild (i.e.. CMNIA000/LDSLOAD) will also repair the problem.

ChangeMan ZMF Message Descriptions

ZMF Server Messages

CMN_000I CMNENTFY Error - Port or IP address not found

CMN_000I CMNENTFY Error - Event Notification Task Exiting

CMN_004I CMNENTFY Port {nnnnnn} IP address {iiiiii}

CMN_204I CMN Unable to allocate JCL file to submit {site position}

CMN_208I CMN Member {member} not found

CMN_300 Attach Failure

CMN_300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=ELDS,@TCA={address},@TCB={address}

CMN_300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=IADS,@TCA={address},@TCB={address}

CMN_300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=INFO,@TCA={address},@TCB={address}

CMN_300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=SERVDLAY,@TCA={address},@TCB={address}

CMN_300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=SSV,@TCA={address},@TCB={address}

CMN_300I CMNSTART Initialization in progress; @TCA={address}

CMN_301I Loading CMN services; @ADR={address}

CMN_302I CMNSTART ERO has been disabled Server started with reusable ASID

CMN_303I CMNSTART Initialization Complete

CMN_303I Scheduled job member submitted {member} {package}

CMN_304I CMNSERVR - Calendar shifting problem

CMN_304W CMNSTART Calendar shifting warning {sitename} {date}

CMN_305I CMNSTART Detach U=CMNSTART,F1=DETACH,F2={subtask},@TCA={address}, @TCB={address}

CMN_306E CMNSTART Calendar shifting error

CMN_308I CMNSTART ZMF version 7.1.3

CMN_309I CMNSTART Invalid command syntax, please reenter.

CMN_310E CMNSTART CMNSTART Log full or global record problem - abend 310.

CMN_311I CMNSTART Unrecognized command, please reenter.

CMN_313I CMNSTART Termination Complete

CMN_315I CMNSTART IADS Task Attached

CMN_315I CMNSTART Reject; IADS Already Attached

CMN_315I CMNSTART HLLX address space is already active, no action taken.

CMN_316I CMNSTART IADS Task Detached

CMN_317I CMNSTART All scheduled jobs held

CMN_340I CMNSTART Loading active exits

CMN_340I {exit name} loaded

CMN_350I CMNSTART *** Warning *** DB2 CAF interface module could not be loaded - DSNALI.

CMN_350I CMNSTART *** Warning *** Missing DD Name = {ddname}

CMN_381E Scheduling error detected in subsys({subsys}) for {function}

CMN_381E Scheduled job member submitted {member} {package}

CMN_381E I/O error detected at CMNSCHED+{offset}

CMN_385I CMNINFVS Attempting INFO API Connect CMNINFAP (MVS-6.1.0) 20100517 19.17 Copyright

CMN_385I CMNSSV Attempting SSV initialization CMNSSV (MVS-7.1.0) 20100517 16.31

CMN_386I CMNINFVS Unable to load BLGYSRVR - INFO API

CMN_387I CMNINFVS INFO Connection disabled

CMN_387I CMNSSV SSV initialization failed

CMN_387I CMNSSV SSV terminated

CMN_388I CMNSSV SSV initialization complete

CMN_391I CMNIAM00 Attempting to open the I/A Dataspace.

CMN_392I CMNIAM00 I/A Dataspace OPEN, LDS {dsn}

CMN_393I CMNIAM00 I/A Dataspace open failed, rc {return code}, rsn {reason code}.

CMN_394I CMNIAM00 Closing the I/A Dataspace.

CMN_395I CMNIAM00 The I/A Dataspace is now offline.

CMN_400E CMNSTART Invalid Major Function= {function}

CMN_402A ATTENTION I/A dsp full | ATTENTION The impact analysis dataspace is full, reorganization is required.

CMN_403A I/A dsp full | The current I/A operation must be terminated, ABENDU0937.

CMN_460I CMNDELAY - START of processing

CMN_461I CMNDELAY - END of processing {trancnt}

CMN_464I CMNDELAY - {package} {trancd} {trandata}

CMN_468I CMNDELAY - Waiting for resource => {qname rname}

CMN_469I CMNDELAY - Resource obtained successfully.

CMN_470I CMNSTART CMNDELAY is waiting for jobname,asid,system {jobname} {asid} {smfid}

CMN_476I CMNSTART Delay file processing started

CMN_477I CMNSTART Delay file processing already in progress

CMN_478I CMNSTART Delay file processing complete

CMN_480I CMNSTART Waiting for HLL exit address space to initialize.

CMN_481I CMNSTART Successfully connected to HLL exit address space.

CMN_482I CMNSTART Termination of HLL exit address space requested.

CMN_483I CMNSTART Termination of HLL exit address space complete.

CMN_484I CMNSTART Nothing heard from HLLX, unilateral termination.

CMN_485I CMNSTART HLLX active exit table has been reloaded.

CMN_486I CMNSTART No active HLLX exits are defined, HLLX will shut down.

CMN_487I CMNSTART Please issue ATTACH HLLX command or restart ZMF if you wish to re-activate one or more exits.

CMN_488I CMNSTART Prior instance of HLLX still active, please try later.

CMN_489I CMNSTART HLL exit address space creation failed.

CMN_490I CMNSTART HLL exit address space failed to initialize, re-attempt via ATTACH command.

CMN_491I CMNSTART There are currently no active HLL exits.

CMN_492I CMNSTART Displays a set of messages identifying each active HLLX exit.

CMN_493I CMNSTART End of HLLX active exits list.

CMN_494I CMNSTART IntName Typ Env External Name Debug Ids

CMN_495I CMNSTART {intname} STD {env} {external name}

CMN_496I CMNSTART {intname} DBG {env} {external name} {debug ids}

`CMN_000I` `CMNENTFY Error - Port or IP address not found`

`CMN_000I` `CMNENTFY Error - Event Notification Task Exiting`

`CMN_004I` `CMNENTFY Port {``nnnnnn``} IP address {``iiiiii``}`

`CMN_204I` `CMN Unable to allocate JCL file to submit {``site position``}`

`CMN_208I` `CMN Member {``member``} not found`

`CMN_300` `Attach Failure`

`CMN_300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=ELDS,@TCA={``address``},@TCB={``address``}`

`CMN_300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=IADS,@TCA={``address``},@TCB={``address``}`

`CMN_300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=INFO,@TCA={``address``},@TCB={``address``}`

`CMN_300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=SERVDLAY,@TCA={``address``},@TCB={``address``}`

`CMN_300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=SSV,@TCA={``address``},@TCB={``address``}`

`CMN_300I CMNSTART Initialization in progress; @TCA={``address``}`

`CMN_301I` `Loading CMN services; @ADR={``address``}`

`CMN_302I` `CMNSTART ERO has been disabled Server started with reusable ASID`

`CMN_303I` `CMNSTART Initialization Complete`

`CMN_303I Scheduled job member submitted {``member``} {``package``}`

`CMN_304I` `CMNSERVR - Calendar shifting problem`

`CMN_304W` `CMNSTART Calendar shifting warning {``sitename``} {``date``}`

`CMN_305I` `CMNSTART Detach U=CMNSTART,F1=DETACH,F2={``subtask``},@TCA={``address``}, @TCB={``address``}`

`CMN_306E` `CMNSTART Calendar shifting error`

`CMN_308I` `CMNSTART ZMF version 7.1.3`

`CMN_309I` `CMNSTART Invalid command syntax, please reenter.`

`CMN_310E` `CMNSTART CMNSTART Log full or global record problem - abend 310.`

`CMN_311I` `CMNSTART Unrecognized command, please reenter.`

`CMN_313I` `CMNSTART Termination Complete`

`CMN_315I` `CMNSTART IADS Task Attached`

`CMN_315I CMNSTART Reject; IADS Already Attached`

`CMN_315I CMNSTART HLLX address space is already active, no action taken.`

`CMN_316I` `CMNSTART IADS Task Detached`

`CMN_317I` `CMNSTART All scheduled jobs held`

`CMN_340I CMNSTART Loading active exits`

`CMN_340I {``exit name``} loaded`

`CMN_350I` `CMNSTART * Warning * DB2 CAF interface module could not be loaded - DSNALI.`

`CMN_350I CMNSTART * Warning * Missing DD Name = {``ddname``}`

`CMN_381E` `Scheduling error detected in subsys({``subsys``}) for {``function``}`

`CMN_381E Scheduled job member submitted {``member``} {``package``}`

`CMN_381E I/O error detected at CMNSCHED+{``offset``}`

`CMN_385I` `CMNINFVS Attempting INFO API Connect CMNINFAP (MVS-6.1.0) 20100517 19.17 Copyright`

`CMN_385I CMNSSV Attempting SSV initialization CMNSSV (MVS-7.1.0) 20100517 16.31`

`CMN_386I` `CMNINFVS Unable to load BLGYSRVR - INFO API`

`CMN_387I` `CMNINFVS INFO Connection disabled`

`CMN_387I CMNSSV SSV initialization failed`

`CMN_387I CMNSSV SSV terminated`

`CMN_388I CMNSSV SSV initialization complete`

`CMN_391I` `CMNIAM00 Attempting to open the I/A Dataspace.`

`CMN_392I` `CMNIAM00 I/A Dataspace OPEN, LDS {``dsn``}`

`CMN_393I` `CMNIAM00 I/A Dataspace open failed, rc {``return code``}, rsn {``reason code``}.`

`CMN_394I` `CMNIAM00 Closing the I/A Dataspace.`

`CMN_395I` `CMNIAM00 The I/A Dataspace is now offline.`

`CMN_400E` `CMNSTART Invalid Major Function= {``function``}`

`CMN_402A` `ATTENTION I/A dsp full | ATTENTION The impact analysis dataspace is full, reorganization is required.`

`CMN_403A` `I/A dsp full | The current I/A operation must be terminated, ABENDU0937.`

`CMN_460I` `CMNDELAY - START of processing`

`CMN_461I` `CMNDELAY - END of processing {``trancnt``}`

`CMN_464I CMNDELAY - {``package``} {``trancd``} {``trandata``}`

`CMN_468I` `CMNDELAY - Waiting for resource => {``qname rname``}`

`CMN_469I` `CMNDELAY - Resource obtained successfully.`

`CMN_470I` `CMNSTART CMNDELAY is waiting for jobname,asid,system {``jobname``} {``asid``} {``smfid``}`

`CMN_476I` `CMNSTART Delay file processing started`

`CMN_477I` `CMNSTART Delay file processing already in progress`

`CMN_478I` `CMNSTART Delay file processing complete`

`CMN_480I` `CMNSTART Waiting for HLL exit address space to initialize.`

`CMN_481I` `CMNSTART Successfully connected to HLL exit address space.`

`CMN_482I` `CMNSTART Termination of HLL exit address space requested`.

`CMN_483I` `CMNSTART Termination of HLL exit address space complete.`

`CMN_484I` `CMNSTART Nothing heard from HLLX, unilateral termination.`

`CMN_485I` `CMNSTART HLLX active exit table has been reloaded.`

`CMN_486I` `CMNSTART No active HLLX exits are defined, HLLX will shut down.`

`CMN_487I` `CMNSTART Please issue ATTACH HLLX command or restart ZMF if you wish to re-activate one or more exits.`

`CMN_488I` `CMNSTART Prior instance of HLLX still active, please try later.`

`CMN_489I` `CMNSTART HLL exit address space creation failed.`

`CMN_490I` `CMNSTART HLL exit address space failed to initialize, re-attempt via ATTACH command.`

`CMN_491I` `CMNSTART There are currently no active HLL exits.`

`CMN_492I` `CMNSTART Displays a set of messages identifying each active HLLX exit.`

`CMN_493I` `CMNSTART End of HLLX active exits list.`

`CMN_494I` `CMNSTART IntName Typ Env External Name Debug Ids`

`CMN_495I` `CMNSTART {``intname``} STD {``env``} {``external name``}`

`CMN_496I` `CMNSTART {``intname``} DBG {``env``} {``external name``} {``debug ids``}`

`CMN_497I` `CMNSTART No active HLL exits are defined, the HLLX address space will not be started.`

`CMN_498I` `CMNSTART The HLLX started task is not active, No action taken or required.`