Console messages


The following write-to-operator (WTO) and write-to-operator-with-reply (WTOR) are issued by FDR:

Number

Description

FDRW01

CONFIRM REQUEST TO  function  VOL= vol  TO UNIT= uuuu  ON  nnn  SYSTEMS REPLY YES OR NO


Explanation: FDRPAS has been requested to process volume “vol” to offline target device “uuuu” and CONFMESS=YES was specified. “nnn” system images are participating in the function. “function” is SWAP for a SWAP function or DUMP for a SWAPDUMP function. If you are using the FDRPAS ISPF panels to monitor active swaps, this message also appears on the ISPF display; you can reply to it from ISPF or from the operator console.

If WTOR=NO is specified on the FDRPAS main statement, then the FDRW01 message is issued as a WTO, not a WTOR, and the operator cannot reply; the FDRPAS ISPF panel must be used to reply.

User response:  Reply YES – Operator approves request.

Reply NO – Operator does not approve the request; the function is terminated. Message FDR234 Explanation=Q is printed.

To perform FDRERASE without operator intervention, specify CONFERASE=NO on the SWAP statement or omit CONFERASE= (NO is the default).

FDRW01

CONFIRM REQUEST TO INITV nnnn UNITS - REPLY YES OR NO - SEE PREVIOUS FDR235 MSG FOR UNITS


Explanation:  This form of message FDRW01 is issued by FDRINITV if CONFERASE=YES is specified. It is issued once for all the units to be initialized (the units are listed in message FDR235 that precedes the FDRW01).

User response: Reply YES – Operator approves request.

Reply NO – Operator does not approve the request; the function is terminated. Message FDR234 Explanation=Q is printed.

To perform INITV without operator intervention, specify CONFERASE=NO on the SWAP statement or omit CONFERASE= (NO is the default).


FDRW01

CONFIRM REQUEST TO VARY OFFLINE FOR function VOL=vol UNIT=uuuu - REPLY YES, NO OR ALL

Explanation: This form of message FDRW01 is issued by FDRERASE or FDRINITV if ONLINE=VARYOFF is specified. It is issued for each online unit that is varied offline and erased or initialized.

User response: Reply YES – Operator approves request for this volume.

Reply NO – Operator does not approve the request; the erase of this volume is terminated. Message FDR234 Explanation=Q is printed.

Reply ALL  – Operator approves request for this volume and all subsequent volumes in this step. No further FDRW01 messages are issued.

FDRW07

JOB=job READY TO CONFIRM function REPLY YES TO CONFIRM


Explanation: A MONITOR TYPE=CONFIRMSWAP or TYPE=CONFIRMSPLIT was submitted with CONFMESS=YES specified. When all the volumes in the CONFIRM step are synchronized, this FDRW07 message is issued.

User response: Reply “YES” when you are ready to confirm the volumes and complete the SWAP or SWAPDUMP operation on those volumes.

CONFMESS=YES can be useful with TYPE=CONFIRMxxxx when you use a system automation product. The product can wait for the FDRW07 message, perform other functions such as quiescing some applications, and then confirm the swaps by replying “YES”.

FDRW45

MIM ACTIVE -- MOVES ON OTHER SYSTEMS WILL NOT BE DETECTED


Explanation: FDRMOVE detected that MIM is the cross-system enqueue product. This is a warning to notify the site that data set moves on other systems are not detected by FDRMOVE.

User response: The MIM cross-system enqueue product does not support GQSCAN, so FDRMOVE can not determine if a job on another system moves a data set. To reduce the window, where this is a factor, use FASTMOVE if possible or ensure that data sets are not being moved by other jobs.

FDRW60

FDROPSPF VER  x . x / xx  - PROCESSING ERROR - PARM-LVL  level


Explanation: The FDR installation dialog CLIST invoked program FDROPSPF with an incompatible parameter level, indicating that the DDNAME allocations for the FDR CLIST library and the FDR program library point to libraries at different maintenance levels. On a re-installation, the problem might be that the new FDR program library is not allocated to either ISPLLIB or STEPLIB DDNAMEs, thus causing the prior level FDR programs to be loaded from the Linklist.

User response: Use the ABRALLOC CLIST supplied by BMC Support, as documented in Invoking the Installation ISPF Dialog (Panel A.I).

FDRW66

function  OF VOL= vol  TO UNIT= uuuu  STARTED ON  nnn  SYSTEMS ( sysid1  …)


Explanation:  FDRPAS has begun to process volume  vol to offline unit uuuunnn systems (1-128) systems are participating in the function. The system names of the participating systems are listed (if all system names cannot fit in one message, additional FDRW66 messages with only the additional system names are issued). “function” is SWAP for a SWAP function or DUMP for a SWAPDUMP function.

