According to QuickRef, something is up that you are not aware of and it
is preventing you from shooting yourself in the foot! :-)
This message may occur:
- if you have systems which are not running MVS-type operating systems
or which are not active; see "Multi-System Determination" in Section
320.01 for
details
- if you have not started a 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 will
probably need to increase the task or LPAR priority to get a successful
swap.
Message FDR234 REASON=M may also be displayed on the console to identify
the non- responding systems. See the topic "System Determination" in
Section 300.05 for an explanation of FDRPAS multi-system operation and
the
determination of the number of systems. Also see the #SYSTEMS= and
MIN#SYSTEMS= parameters in Section 310.02.
. If you are using the FDRPAS ISPF panels to monitor active swaps, this
message will also appear on the ISPF display; you can reply to it from
ISPF or from the operator console.
Note: 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.
Action: Reply YES - if you want the swap to continue. This should be
done only if you are sure that the additional system images do
not have the source volume online; Innovation
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.
Reply NO - terminate the swap request. Message FDR234
REASON=Q will be printed.
Reply RETRY - FDRPAS will wait 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 will be 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.
I would heed that warning.
Bob Richards
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Tom Moulder
Sent: Tuesday, June 12, 2007 12:03 PM
To: [email protected]
Subject: FDRPAS Question
I have a four CPU complex with multiple LPARS on each CEC and DASD
from three vendors attached to all CECs. Using FDRPAS to swap a
volume that is only online to one volume, but getting fdrw68 message.
Anyone else run into that situation? What did you do to get rid of
the message? Any suggestions are appreciated.
LEGAL DISCLAIMER
The information transmitted is intended solely for the individual or entity to
which it is addressed and may contain confidential and/or privileged material.
Any review, retransmission, dissemination or other use of or taking action in
reliance upon this information by persons or entities other than the intended
recipient is prohibited. If you have received this email in error please
contact the sender and delete the material from any computer.
SunTrust and Seeing beyond money are federally registered service marks of
SunTrust Banks, Inc.
[ST:XCL]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
