Gadi, 

You are correct, you cannot flash to a Global Mirror primary.  I sincerely 
doubt you want to terminate your Global Mirror relationships so that you can do 
a DFDSS backup of a group of volumes either.  If you did then you would need to 
do a full push of your data for those volumes.

I prefer to replicate everything using Global Mirror so an additional backup 
normally is not needed.  However if you have a smaller subset of volumes that 
you want to flash and do a backup of, those need to be removed from your Global 
Mirror Session.  Those volumes could be in a separate group where you 
Flash/backup and then establish a XD relationship (outside of GM).  They will 
not be consistent with the rest of your GM environment though. 

Roger


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Carmen Vitullo
Sent: Thursday, November 30, 2017 9:06 AM
To: [email protected]
Subject: Re: Problem after starting PPRC

Gadi, been a while, but I believe you can issue the FCWITHDR 



PURPOSE: ISSUE FCWITHDR COMMAND TO ENSURE FLASH TO VOLUMES ARE AVAILABLE. 

//STEP01 EXEC PGM=IKJEFT01,DYNAMNBR=20
//**********************************************
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
FCWITHDR TDEVN(X'4749') 


https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.antg000/vstates.htm
 




Carmen Vitullo 

----- Original Message -----

From: "גדי בן אבי" <[email protected]>
To: [email protected]
Sent: Thursday, November 30, 2017 7:59:31 AM
Subject: Re: Problem after starting PPRC 

I know that
Is there a way to disable to Peer to Peer relationship in batch so the job will 
work. 

Gadi 

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Carmen Vitullo
Sent: Thursday, November 30, 2017 3:29 PM
To: [email protected]
Subject: Re: Problem after starting PPRC 

A quick look it appears a Peer to Peer relationship was already established 
with the output volume your error message PPRC PRIM CURRENTLY ACTIVE ADR938E 


RC 9 in the nice message guide sez 



X'9' 
One or more target devices are not eligible for fast replication at this time. 


When DEBUG(FRMSG(SUMMARIZED)) is specified, return code X'9' is followed by 
summarized volume information that consists of reason codes that indicate why 
one or more volumes are not eligible. For each reason code issued, the number 
of volumes failing for that reason is provided. The reason codes include SDM 
QFRVOLS volume reason codes (qfrvols_vrsn) and extent reason codes 
(qfrvols_xrsn). 
You can use the DEVSRV (DS P) command to check any P-P relationship 


Carmen Vitullo 

----- Original Message ----- 

From: "גדי בן אבי" <[email protected]>
To: [email protected]
Sent: Thursday, November 30, 2017 6:22:11 AM
Subject: Problem after starting PPRC 

Hi, 

Yesterday we established PPRC (Global Mirror) relationships between our local 
DS8884 and our remote DS8884. 
This is our first venture into the storage replication area. 

We have a series of jobs that use flashcopy to copy a volume to a secondary 
volume, and then backu to secondary to tape. This is done using DFSMSdss. 
The command looks like this: 
COPY FULL ADMINISTRATOR INDYNAM(SCR016) OUTDYNAM(FLSH04) - DUMPCONDITIONING 
FASTREPLICATION(REQUIRED) PURGE ALLDATA(*) - ALLEXCP CANCELERROR IF LASTCC = 0 
THEN DUMP FULL ADMIN INDYNAM(FLSH04) OUTDDNAME(OUTPUT) ALLDATA(*) - ALLEXCP 
OPTIMIZE(4) CANCELERROR 