FDRW66

function  OF VOL= vol  TO UNIT= uuuu  CONTINUES WITH OVERRIDE OF WARNINGS


Explanation:  This form of the  FDRW66 message occurs when the swap has been allowed to continue despite warning messages. For example, you replied YES to the FDRW68 message, to document that you have approved continuing with the swap despite the warning that an apparent insufficient number of systems are participating, or you specified LARGERSIZE=OK to allow a swap to a larger DASD. “function” is SWAP for a SWAP function or DUMP for a SWAPDUMP function.

FDRW66

SWAP OF VOL= vol  TO UNIT= uuuu  NEEDS TO BE STARTED ON  nnn  SYSTEMS

Explanation: This form of the FDRW66 message occurs for a SIMSWAP operation and appears only in the printout, not on the console. It indicates that FDRPAS has determined that the volume “vol” is attached to “nnn” systems (not including systems for which EXCLUDE statements were present) and a MONITOR task or SWAP task should be running on each of those systems. If FDRPAS was unable to determine the number of systems, “nnn” is the value you specified for #SYSTEMS=nnn.

FDRW68

CAUTION REQUEST TO SWAP VOL=vol TO UNIT=uuuu ON nnn SYSTEMS- IGNORING mmm NON-RESPONDING CPUS REPLY RETRY OR NO
 CAUTION REQUEST TO SWAP VOL=vol TO UNIT=uuuu ON nnn SYSTEMS- IGNORING mmm NON-RESPONDING CPUS REPLY YES, NO OR RETRY


Explanation: FDRPAS has been requested to process volume “vol” to offline target device “uuuu”. “nnn” system images have indicated that they will participate in the function within a time limit imposed by FDRPAS, but FDRPAS expected that a larger number of systems would participate. The second form appears if NONRESPONDING=MSG is in effect, as described in SWAP, SWAPDUMP, SIMSWAP, SIMSWAPMON Statements.

If the source volume is in an EMC Symmetrix subsystem (except the 4xxx series), or in an IBM DS8xxx or Hitachi VSP subsystem with the Query Host Access (QHA) feature, then FDRPAS only expects a system to participate in the SWAP if the source volume is online on that system. If the source volume is not in one of these subsystems, then FDRPAS cannot tell whether the volume is online on another system, and expects a system to participate in the SWAP if the source volume is connected to that system. See topics Query Host Access Support and Multi-System Determination in FDRPAS Special Hardware Considerations for further information.

This message may occur:

  • If you have systems that are not running z/OS-type operating systems or that are not active. See Multi-System Determination for details.
  • If you have not started an FDRPAS MONITOR task on all system images.
  • If the target device is online to some systems (see message FDR235 in the MONITOR task listings).
  • If the MONITOR tasks are not monitoring the proper target device(s).
  • If some MONITOR tasks have failed.
  • If the MONITOR tasks have a low dispatching priority on a busy system, or the LPAR running the MONITOR task has a low priority; you probably need to increase the task or LPAR priority to get a successful swap.

Message FDR234 Explanation=M may also be displayed on the console to identify the non-responding systems. See System Determination for an explanation of FDRPAS multi-system operation and the determination of the number of systems. If you are using the FDRPAS ISPF panels to monitor active swaps, this message also appears on the ISPF display; you can reply to it from ISPF or from the operator console.

If WTOR=NO is specified on the FDRPAS main statement, then the FDRW68 message is issued as a WTO, not a WTOR, and the operator cannot reply; the FDRPAS ISPF panel must be used to reply. If you specify NONRESPONDING=FAIL, then no message is issued and FDRPAS acts as if “NO” was replied (terminate the swap).

User response: Reply YES – if you want the swap to continue. A reply of YES is accepted only if YES was shown as an option in message FDRW68, i.e. only if NONRESPONDING=MSG is in effect, as described in SWAP, SWAPDUMP, SIMSWAP, SIMSWAPMON Statements . Only reply YES if you are sure that the additional system images do not have the source volume online; BMC Support suggests that you use console commands on every system to verify how many have the volume online. If in doubt, reply “NO” until the condition can be investigated and corrected if necessary. You should always contact BMC Support before responding “YES” to this message.

Reply NO – terminate the swap request. Message FDR234 Explanation=Q is printed.

Reply RETRY – FDRPAS waits additional time to see if the additional systems indicate their participation. If you did not start FDRPAS MONITOR tasks on all systems, start them before replying. If sufficient additional systems do not participate, the message is reissued.

Under no circumstances should you automate the reply to this message. Every occurrence of the message must be investigated by a knowledgeable person before replying. We recommend that you reply “RETRY” at least once in case some MONITOR tasks were running but were not able to respond in time.



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*