DIF messages - syncsort_cobol_migration_manager - syncsort_clone_center - syncsort_space_recovery_system - syncsort_scc_monitor - syncsort_simulate_2000 - syncsort_allocation_control_center

DIF00100 RELEASE n.n.n OF THE DYNAMIC INSTALL FACILITY HAS BEEN STARTED ON day date AT time

Explanation: The Dynamic Install Facility (DIF) displays this message during initialization. DIF is the started task that installs all products. This message will also display the current version of DIF: n.n.n.

Message Level: I

Response: None

DIF00101 START OPTIONS: options

Explanation: This message echoes the parameters specified on the EXEC statement in the DIF started task. This message is written to the SYSPRINT DD statement found in DIF.

Message Level: I

Response: None

DIF00103 ddname COULD NOT BE OPENED

Explanation: DIF failed to open one of the required DD statements in the DIF started task: SYSPRINT, STEPLIB, and PARMLIB.

Message Level: E

Response: The SYSPRINT, STEPLIB, and PARMLIB DD statements are required. For more information, examine “DIF Overview” on page 6-1 in the SCC Product Installation Guide.

DIF00104 ANOTHER DYNAMIC INSTALL JOB IS ACTIVE FOR subsys

Explanation: Multiple copies of DIF can be active at the same time. Each copy can use a separate subsystem, or all DIF started tasks can share the same subsystem. By default, DIF uses DT71 as the subsystem name, but the SUBSYS DIF parameter can be used to specify the subsystem name.

During initialization, the Dynamic Install Facility found another version of DIF using the same subsystem. To avoid unintended execution of multiple DIF started tasks, this warning message informs your operators that another version using the same subsystem is active.

Message Level: I

Response: DIF issues message DIF00108 to prompt the operator to complete start processing. If the operator determines that multiple DIF are allowed in your environment, the operator should reply “YES”. All other responses will terminate the starting DIF.

DIF00105 COLD START IGNORED

Explanation: Multiple copies of DIF can be active at the same time. Each copy can use a separate subsystem, or all DIF started tasks can share the same subsystem. The COLD=YES operand was specified in the DIF EXEC parameter field.

During initialization, the Dynamic Install Facility found another version of DIF using the same subsystem. A cold start cannot be performed to establish new subsystem control blocks. If allowed, the other copies using the same subsystem name would be corrupted. The cold start is denied.

Message Level: I

Response: If a cold start is required, terminate all versions of DIF using the same subsystem name.

DIF00106 DYNAMIC INSTALL FACILITY IS NOT AUTHORIZED

Explanation: The Dynamic Install Facility performs many functions that are considered “privileged” by the operating system. During DIF initialization, a TESTAUTH request was used to determine that DIF was not running authorized.

Message Level: E

Response: Ensure that the DIF load modules are linked into an authorized load library. For the list of authorized data sets on your system, examine SYS1.PARMLIB(IEAAPFnn). DIF0000 must be linked with the AC(1) to establish authorization. Also, all data sets allocated to the DIF STEPLIB DD statement must be authorized libraries. If any non-authorized data set is concatenated to STEPLIB, the authorization will be removed.

DIF00107 OPSYS(sysrel) FMID(fmid) VERSION(ver) DFPREL(X’dfprel’) SMSREL(X’smsrel’)

Explanation: The Dynamic Install Facility (DIF) displays this message during initialization. This message documents the current OS environment. The message is written to the SYSPRINT DD statement found in DIF.

Message Level: I

Response: None

DIF00108 ENTER YES TO CONTINUE START

Explanation: Multiple copies of DIF can be active at the same time. Each copy can use a separate subsystem, or all DIF started tasks can share the same subsystem. By default, DIF uses DT71 as the subsystem name, but the SUBSYS DIF parameter can be used to specify the subsystem name.

During initialization, the Dynamic Install Facility found another version of DIF using the same subsystem. To avoid unintended execution of multiple DIF started tasks, the DIF00104 warning message informs your operators that another version using the same subsystem is active. DIF issues message DIF00108 to prompt the operator to complete start processing.

Message Level: R

Response: If the operator determines that multiple DIF are allowed in your environment, the operator should reply “YES”. All other responses will terminate the starting DIF.

DIF00109 SUBSYS COMMAND CHARACTER cmdchar IS ALREADY IN USE

Explanation: The CMDCHAR parameter on the DIF EXEC statement specifies the character used by your installation: cmdchar. However, the command character is already being used by another subsystem. On MVS systems, the “D OPDATA” console command can be used to list the command character used by each subsystem. For more information, examine “DIF Commands from the Operator Console” on page 5-7 in the Rules Language Programming Guide.

Message Level: E

Response: DIF has started without activating the requested command character, but you can still use the Modify

(F) form of command input. Please select another command character for the CMDCHAR parameter on the DIF EXEC statement. However, the new command character cannot be used until a DIF restart is performed.

DIF00150 READY FOR MODIFY COMMANDS OR USE cmdchar

Explanation: DIF has completed installation. The DIF subsystem can now accept console commands. Commands can be entered with the Modify (F) command, or by using the subsystem command character: cmdchar.

Message Level: I

Response: The Modify (F) form of entering commands looks similar to the way VTAM commands are entered. The following STATUS command uses the Modify

(F) form of command input.

F DIF,STATUS