When the jobs ran last night it returned: 
PAGE 0001 5695-DF175 DFSMSDSS V2R01.0 DATA SET SERVICES 2017.334 05:29 COPY 
FULL ADMINISTRATOR INDYNAM(SCR016) OUTDYNAM(FLSH04) - DUMPCONDITIONING 
FASTREPLICATION(REQUIRED) PURGE ALLDATA(*) - ALLEXCP CANCELERROR ADR101I 
(R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'COPY ' 
IF LASTCC = 0 THEN
ADR101I (R/I)-RI01 (01), TASKID 002 HAS BEEN ASSIGNED TO COMMAND 'IF ' 
DUMP FULL ADMIN INDYNAM(FLSH04) OUTDDNAME(OUTPUT) ALLDATA(*) - ALLEXCP 
OPTIMIZE(4) CANCELERROR ADR101I (R/I)-RI01 (01), TASKID 003 HAS BEEN ASSIGNED 
TO COMMAND 'DUMP ' 
ADR109I (R/I)-RI01 (01), 2017.334 05:29:33 INITIAL SCAN OF USER CONTROL 
STATEMENTS COMPLETED ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR 
THIS TASK ADR006I (001)-STEND(01), 2017.334 05:29:33 EXECUTION BEGINS ADR918I 
(001)-DDTFP(03), FAST REPLICATION COULD NOT BE USED FOR VOLUME SCR016, RETURN 
CODE 9
1 VOLUME WAS REJECTED FOR QFRVOLS VOLUME REASON CODE 2 - PPRC PRIM CURRENTLY 
ACTIVE ADR938E (001)-DDTFP(03), FASTREPLICATION(REQUIRED) WAS SPECIFIED BUT 
FAST REPLICATION COULD NOT BE USED FOR VOLUME SCR016 ADR006I (001)-STEND(02), 
2017.334 05:29:33 EXECUTION ENDS ADR013I (001)-CLTSK(01), 2017.334 05:29:33 
TASK COMPLETED WITH RETURN CODE 0008 ADR016I (003)-PRIME(01), RACF LOGGING 
OPTION IN EFFECT FOR THIS TASK ADR006I (003)-STEND(01), 2017.334 05:29:34 
EXECUTION BEGINS ADR006I (003)-STEND(02), 2017.334 05:51:15 EXECUTION ENDS 
ADR013I (003)-CLTSK(01), 2017.334 05:51:15 TASK COMPLETED WITH RETURN CODE 0000 
ADR012I (SCH)-DSSU (01), 2017.334 05:51:15 DFSMSDSS PROCESSING COMPLETE. 
HIGHEST RETURN CODE IS 0008 FROM: 
TASK 001 

From what I read, I have to remove the PPRC connection for the Flashcopy 
Target, and then reestablish it (maybe). 

Am I correct? 
How can I do this in batch, hopefully only specifying the VOLSER’s. 

We are running z/OS v2.1 

Thanks 

Gadi
לתשומת ליבך, בהתאם לנהלי חברת מלם מערכות בע"מ ו/או כל חברת בת ו/או חברה קשורה 
שלה (להלן : "החברה") וזכויות החתימה בהן, כל הצעה, התחייבות או מצג מטעם החברה, 
מחייבים מסמך נפרד וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או 
שמה המודפס ובצירוף חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף 
להודעת דואר אלקטרוני זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין 
להסתמך עליה לביצוע פעולה עסקית או משפטית כלשהי. Please note that in accordance 
with Malam and/or its subsidiaries (hereinafter : "Malam") regulations and 
signatory rights, no offer, agreement, concession or representation is binding 
on the Malam, unless accompanied by a duly signed separate document (or a 
scanned version thereof), affixed with the Malam seal. 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN 


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN לתשומת ליבך, בהתאם 
לנהלי חברת מלם מערכות בע"מ ו/או כל חברת בת ו/או חברה קשורה שלה (להלן : "החברה") 
וזכויות החתימה בהן, כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד 
וחתום על ידי מורשי החתימה של החברה, הנושא את לוגו החברה או שמה המודפס ובצירוף 
חותמת החברה. בהעדר מסמך כאמור (לרבות מסמך סרוק) המצורף להודעת דואר אלקטרוני 
זאת, אין לראות באמור בהודעה אלא משום טיוטה לדיון, ואין להסתמך עליה לביצוע פעולה 
עסקית או משפטית כלשהי. Please note that in accordance with Malam and/or its 
subsidiaries (hereinafter : "Malam") regulations and signatory rights, no 
offer, agreement, concession or representation is binding on the Malam, unless 
accompanied by a duly signed separate document (or a scanned version thereof), 
affixed with the Malam seal. 

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN 


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to