The pound (#) character is the default subsystem command character used by DIF. The CMDCHAR parameter on the DIF EXEC statement specifies the character used by your installation: cmdchar. The following example assumes the pound (#) character is the subsystem character used by DIF. The following STATUS command uses the subsystem form of command entry.

#STATUS

DIF00151 OPERATOR STOP COMMAND NOT SUPPORTED. USE DIF Z OR SHUTDOWN COMMAND

Explanation: A DIF initialization parameter (PCMD) allows installations to specify how a P DIF command should be treated. The default, PCMD=NONE will not allow DIF to be terminated with a P DIF command. If a P DIF is performed, operators will receive this message.

PCMD=SHUTDOWN will terminate DIF and all products started by DIF. PCMD=Z will terminate DIF but leave the products installed.

Message Level: E

Response: For more information, examine “DIF - PARM Information” on page 6-7 in the Product Installation Guide.

DIF00152 RACF SECURITY ERROR - RC=src-rrc

Explanation: During DIF command processing, a security token was received from the operating system with the command request. DIF attempted to use the token on a RACROUTE request to create a security environment for the command. The RACROUTE failed with a SAF return code (src) and RACF return code (rrc) which are displayed in the message.

Note: In Top Secret installations, this message is usually accompanied by a TSS7100E message. It's not clear what circumstances cause Top Secret to fail the request and issue the TSS message. Since there is no impact, the message can be bypassed by adding the following statement to the START00 member in the DIF parmlib.

MSG DIF00152 SKIP ON

Message Level: E

Response: For more information about the RACROUTE return codes, examine the return codes for the RACROUTE REQUEST=VERIFY (standard form) in the OS/ 390 Security Server External Security Interface (RACROUTE) Macro Reference IBM manual (GC28-1922).

DIF00200 OPSYS VALUE IS NOT VALID

Explanation: During DIF initialization, keywords can be passed to DIF via the parameter field on the DIF EXEC statement. The OPSYS keyword was specified but did not contain a valid OPSYS parameter.

Message Level: E

Response: For more information, examine “DIF - PARM Information” on page 6-7 in the Product Installation Guide.

DIF00310 SUBSYSTEM DOES NOT POINT TO A VALID DCVT

Explanation: During initialization, DIF attempts to locate any existing DIF subsystem control blocks. The SUBSYS parameter field on the DIF EXEC statement defines the name of the DIF subsystem and defaults to DT71. DIF located the subsystem control blocks, but the control blocks did not belong to DIF.

Message Level: C

Response: An invalid subsystem name has been specified on the SUBSYS parameter. If SUBSYS was not specified, contact Customer support.

DIF00311 DIF LEVEL HAS CHANGED - COLD START REQUIRED

Explanation: The DIF being started is at a higher version than the DIF that created the subsystem control blocks. To accommodate the changes that may have been made to DIF, a cold start is required. This will force DIF to rebuild the subsystem control blocks.

Message Level: C

Response: To start DIF with the cold start parameter, enter the following command:

START DIF,’COLD=YES’

DIF00312 ENF CALL FAILED - RC = X’rc’

Explanation: DIF uses the Event Notification Facility (ENF) to determine whether a device has come online, or gone offline. This facility allows DIF to perform automatic refresh commands on products that use device lists.

The call to ENF failed.

Message Level: E

Response: Please contact Customer support.

DIF00313 LICENSED FOR COMPANY NAME: company-name

Explanation: When DIF starts, this message displays the company-name that has licensed the product, or is in the process of performing a product trial.

Message Level: None

Response: None

DIF00314 LICENSED FOR LOCATION: location

Explanation: When DIF starts, this message displays the company location that has licensed the product, or is in the process of performing a product trial.

Message Level: None

Response: None

DIF00315 CPU INFORMATION: CPUID(cpuid)

TYPE(cputype) MODEL(cpumodel)

Explanation: When DIF starts, this message displays the last five digits of the CPUID, the CPU type, and model information.

Message Level: None

Response: None

DIF00316 LICENSE MEMBER IN DIF PARMLIB IS NOT VALID

Explanation: The LICENSE member in DIF PARMLIB does not conform to the new license key format used in SCC

7.1. Starting with release 5.1, a new algorithm was developed to replace the original. All Product and customer information is now encrypted into a single self-signed license key. The key is much larger and more robust than the original license keys.

Message Level: C

Response: Please contact your sales representative to obtain a new license key for your organization.

DIF00330 SYSTEM DOES NOT SUPPORT NEW JCL

Explanation: DIF can dynamically add new parameters to JCL statements on MVS/ESA and OS/390 systems using an operating system facility called SJF. The product has requested new parameters for JCL statements, but DIF has found that the operating system doe not support the SJF facility.

Message Level: E

Response: None

DIF00331 JCL TABLE NOT CORRECT FORMAT

Explanation: DIF can dynamically add new parameters to JCL statements on MVS/ESA and OS/390 systems using an operating system facility called SJF. The product has requested new parameters for JCL statements, but DIF has found that the new table format does not match the existing table format.

Message Level: E

Response: Please contact Customer support.

DIF00332 JCL DEFINE FAILED - RC=X’rc’

Explanation: DIF can dynamically add new parameters to JCL statements on MVS/ESA and OS/390 systems using an operating system facility called SJF. The product has requested new parameters for JCL statements, but DIF failed on the call to the system interface module for SJF.

Message Level: E

Response: Please contact Customer support.

DIF00361 COLD START SPECIFIED BUT PRODUCTS ARE ACTIVE

Explanation: During DIF initialization, keywords can be passed to DIF via the parameter field on the DIF EXEC statement. The COLD=YES keyword was specified, but DIF has active products. DIF00362 prompted the operator to validate the cold start request, and the operator denied the request.

Message Level: A

Response: For more information, examine “DIF - PARM Information” on page 6-7 in the Product Installation Guide.

DIF00362 ENTER YES TO CONTINUE WITH COLD START

Explanation: During DIF initialization, keywords can be passed to DIF via the parameter field on the DIF EXEC statement. The COLD=YES keyword was specified, but DIF has active products. This message is followed by DIF00362, asking the operator to validate the cold start request.

Message Level: A

Response: For more information, examine “DIF - PARM Information” on page 6-7 in the Product Installation Guide.

DIF00370 DIF SVC TABLE IS FULL

Explanation: During DIF initialization, keywords can be passed to DIF via the parameter field on the DIF EXEC statement. The COLD=YES keyword was specified, but DIF has active products. This message prompts the operator to validate the cold start request.

Message Level: R

Response: For more information, examine “DIF - PARM Information” on page 6-7 in the Product Installation Guide.

DIF00370 DIF SVC TABLE IS FULL

Explanation: DIF also installs a dynamic SVC facility for use by products. This facility works like the Extended Router SVCs. If no SVC operand is specified in the DIF parameter field, DIF scans the SVC table for an unused SVC number. After installing the SVC, a console message displays the new SVC number selected by DIF - message DIF10130.

The dynamic SVC facility can only be used by authorized users. All programs that use the SVC facility must be registered with the DIF dynamic SVC interface. Control will immediately be returned to any program issuing the SVC which has not registered with the DIF dynamic SVC interface. Unfortunately, the DIF SVC registration table is full.

Message Level: C

Response: Please contact Customer support.

DIF00703 option REQUIRES THAT product BE ACTIVE

Explanation: The ENABLE OPTION command was used in an attempt to activate an option for the product.

Options can only be activated if the product has been successfully started.

Message Level: E

Response: Ensure that the product has been started before the option is activated with the ENABLE OPTION command.

DIF00704 PRODUCT TABLE FOR product COULD NOT BE CREATED

Explanation: During START processing, DIF builds a control block for the product in CSA. DIF could not successfully build the control block. A message preceding DIF00704 contains the reason for failure.

Message Level: E

Response: Examine the DIF message that precedes DIF00704.

DIF00750 FILE filename(ddname) IS NOW CLOSED

DIF01041 product NOT DORMANT - WAITING FOR PRODUCT LOCK

Explanation: During STOP product processing, DIF uses locks to protect running jobs from synchronization problems caused by product termination. One or more jobs are currently performing tasks that do not allow DIF to STOP the product. As soon as the product releases the lock, DIF will be allowed to complete processing.

Note: This message can be caused by jobs waiting for outstanding tape mounts, or locks that are held by initiators that took an abend. Wait for tape mounts to complete, or try stopping and restarting initiators to free the lock.

Message Level: I

Response: Message DIF01042 usually accompanies this message. If the product lock has not been automatically released within one minute, reply with INACT. This will terminate the current STOP command to allow DIF console command processing, and mark the product as INACTIVE. Then contact Customer support. Note: If the STOP request is being performed as part of a DIF SHUTDOWN command, the product will be marked as INACTIVE and shutdown processing will proceed.

DIF01042 REPLY 'INACT' OR 'FORCE'. TO CONTINUE WAITING, DO NOT REPLY

Explanation: During STOP product processing, DIF uses locks to protect running jobs from synchronization problems caused by product termination. One or more jobs are currently performing tasks that do not allow DIF to STOP the product.

INACT will mark the product as INACTIVE and terminate the current STOP command to allow DIF console command processing. The job(s) that held the lock can complete normally, but without using the services provided by the product.

Note: If the STOP request is being performed as part of a DIF SHUTDOWN command, the product will be marked as INACTIVE and shutdown processing will proceed.

Issue FORCE to force DIF to ignore the product lock. Since this request could lead to abends for jobs that hold the lock, you should only issue FORCE when recommended by Customer support.

Message Level: I

Response: If the product lock has not been automatically released within one minute, reply with INACT. This will terminate the current STOP command to allow DIF console command processing, and mark the product as INACTIVE. Then contact Customer support. Note: If the STOP request is being performed as part of a DIF SHUTDOWN command, the product will be marked as INACTIVE and shutdown processing will proceed.

DIF01043 OPERATOR CANCELED WAIT

Response: Use a valid SYSVAR number: 1-5

DIF01421 SYSVAR num = text

Explanation: The DIF SYSVAR command allows operators to communicate with the rules language. SYSVAR sets a symbolic field that can be accessed by rules statements. All products that use the rules language have access to five SYSVAR symbolic fields: SYSVAR1-5. Each symbolic field is a 50-byte character field.

Explanation: The SYSPCMD command can be used to route a DIF command to all DIF started tasks running in a sysplex.

The DIF SYSPCMD command was issued, and each system in the sysplex that is running a DIF started task returns messages. This message is used to display the response from a member of the sysplex. Note: The response message(s) should be preceded by a DIF01532 message that contains the

sysplex-member name. Message Level: I Response: None

DIF01540 DIF VERSION n.n.n RUNNING ON sysid

Explanation: The DIF VERSION command was issued by the operator or by the startup member. The command displays the current DIF version executing (n.n.n) and the sysid of the current OS. Note: Use the DIF Status or SL command to obtain the release information about each product running under DIF.

Message Level: I

Response: None

DIF01560 RULE TRACE IS status FOR product - JOB(jobname) FILTER(filter)

Note: The dynamic SVC facility can only be used by authorized users. Control will immediately be returned to any program issuing the SVC which has not registered with the DIF dynamic SVC interface.

Message Level: A

Response: None

DIF10131 SVC NUMBER COULD NOT BE CREATED

Explanation: During DIF initialization, DIF attempted to install the dynamic SVC facility. DIF scanned for an empty slot in the SVC table, but no empty slot could be found. products use the facility like the Extended Router SVCs.

Message Level: E

Response: Please contact Customer support.

Explanation: During DIF START or DM command processing, load module text records must be read from the ddname found in the JCL for the DIF started task. The loadmod could not be found in the requested ddname.

DIF10302 MODIFICATION CONTINUES DUE TO NOVERIFY OPTION

Explanation: During DIF START processing, the install facility determines the locations in the operating system that require modification. DIF validates all modifications before attempting any modification. At least one validation failed.

Examine the associated DIF10300 messages for the location of the problem. Since VERIFY OFF was requested with the DIF SET command, start processing will continue.

Explanation: During DIF STOP processing, the install facility determines the locations in the operating system that require modification. DIF validates all modifications before attempting any modification. At least one validation failed. Examine the associated DIF11110 messages for the location of the problem. Since VERIFY OFF was requested with the DIF SET command, stop processing will continue.

Note: Only use the VERIFY OFF option when requested by Customer support.

Message Level: A

Response: Another product has been dynamically installed onto the same location in the system. The VERIFY OFF request probably removed the other product during termination. The other product may have an “active” status, but an operating system modification has been removed. The product is probably in a semi-functional state. WARNING: Bringing down the other product after performing a stop with VERIFY OFF will probably corrupt your system.

DIF11113 VALIDATION FAILED AT loadmod.csect+X’offset’ VADDR(address)

Explanation: During DIF STOP processing, the install facility determines the locations in the operating system that require modification (loamod.csect+X’offset’). DIF examines the data at this location for expected values. This validation process failed.

Conditional stop processing has been enabled. This message is preceded by DIF11114. STOP processing will leave the failing hook module in place, and continue removing the other system hooks made by the product.

Note: This message is only displayed in the DIF SYSPRINT DD statement.

Message Level: E

Response: Another product has been dynamically installed onto the same location in the system. The other product will have to be removed before this product can be terminated.

DIF11114 ONE OR MORE HOOKS NOT REMOVED BUT MARKED INACTIVE

Explanation: Conditional stop processing has been enabled. DIF11113 will also be displayed in the DIF SYSPRINT DD statement and contains the name of the module failing validation.

STOP processing will leave the failing hook module in place, and continue removing the other system hooks made by the product.

Message Level: A

Response: Another product has been dynamically installed onto the same location in the system. The other product will have to be removed before this product can be terminated.

DIF11115 DATA AT INDIRECT ADDRESS vconaddr-->hookmod:

Explanation: During DIF STOP processing, the install facility determines the locations in the operating system that require modification. DIF validates all modifications before attempting any modification. The DIF shutdown routines found another product module at the address hookmod installed. Another product was dynamically installed after the DTS product was started. The DIF11115 message displays the address of the VCON pointing to the product module. DIF writes the DIF11115 and DIF11116 messages to the DIF SYSPRINT file to display the first 64 characters of the module.

Message Level: I

Response: Please contact Customer support.

DIF11116 hex1 hex2 hex3 hex4 eyecatcher

Explanation: During DIF STOP processing, the install facility determines the locations in the operating system that require modification. DIF validates all modifications before attempting any modification. The DIF shutdown routines found another product module at the address hookmod installed. Another product was dynamically installed after the DTS product was started. The DIF11115 message displays the address of the VCON pointing to the product module. DIF writes the DIF11115 and DIF11116 messages to the DIF SYSPRINT file. The DIF11116 messages display the first 64 characters of the module.

Message Level: I

Response: Please contact Customer support.

DIF11200 STORAGE MODIFICATION AT ADDRESS vaddress FAILED

Explanation: When DIF performs a product START or STOP request, DIF adds or removes hooks from the operating system. The modifications are documented in the DIF SYSPRINT DD statement.

DIF performs validation tests on all proposed changes to the OS to ensure system integrity. When DTS products are started, the DIF started task builds a table that contains all the storage modifications that WILL be required to start the product. After loading the DTS product software into system memory, the product then uses the table to verify that all the locations DIF is about to change have the expected values. The same storage modification table is later used for shutdown processing.

When stop processing is requested, DIF again validates that all the expected values are found in memory. Start and stop processing occurs only after all checks have passed validation.

After performing a memory change, DIF also verifies that the memory change was successfully applied to the system. If the expected value is not in memory after DIF attempts the memory modification, the DIF11200 message is written to the operator console.

If the error occurs during start processing, the product rolls back the modifications already made by the start request and unloads the DTS product modules. The start is not performed. If the storage modification error occurs during shutdown, DIF marks the product as inactive and leaves the DTS product hooks in place. The inactive DTS hooks immediately pass control through to the IBM modules.

Message Level: C

Response: Please save the output from the DIF SYSPRINT DD statement and contact Customer support.

DIF20020 ISPLINK FAILED FOR function - RC=rc

Explanation: DIF message services made a function request to ISPLINK, but the request failed with a return code rc.

Message Level: E

Response: Please contact Customer support.

DIF20030 product:ESTAE FAILED - RC=X’rc’

Explanation: The product attempted to establish an ESTAE routine. The ESTAE request received a return code: rc.

Message Level: E

Response: Please contact Customer support.

DIF20031 product:ESTAE ESTABLISHED

Explanation: The product succeeded in establishing an ESTAE routine. This message is only produced when CSRLOG=n is specified for DIF processing, or the DDLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Log Level: 4

Message Level: None

Response: None

DIF20032 product:ESTAE CANCELLED

Explanation: The product succeeded in canceling an ESTAE routine. This message is only produced when CSRLOG=n is specified for DIF processing, or the DDLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Log Level: 4

Message Level: None

Response: None

DIF20032 ESTAE Recovery Terminated

Explanation: The product abended, and the parameter block to the ESTAE recovery routine was not available (SDWA). The recovery was terminated.

Message Level: C

Response: Please contact Customer support.

DIF20041 RECURSIVE ABEND IN product

Explanation: The product abended, and the ESTAE recovery routine passed control to the product’s retry routine. Since another abend occurred, the recovery routine terminates to keep from looping.

Message Level: C

Response: Please contact Customer support.

DIF20042 SYSTEM code ABEND OCCURRED AT OFFSET X’offset’ IN MODULE modname

Explanation: An abend occurred in a module: modname. The system abend code and module offset are also displayed in the message. Processing will terminate, and control will be returned to the operating system function that the product is frontending. If the product is not essential to the success of the job, the job may run to successful completion.

If the offset displays question marks (????????), the modname has passed control to an operating system routine, and the abend occurred outside the product’s executable code. The name of the associated operating system routine is displayed in message DIF20480.

Message Level: C

Response: Please contact Customer support.

DIF20043 PSW AT ABEND psw

Explanation: An abend occurred in a module. The modname, system abend code, and module offset are displayed in message DIF20042. DIF20043 displays the PSW at abend. Processing will terminate, and control will be returned to the operating system function that the product is frontending. If the product is not essential to the success of the job, the job may run to successful completion.

Message Level: C

Response: Please contact Customer support.

DIF20044 REGS (n-n)

Explanation: An abend occurred in a module. The modname, system abend code, and module offset are displayed in message DIF20042. DIF20044 displays the registers at abend. Processing will terminate, and control will be returned to the operating system function that the product is frontending. If the product is not essential to the success of the job, the job may run to successful completion.

Message Level: C

Response: Please contact Customer support.

Explanation: A product has requested that a common service routine call the SYSEVENT SVC. The request was successful. The message describes the SYSEVENT requested (nn), and the value of register 1 when the SVC was issued - reg1.

This message is only produced when CSRLOG=n is specified for DIF processing, or the DDLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Explanation: The Common Service Routine (CSR) for ATTACH has been called to execute a load module (modname). The message describes the type of attach being requested (req), and the return code from the attach (rc).

This message is only produced when CSRLOG=n is specified for DIF processing, or the DDLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Log Level: 8

Message Level: None

Response: None

DIF20200 DETACH FOR req:MODULE mod-name TCB(address), RC=X’rc’

Explanation: The Common Service Routine (CSR) for DETACH has been called to remove a load module (modname). The message also describes the type of detach being requested (req), the address of the TCB, and the return code from the detach (rc).

This message is only produced when CSRLOG=n is specified for DIF processing, or the DDLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Log Level: 8

Message Level: None

Response: None

DIF20210 LINK FAILED FOR req - MODULE modname RC=X’rc’

Explanation: A module has requested that a common service routine LINK to a load module (modname). The load module received a return code (rc). The message also describes the type of module required (req).

Message Level: E

Response: Please contact Customer support.

DIF20212 LINK FOR req:MODULE modname RC=X’rc’, R0=X’r0’, R1=X’r1’

Explanation: The Common Service Routine (CSR) for LINK has been called to execute a load module (modname). The message describes the type of link being requested (req) and the return code from the link (rc). r0 and r1 are also displayed

This message is only produced when CSRLOG=n is specified for DIF processing, or the DDLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Explanation: A module has requested that a common service routine ENQ on a resource. The qname, rname, and length of the rname (rlen) are displayed at the start of the message. The use field displays whether the ENQ is SHR or EXC. The scope and ret values are also displayed. If this enqueue is actually a RESERVE request for a DASD volume, the name of the vol will be displayed in the message.

This message is only produced when CSRLOG=n is specified for DIF processing, or the DDLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Log Level: 8

Message Level: None

Response: None

DIF20321 ENQ FOR QNAME(qname) RNAME(rname) RC=’rc’

Explanation: A module has requested that a common service routine ENQ on a resource. The qname and rname of the request are displayed along with the return code received from the enqueue (rc).

This message is only produced when CSRLOG=n is specified for DIF processing, or the DDLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Log Level: 8

Message Level: None

Response: None

DIF20330 DEQ FOR QNAME(qname) RNAME(rname)/rlen use scope RET=ret VOLUME(vol)

Explanation: A module has requested that a common service routine DEQ on a resource. The qname, rname, and length of the rname (rlen) are displayed at the start of the message. The use field displays whether the ENQ is SHR or EXC. The scope and ret values are also displayed. If this dequeue is actually releasing a RESERVE on a DASD volume, the name of the vol will be displayed in the message.

This message is only produced when CSRLOG=n is specified for DIF processing, or the DDLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Log Level: 8

Message Level: None

Response: None

DIF20331 DEQ FOR QNAME(qname) RNAME(rname) RC=’rc’

Explanation: A module has requested that a common service routine DEQ on a resource. The qname and rname of the request are displayed along with the return code received from the dequeue (rc).

This message is only produced when CSRLOG=n is specified for DIF processing, or the DDLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Log Level: 8

Message Level: None

Response: None

DIF20350 PLPA/SEGMENT PROTECTION reqtype FOR A(address) LEN(length)

Explanation: The product is attempting to bypass PLPA or SEGMENT protection to perform product installation.

Protection is removed from the page(s) or segment(s), the modifications are made, and then protection is restored. The message will display the reqtype: ENABLE or DISABLE. Also, the address and length of the storage being modified are displayed. If the modification crosses a page or segment, DIF will work with multiple page or segment entries.

This message is only produced when CSRLOG=n is specified for DIF processing. Messages are written to the SYSPRINT DD statement.

Explanation: The Common Service Routine (CSR) for managing MLPA CDE entries has been called. This message displays the cmdtype (MOD, ADD, or DEL) and module name, followed by the address of the MLPA CDE entry, the module entry point, and the address of the DIF GMT entry for the module. This message is typically written to the CSRLOG.

This message is only produced when CSRLOG=n is specified for DIF processing, or the DDLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Log Level: 8

Message Level: None

Response: None

DIF20610 DEVICE SWAP REFRESH DEVN=oucb/nucb ovol/nvol

Explanation: The DIF started task contains an Event Notification Facility (ENF) listening routine to monitor devices going on-line, off-line, or being swapped. DTS products that contain device pools in the rule definitions can be automatically refreshed when the DIF ENF listen routine encounters a status change for a device used by a product’s pool definition(s). When a rule refresh is required for a device swap, the ENF routine issues a DIF20610 message displaying the old/new UCBs for the swap. The volume names mounted on the old/new UCBs are also displayed.

Explanation: A product has requested that a common service routine locate a rule member. The calling function can also request a log message containing trace fields passed to the rules routine. Typically, the trace fields contain the environment name and the statement making the rules request. The message will only be produced if rules tracing has been enabled.

Message Level: None

Response: None

DIF20710 ENTERING stmt: rulename.#

Explanation: The product’s TRACE DD statement has been specified. This DD statement requested that rules tracing be used when scanning the rules language. This message specifies the name of the DEFRULE, DEFPROC, or DO-END statement being entered. Note: Since DO-END statements do not have associated names, the product generates an internal statement name.

Since the DEFRULE, DEFPROC, and DO-END statements can contain multiple IF-THEN-ELSE groups, this message will be produced as each group is entered. The number of each IF-THEN-ELSE group is also displayed.

Message Level: None

Response: None

DIF20730 FIELD UPDATE FAILED FOR fldname - RC=rc

Explanation: The rules conversion process uses the private region in the DIF started task for conversion. A rules conversion buffer was insufficient to convert the rules definition statements. If the conversion process had been successful, the rules would have been moved into extended CSA.

Message Level: E

Response: The DIF SET command can be used to provide a larger conversion buffer for the internal table. By default, the rules compiler allocates 6 kilobytes for the global LLE table. The following command could be used to increase the buffer for ACC to 12 kilobytes. If you still have problems, please contact Customer support.

F DIF,SET ACC RLLEBUF 12

DIF2080C field CANNOT BE SPECIFIED TWICE

Explanation: An internal parse routine detected an error. The field name, or subparameter using the field, cannot be specified twice in the input stream.

Message Level: E

Response: Please examine the command or control card being parsed for a parameter specified twice on the control card or command. Please specify the subparameter only once.

Explanation: A module has requested that a common service routine issue an EXCP to ucb volume volser. The ucb address, ccw, ecb, and timeout information are also displayed. The IO request failed.

Log Level: E

Response: Please contact Customer support.

DIF20970 ENTERING POOL: poolname FOR VOLUME volser - ucb

Explanation: The product’s TRACE DD statement has been specified. This DD statement requested that rules tracing be used when scanning the rules language. When the current pool definition contains expressions that must be evaluated at run-time, DIF20970 is displayed for the candidate volume.

This message will be followed by comparison messages produced by the expressions in the pool definition. DIF20971 will then display the result of the evaluation.

Message Level: None

Response: None

DIF20971 RUN-TIME CHECKS result

Explanation: The product’s TRACE DD statement has been specified. This DD statement requested that rules tracing be used when scanning the rules language. When the current pool definition contains expressions that must be evaluated at run-time, DIF20970 is displayed for the candidate volume.

requested a symbolic field that was not available at execution time.

NUMBER TOO LARGE FOR FIELD - The DEFREC

requested a numeric field that was available, but the number value was too large for the field in the record.

Message Level: E

Response: The field you are requesting does not exist at the time you made the request, or a number overflows the size of the field provided in the record.

DIF21051 REQUIRED FIELD NOT FOUND - DEFREC recname FIELD(fldname) (pos:len) - msg_error

Explanation: During rules execution, the DEFREC recname statement could not obtain the information for a required fldname. The position and length of the field are also displayed. The msg_error can be used to further narrow the problem accessing the field.

RUNTIME VARIABLE NOT AVAILABLE - The

DEFREC requested a symbolic field that was generated by the rules language with the DEFVAR statement. The field could not be accessed by the DEFREC statement at execution time.

SYMBOLIC FIELD NOT AVAILABLE - The DEFREC

requested a symbolic field that was not available at execution time.

NUMBER TOO LARGE FOR FIELD - The DEFREC

requested a numeric field that was available, but the number value was too large for the field in the record.

Message Level: E

Response: The field you are requesting does not exist at the time you made the request, or a number overflows the size of the field provided in the record.

DIF21060 STARTING TRACE FOR env-envs

Explanation: The product’s TRACE DD statement has been specified. This DD statement requested that rules tracing be used when scanning the rules language. This message displays the environment (env) and sub-environment when entering the rules language.

Message Level: None

Response: None

DIF21061 STARTING TRACE FOR env-envs DSN=dsname VOL=volser DDNAME=ddname

Explanation: The product’s TRACE DD statement has been specified. This DD statement requested that rules tracing be used when scanning the rules language. This message displays the environment (env), and sub-environment when entering the rules language. The current data set name, volume, and DDname are also displayed.

Message Level: None

Response: None

DIF21080 VVDS READ FOR dsname-volser

Explanation: A module has requested that a common service routine read the VVDS record for data set dsname on volume volser.

This message is only produced when CSRLOG=n is specified for DIF processing, or the DDLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Log Level: 12

Message Level: None

Response: None

DIF21100 ERROR INITIALIZING THE REXX ENVIRONMENT - RC=rc-rs

Explanation: The rules language made a CALLREXX request to execute a Rexx program. The call to IRXINIT to initialize the Rexx environment failed. The return code (rc) and reason code (rs) for the failure are returned by the DIF routine.

Message Level: E

Response: Please contact Customer support.

DIF21101 REXX RUN ERROR - RC=rc

Explanation: The rules language made a CALLREXX request to execute a Rexx program. The call to IRXEXEC to execute the Rexx program failed with a return code (rc).

Message Level: E

Response: Please contact Customer support.

DIF21200 SAF FUNCTION func RC=r15-bytes1to4-bytes5to8

Explanation: A module has requested that a common service routine call the SAF interface (ie. security calls using RACROUTE). The message displays the function requested (AUTH, CREATE or DELETE), and the return codes (r15, return code structure)

Byte: 1 SAF return code (R15 after RACROUTE) Byte: 2 Function code Byte: 3 RACROUTE return code Byte: 4 RACROUTE reason code Byte: 5-8 Internal reason code

This message is only produced when CSRLOG=n is specified for DIF processing, or the DDLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Log Level: 8

Message Level: None

Response: None

DIF21210 PIN FOR device volume / TOKEN RETURNED token

Explanation: A module has requested that a common service routine PIN the UCB for device device and volume volser. The message also displays the token value returned from the UCBPIN PIN request.

This message is only produced when CSRLOG=n is specified for DIF processing, or the DDLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Log Level: 12

Message Level: None

Response: None

DIF21211 UNPIN FOR TOKEN token

(ddname-dsname) - RC=r15-ec-ic

Explanation: A DIF service routine issued a dynamic unallocation request. The dynamic unallocation attempt failed. The RC field contains the decimal value of register 15, the hexadecimal values for the error code (ec), and the information code (ic).

Message Level: E

Response: Examine the Authorized Assembler Language Programs manual to obtain the return, error, and information codes specified in this message (GC28-1645). If the information does not help you solve the problem, contact Customer support.

DIF21261 FREE FOR DD=ddname / DSN=dsname

Explanation: A module has requested that a common service routine free a data set allocated to DD ddname.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 12.

//ACCLOG DD DUMMY,DCB=LRECL=12

Log Level: 12

Message Level: None

Response: None

DIF21320 EMC REQUEST FOR volser - RC=r15-r0

Explanation: A module has requested that a common service routine obtain information about an EMC device. This message displays the results (R15 and R0) of the EMC API call for the volser volume.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 16.

//ACCLOG DD DUMMY,DCB=LRECL=16

Log Level: 16

Message Level: None

Response: None

DIF21330 ERROR FOR GENERIC CATALOG REQUEST FOR dsname - RC=rc-rs

Explanation: A DIF service routine issued a generic catalog request to obtain information about the dsname. The request failed. The RC field contains the hexadecimal values of register 15 (rc) and the reason code (rs).

Message Level: E

Response: Please contact Customer support.

DIF21360 DSPSERV REQUEST FAILED -RC=src-srs

Explanation: A DIF service routine issued a data space services request to create or delete a data space. The request failed.

Message Level: W

Response: DIF is attempting to create a data space and can't. The OS has reached its maximum number of common data spaces. The situation will be corrected at the next IPL.

Note: This error will not affect the product’s functionality. If DIF fails in the attempt to load data into a dataspace, the product will use CSA/ECSA instead.

DIF21361 DSPSERV type FOR value

Explanation: A DIF service routine issued a data space services request to create or delete a data space. If type is GET, the value is for the number of 4K blocks. For types of GETALET and FREEALET, the value is the ALET number.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Log Level: 8

Explanation: A DCC component attempted to use the BTI channel interface to access the Bus-Tech MDL or EMC DLm. However, the pool specified to process the command request had no available units. By default, DCC selects online/unallocated units for command processing. However, the pool definitions in DLMPOOLS can be defined to allow both online and offline devices for command processing, or only offline devices.

Once a device is selected, DCC locks the device for command processing until the command completes and then releases the unit.

Message Level: E

Response: Verify that the DLMPOOLS member contains enough units in the pool definitions for the Bus-Tech MDL or EMC DLm command interface usage. For example, if there exists a possibility that all online units can be used for normal tape mount processing on jobs, consider adding additional units to the pool, or reserve units for command processing. For more information, please contact Customer support.

DIF21545 UCB ucb ucbaddr rejtype fld1 fld2 fld3 fld4 fld5

Explanation: DCC is using the BTI channel interface to access the Bus-Tech MDL or EMC DLm. This log message displays information about the command request.

This message is only produced when CSRLOG=n is specified for DIF processing, or the DCCLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using a DCC debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 30.

//DCCLOG DD DUMMY,DCB=LRECL=30

Log Level: 30

Message Level: None

Response: None

DIF21545 DTS Script Failure or Not Installed

Explanation: A DCC component attempted to use the BTI channel interface to execute a DTS script on the Bus-Tech MDL or EMC DLm. Either a script failure occurred or the DTS scripts were not installed on the DLm.

Message Level: E

Response: Please contact Customer support.

DIF21547 DTS DLM SCRIPT TIMEOUT

Explanation: A DCC component attempted to use the BTI channel interface to execute a DTS script on the Bus-Tech MDL or EMC DLm. The script did not complete execution within the time allowed on the script command request.

Message Level: E

Response: Please contact Customer support.

DIF21620 SYSPARM name KEY(key) GLOBAL(gblname) PROD(product) DATA(value)

Explanation: The Common Service Routine (CSR) for SYSPARM processing has been called to perform an obtain request for a SYSPARM variable. The message displays the name and value of the sysparm variable. The default name is

$SYSPARM when SYSPARM is specified in the parameter field on an EXEC statement (e.g., SYSPARM=DD). The key xxxxxxxxxx. The variable can be limited to a specific product, and the gblname name will have a value if the variable is global.

This message is only produced when CSRLOG=n is specified for DIF processing, or the DDLOG DD DUMMY statement was specified in a test job. For the DIF started task, messages are written to the SYSPRINT DD statement.

For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log.

Message Level: None

Response: None

DIF40400 NO OUTPUT DD

Explanation: The DCC/ZCC volume clone application was executed to copy tapes to a Bus-Tech MDL, EMC DLm, or Optica zVT. However, the application could not find any OUTnn DD statements in the execution JCL. The clone application uses the OUTnn DD statements to specify the target library for the copy process. Up to 99 OUTnn DD statements can be specified to allow up to 99 concurrent copy subtasks.

Message Level: E

Response: For more information, examine the Migration section of the DLM Control Center (DCC) User’s Guide for sample execution JCL for DLMCLONE, or the zVT Control Center (ZCC) User’s Guide for sample execution JCL for ZVTCLONE.

DIF40402 TAPECOPY SUBTASK ABENDED

Explanation: The DCC/ZCC volume clone application was executed to copy tapes to a Bus-Tech MDL, EMC DLm, or Optica zVT. Up to 99 OUTnn DD statements can be specified to allow up to 99 concurrent copy subtasks. One of the subtasks abended during the copy process. If possible, rerun the job and add a SYSUDUMP or SYSABEND DD statement to the execution JCL.

Message Level: E

Response: Please contact Customer support.

DIF40403 OUTPUT DD ddname NOT ASSOCIATED WITH DLM LIBRARY

Response: No action is required unless you want to change the status of the volume entry in the Audit file. You may wish to specify the TM(RMM(SCRATCH(SKIP)) parameter on the EXEC statement to cause volumes in SCRATCH or PENDING RELEASE status to be bypassed without attempting to mount them.

DIF4041X1 VOLUME volser WAITING TO BE EJECTED FROM sms-lib

Explanation: The DCC/ZCC volume clone application was executed to copy tapes to a Bus-Tech MDL, EMC DLm, or Optica zVT. This message is produced by an internal tape copy subtask. The migration project has requested that tapes be ejected from the old SMS library. This is a mechanical process and must complete before clone processing can add the tape to a new SMS library. This tape notifies the migration job that the subtask is waiting for the EJECT request to complete.

Message Level: A

Response: None

DIF40420 INPUT TAPE IO ERROR

Explanation: The DCC/ZCC volume clone application was executed to copy tapes to a Bus-Tech MDL, EMC DLm, or Optica zVT. This message is produced by an internal tape copy subtask. The copy subtask terminated because the clone application encountered an I/O error on the input tape.

Attempt to read the tape with a different application (i.e., DITTO) to determine if the tape can be successfully read by another program.

Message Level: E

Response: Please contact Customer support.

DIF40421 OUTPUT TAPE IO ERROR

Explanation: The DCC/ZCC volume clone application was executed to copy tapes to a Bus-Tech MDL, EMC DLm, or Optica zVT. This message is produced by an internal tape copy subtask. The copy subtask terminated because the clone application encountered an I/O error on the output tape.

Message Level: E

Response: Please contact Customer support.

DIF40422 END OF REEL OUTPUT TAPE

Explanation: The DCC/ZCC volume clone application was executed to copy tapes to a Bus-Tech MDL, EMC DLm, or Optica zVT. This message is produced by an internal tape copy subtask. The copy subtask terminated because the clone application encountered an EOV condition on the output tape. Note: This condition can be encountered when a DLM unit has been configured with a size limit that is smaller than the input tape.

Message Level: E

Response: Please contact Customer support.

Explanation: The DCC/ZCC volume clone application was executed to copy tapes to a Bus-Tech MDL, EMC DLm, or Optica zVT. This message is produced by an internal tape copy subtask. When the clone application read the input tape during copy processing, the application encountered a block that was greater than 256K.

Message Level: E

Response: Please contact Customer support.

DIF40429 WRONG INPUT TAPE MOUNTED

Explanation: The DCC/ZCC volume clone application was executed to copy tapes to a Bus-Tech MDL, EMC DLm, or Optica zVT. This message is produced by an internal tape copy subtask. When the clone application read the input tape during copy processing, the volume name extracted from the VOL1 record on the tape did not match the volume mounted on the input drive.

Message Level: E

Response: Please contact Customer support.

DIF4042A STOP REQUESTED

Explanation: The DCC/ZCC volume clone application was executed to copy tapes to a Bus-Tech MDL, EMC DLm, or Optica zVT. This message is produced by an internal tape copy subtask. An operator used the “F jobname,STOP volser” command to terminate the tape migration for the volume.

DIF90211 INCLUDE MEMBER memname CAUSED LOOP

Explanation: The rules language includes a member name that is currently active in include processing. For example, RULE01 includes RULE02, and RULE02 includes RULE01. If the include was allowed, rule processing would be stuck in a loop.

Message Level: E

Response: Correct the INCLUDE statements used by the rule language.

DIF90212 EOF ENCOUNTERED IN MEMBER memname WITHIN COMMENT BLOCK

Explanation: The rules language encountered an End- Of-File condition on a member while that member was still inside a comment block. The product will terminate all comment blocks and continue processing.

Message Level: W

Response: Examine the member to ensure that an incorrect comment block was specified.

DIF90230 CARD BUFFER OVERFLOW OCCURRED IN RULES CONVERSION

Explanation: The rules compiler uses the private region in the DIF started task for conversion. The buffer obtained for card images was insufficient to convert the rules definition statements. If the conversion process had been successful, the rules would have been moved into extended CSA.

Message Level: C

Response: The DIF SET command can be used to provide a larger conversion buffer for card images. By default, the rules compiler can process approximately 3500 card images for a rule member and included member names. This number can be much lower if your rules use DO-END statements.

For example, the following command could be used to increase the card image buffer for ACC to 5000 cards. If you still have problems, please contact Customer support.

F DIF,SET ACC RCARDS 5000

DIF90380 TYPE COMPARE ERROR ON statement AT LINE num: field_name

Explanation: During rules conversion, a filter list contained a field definition that would produce a comparison error during rule processing. A numeric field in a character comparison, or a character field in a numeric comparison. For more information, examine “SCC SYMBOLIC FIELDS” on page 6-1 in the Rules Language Programming Guide. Also, examine the “SYMBOLIC FIELDS” chapter for the related product.

Message Level: E

Response: Correct the control card. Then issue the START or REFRESH command.

DIF90420 INVALID SYMBOLIC OR LITERAL ON LINE NUMBER num

Explanation: During rules conversion, a FIELD subparameter on line num in a DEFREC statement contains an invalid symbolic name or literal. An invalid literal is a null field (‘’). For more information, examine “SCC SYMBOLIC FIELDS” on page 6-1 in the Rules Language Programming Guide. Also, examine the “SYMBOLIC FIELDS” chapter for the related product.

Message Level: E

Response: Correct the control card. Then issue the START or REFRESH command.

DIF90421 FIELD DEFINITION ON LINE num OVERRAN RECORD LENGTH

Explanation: During rules conversion, a FIELD subparameter on line num in a DEFREC statement causes the record buffer specified on the DEFREC statement to be overrun.

Message Level: E

Response: Increase record length on the associated DEFREC statement. Then issue the START or REFRESH command.

DIF90450 ABOVE ERROR OCCURRED IN

TABLE table_name LINE NUMBER num

Explanation: During rules conversion, an error occurred during table processing. A previous message details the error. This message displays the name and line number of the PDS member containing the error.

Message Level: E

Response: Correct the control card. Then issue the START or REFRESH command.

DIF90500 INVALID EXPRESSION ON LINE NUMBER num

Explanation: During rules conversion, the expression parse routine encountered an invalid expression at line num. For more information, examine “Expressions” on page 3-29 in the Rules Language Programming Guide.

Message Level: E

Response: Correct the control card. Then issue the START or REFRESH command.

DIF90510 TOKEN INVALID ON STMT

statement OPERAND operand LINE NUMBER num

Explanation: During rules conversion, an invalid item was encountered on line num. The names of the current statement and operand are also displayed in the message. For more information, examine the related statement definition in “RULES LANGUAGE REFERENCE” on page 5-1 in the

Rules Language Programming Guide.

Message Level: E

Response: Correct the control card. Then issue the START or REFRESH command.

DIF90520 NUMERIC FIELD INVALID ON STMT statement OPERAND operand LINE NUMBER num

Explanation: During rules conversion, an invalid numeric field was encountered on line num. The names of the current statement and operand are also displayed in the message. For more information, examine “SCC SYMBOLIC FIELDS” on page 6-1 in the Rules Language Programming Guide. Also, examine the “SYMBOLIC FIELDS” chapter for the related product.

Message Level: E

Response: Correct the control card. Then issue the START or REFRESH command.

DIF90530 NUMERIC VALUE INVALID ON

STMT statement OPERAND operand LINE NUMBER num

Explanation: During rules conversion, an invalid numeric value was encountered on line num. The names of the current statement and operand are also displayed in the message. For more information, examine “SCC SYMBOLIC FIELDS” on page 6-1 in the Rules Language Programming Guide. Also, examine the “SYMBOLIC FIELDS” chapter for the related product.

Message Level: E

Response: Correct the control card. Then issue the START or REFRESH command.

DIF90540 MESSAGE TEXT INVALID ON STMT statement OPERAND operand LINE NUMBER num

Explanation: During rules conversion, an invalid field was encountered processing the message text on line num. The names of the current statement and operand are also displayed in the message. For more information, examine “Using

DIF90650 INVALID OPERAND SPECIFIED ON

statement AT LINE num: operand

expression used a numeric range check, and an invalid relational operator was used in the expression. Only EQ or = is allowed for a numeric range check.

WILDCARD COMPARES ONLY ALLOW “EQ” OR

“NE” - The expression used pattern matching, and an invalid relational operator was used in the expression. Only EQ, =, NE, <>, or ¬= is allowed for a wildcard comparison.

FILTLIST COMPARES ONLY ALLOW “EQ” OR “NE”

- The expression used a filter list symbolic name, and an invalid relational operator was used in the expression. Only EQ, =, NE, <>, or ¬= is allowed for comparisons using filter lists.

DIFFERENT FIELD TYPES USED IN EXPRESSION -

The expression used fields of different types. A character field can only be compared with another character field. Numeric fields can only be compared with another numeric field or a numeric range check.

FILTLIST NOT ALLOWED AS OBJECT - The expression used a filter list symbolic name on the left side of the expression. Filter lists are allowed only on the right side of the relational operator.

NUMERIC MOD. EXPRESSION INVALID (LEFT) - The

symbolic field to the left of the relational operator used an invalid numeric modification expression. Numeric modifications are only allowed on SET expressions. For example, the following SET expression shows the proper use of numeric modification:

SET &USRFLDN1 = &USRFLDN1+1

NUMERIC MOD. EXPRESSION INVALID (RIGHT) - A

field to the right of the relational operator used an invalid numeric modification expression. Numeric modifications are only allowed on SET expressions. For example, the following SET expression shows the proper use of numeric modification:

SET &USRFLDN1 = &USRFLDN1+1

Message Level: E

Response: Correct the control card. Then issue the START or REFRESH command.

DIF90710 VALIDATION ERROR ON SET AT LINE num - vald_error

Explanation: The rules conversion process encountered an invalid expression on line num. The vald_error can be used to identify the problem with the expression.

RELATIONAL OPERATOR MUST BE “EQ” - An invalid

relational operator was used in the SET expression. Only EQ or = is allowed in a SET expression.

SYMBOLIC FIELD IS READ ONLY - The symbolic field is a read-only field. The SET expression cannot be allowed to update this field. For more information, examine “SCC SYMBOLIC FIELDS” on page 6-1 in the Rules Language Programming Guide. Also, examine the “SYMBOLIC FIELDS” chapter for the related product.

VALUE ITEM IN SET USED WILDCHAR CHARS - The

value item in the SET expression used pattern matching. Wildcard characters are not allowed in the value item: the field on the right side of the equal sign.

NUMERIC MODIFICATION EXPRESSION INVALID -

The symbolic field to the left of the relational operator used an invalid numeric modification expression. Numeric modifications are only allowed on the right side of the SET expressions. For example, the following SET expression shows the proper use of numeric modification: SET &USRFLDN1 = &USRFLDN1*25%

FILTLIST NOT ALLOWED IN SET_EXPR (LEFT) - The

SET expression used a filter list symbolic name on the left side of the expression. Filter lists are not allowed in SET expressions.

FILTLIST NOT ALLOWED IN SET_EXPR (RIGHT) -

The SET expression used a filter list symbolic name on the right side of the expression. Filter lists are not allowed in SET expressions.

NUMERIC MODIFICATION ATTEMPTS ZERO

DIVIDE - The numeric modification attempts a divide by zero. Since this would result in a product abend, the rule language will not allow this expression.

PERCENT MODIFICATION ON MULTIPLY ONLY -

DIF90802 * WARNING - THE poolname POOL HAS NO DEVICES *

Explanation: After rules conversion routine has completed validation, the conversion process builds the eligible device tables for each pool definition. The expressions used by the poolname trimmed all the devices from the pool definition.

Message Level: W

Response: Examine the DEFPOOL statements for the

poolname to determine whether this situation was intended.

DIF90850 BUFFER OVERFLOW OCCURRED IN RULES CONVERSION

Explanation: The rules conversion process uses the private region in the DIF started task for conversion. The buffer obtained was insufficient to convert the rules definition statements. If the conversion process had been successful, the rules would have been moved into extended CSA.

Message Level: C

Response: The DIF SET command can be used to provide a larger conversion buffer for data structures. By default, the rules compiler can process approximately 200 kilobytes of data structures for a rule member and included member names. For example, the following command could be used to increase the buffer for ACC to 300 kilobytes. If you still have problems, please contact Customer support.

F DIF,SET ACC RCONVBUF 300

DIF90851 POOL pool_name RESTRICT(ALL) REQUIRES DEFENV DD PROCESS(DISKALL)

Explanation: The DEFPOOL statement has RESTRICT(ALL) specified. This operand forces ACC to deny allocation for non-ACC controlled data sets to restricted ACC volumes. To allow existing data sets to be ACC controlled, specify DEFENV DD PROCESS(DISKALL).

Message Level: E

Response: Add DEFENV DD PROCESS(DISKALL) to the rules, or remove the RESTRICT(ALL) parameter from the DEFPOOL statement.

Note: When DEFENV DD PROCESS(DISKALL) is specified in the rules language, ACC will examine all disk DD statements during allocation. If the language was designed for new data set allocations only, this parameter may force your rules language to be too restrictive. The following rule could be added near the start of the rules language to allow the use of RESTRICT(ALL), but force ACC to ignore rules processing for existing data sets.

DEFRULE SKIPOLD
IF DISP1 NE NEW
THEN QUIT

DIF91010 *** WARNING memname

Explanation: After the rule compiler successfully converts a rule member, the rule conversion process examines the DIF started task for the RULECKPT DD statement. If the checkpoint file is available, the rule compiler writes the converted rule member to the checkpoint data set.

During start processing, the memname failed on rule conversion. The rule compiler recalled the member from the checkpoint data set.

Message Level: W

Response: Please examine related messages, and correct the problem(s) with the rule statements. A REFRESH command can then be issued to compile the current rules.

DIF91011 memname NOT FOUND IN CHECKPOINT DATA SET

Explanation: After the rule compiler successfully converts a rule member, the rule conversion process examines the DIF started task for the RULECKPT DD statement. If the checkpoint file is available, the rule compiler writes the converted rule member to the checkpoint data set.

During start processing, the memname failed on rule conversion. The rule compiler attempted a recall from the checkpoint data set, but the rule has not been checkpointed. Start processing failed for the product.

Message Level: E

Response: Please examine related messages, and correct the problem(s) with the rule statements. A START command can then be issued to start the product.

DIF91012 memname IN CHECKPOINT DATA SET TOO LARGE FOR BUFFER

Explanation: After the rule compiler successfully converts a rule member, the rule conversion process examines the DIF started task for the RULECKPT DD statement. If the checkpoint file is available, the rule compiler writes the converted rule member to the checkpoint data set.

During start processing, the memname failed on rule conversion. The rule compiler attempted a recall from the checkpoint data set, but the buffer used by the compiler when the checkpoint occurred is larger than the current rule buffer. Start processing failed for the product.

Message Level: E

Response: Please examine related messages, and correct the problem(s) with the rule statements. A START command can then be issued to start the product.

DIF91013 memname IN CHECKPOINT DATA SET FROM DIFFERENT RELEASE

Explanation: After the rule compiler successfully converts a rule member, the rule conversion process examines the DIF started task for the RULECKPT DD statement. If the checkpoint file is available, the rule compiler writes the converted rule member to the checkpoint data set.

DIF00101 START OPTIONS: options

DIF00103 ddname COULD NOT BE OPENED

DIF00104 ANOTHER DYNAMIC INSTALL JOB IS ACTIVE FOR subsys

DIF00105 COLD START IGNORED

DIF00106 DYNAMIC INSTALL FACILITY IS NOT AUTHORIZED

DIF00107 OPSYS(sysrel) FMID(fmid) VERSION(ver) DFPREL(X’dfprel’) SMSREL(X’smsrel’)

DIF00108 ENTER YES TO CONTINUE START

DIF00109 SUBSYS COMMAND CHARACTER cmdchar IS ALREADY IN USE

DIF00150 READY FOR MODIFY COMMANDS OR USE cmdchar

DIF00151 OPERATOR STOP COMMAND NOT SUPPORTED. USE DIF Z OR SHUTDOWN COMMAND

DIF00152 RACF SECURITY ERROR - RC=src-rrc

DIF00200 OPSYS VALUE IS NOT VALID

DIF00310 SUBSYSTEM DOES NOT POINT TO A VALID DCVT

DIF00311 DIF LEVEL HAS CHANGED - COLD START REQUIRED

DIF00312 ENF CALL FAILED - RC = X’rc’

DIF00313 LICENSED FOR COMPANY NAME: company-name

DIF00314 LICENSED FOR LOCATION: location

DIF00315 CPU INFORMATION: CPUID(cpuid)

DIF00316 LICENSE MEMBER IN DIF PARMLIB IS NOT VALID

DIF00330 SYSTEM DOES NOT SUPPORT NEW JCL

DIF00331 JCL TABLE NOT CORRECT FORMAT

DIF00332 JCL DEFINE FAILED - RC=X’rc’

DIF00361 COLD START SPECIFIED BUT PRODUCTS ARE ACTIVE

DIF00362 ENTER YES TO CONTINUE WITH COLD START

DIF00370 DIF SVC TABLE IS FULL

DIF00370 DIF SVC TABLE IS FULL

DIF00500 STARTING READER FOR name

DIF00501 STARTING WRITER FOR DESTINATION dest

DIF00502 STARTING WRITER FOR DDNAME ddname

DIF00503 AUTOMATIC RESTART num FOR name WRITER

DIF00560 APPC function FAILED RC=rc-rs

DIF00590 LICENSE CHECK FAILED FOR product

DIF00600 product NOT LICENSED FOR CPU cpuid cputype cpumodel

DIF00601 THE LICENSE FOR product HAS EXPIRED

DIF00602 *** product WILL EXPIRE IN nn DAYS ***

DIF00603 LICENSE: text

DIF00604 THERE IS NO LICENSE MEMBER

DIF00605 NO VALID ENTRY IN LICENSE MEMBER FOR PRODUCT

DIF00606 THE LICENSE FOR product IS LIMITED TO release

DIF00607 product NOT LICENSED FOR CPU cpuid LPAR:nn MSU:msu-cap

DIF00608 *** product USES SITE LICENSE KEY ***

DIF00610 PARMLIB DATA SET NOT ALLOCATED

DIF00611 OPEN FAILED FOR PARMLIB DCB

DIF00612 MEMBER memname NOT IN PARMLIB DATA SET

DIF00700 PRODUCT TABLE HAS INVALID FORMAT

DIF00701 CURRENT RELEASE OF DIF (crel) IS NOT COMPATIBLE WITH product WHICH REQUIRES RELEASE rrel.

DIF00703 option REQUIRES THAT product BE ACTIVE

DIF00704 PRODUCT TABLE FOR product COULD NOT BE CREATED

DIF00750 FILE filename(ddname) IS NOW CLOSED

DIF00751 ALLOCATE FAILED FOR DDNAME ddname - RC=r15-s99e-s99i

DIF00780 status host/portnum

DIF00800 APPC REQUEST FROM luname)/userid: prdname function data

DIF00801 SECURITY CHECK FAILED

DIF00820 CONVERSATION FOR userid TIMED OUT

DIF00860 IXCJOIN FAILED. RC=rc-rs

DIF00861 SYSPLEX name type func

DIF01000 product HAS NOT BEEN STARTED

DIF01010 PRODUCT ID OF ptid DOES NOT MATCH ID IN MODULE load-mod(lmid)

DIF01011 PRODUCT RELEASE ptrel DOES NOT MATCH RELEASE NUMBER IN MODULE loadmod(lmrel)

DIF01020 OPERAND IS TOO LONG

DIF01021 OPERAND IS REQUIRED

DIF01023 INVALID KEYWORD ENTERED ON COMMAND

DIF01040 PRODUCT LOCK FAILED RC=X’rc

DIF01041 product NOT DORMANT - WAITING FOR PRODUCT LOCK

DIF01042 REPLY 'INACT' OR 'FORCE'. TO CONTINUE WAITING, DO NOT REPLY

DIF01043 OPERATOR CANCELED WAIT

DIF01044 LOCK OBTAINED - COMMAND PROCEEDING

DIF01045 REPLY OF msgreply IS INVALID

DIF01070 STORAGE NOT AVAILABLE FOR DISPLAY

DIF01100 date time CN(cnid): cmdtext

DIF01101 UNKNOWN COMMAND: cmdname

DIF01102 product DOES NOT SUPPORT COMMANDS

DIF01103 product CANNOT ACCEPT COMMANDS UNTIL ACTIVE

DIF01104 product IS NOT AN ACTIVE PRODUCT

DIF01105 cmdname MUST BE PRECEDED BY ENABLE/DISABLE

DIF01106 cmdname NOT A VALID ENABLE/ DISABLE OPERAND

DIF01107 cmdname IS AMBIGUOUS

DIF01108 PRODUCT NAME IS REQUIRED FOR cmdname COMMAND

DIF01109 COMMAND COMPLETED WITHOUT ISSUING ANY MESSAGES

DIF00602 * product WILL EXPIRE IN nn DAYS *

DIF00608 * product USES SITE LICENSE KEY *