>
>Since I now know that the problem is NOT hardware related, I've tried
>everything to figure out what the problem is. I've installed the patch that
>helps in problem determination (PATCH .FRGCB.+9 BITS(.1......)) and what I
>get follows:
>
>ARC1809I VOLUME CP00AA IS NOT A FAST REPLICATION CANDIDATE FOR L0 VOLUME
>PPRD46, VER=0012, RC=0002
>
>and the RC=0002 says:
>
>volser1 is already paired with another source volume
>
>but when I did the FlashCopy query against the target volume CP00AA it says
>that there's no other relationships on the target volume.
>
>ICKDSF - MVS/ESA    DEVICE SUPPORT FACILITIES 17.0
>
>   FLASHCPY QUERY DDNAME(FCVOL)
>ICK00700I DEVICE INFORMATION FOR 81DE IS CURRENTLY AS FOLLOWS:
>          PHYSICAL DEVICE = 3390
>          STORAGE CONTROLLER = 2107
>          STORAGE CONTROL DESCRIPTOR = E8
>          DEVICE DESCRIPTOR = 0A
>          ADDITIONAL DEVICE INFORMATION = 4800003C
>          TRKS/CYL = 15, # PRIMARY CYLS = 3339
>ICK04000I DEVICE IS IN SIMPLEX STATE
>ICK03091I EXISTING VOLUME SERIAL READ = CP00AA
>
>FLASHCOPY VOLUME CAPABILITY INFORMATION TABLE
>              MAXIMUM      MAXIMUM
> *EXISTING*     ALLOWED      RELATIONS
> *RELATIONS*    RELATIONS    EXCEEDED     CAPABILITY
> *---------*    ---------    ---------    ----------
>     *0*          50099         NO         SRC CAP
>ICKDSF - MVS/ESA    DEVICE SUPPORT FACILITIES 17.0
>                                         TGT CAP
>
>I even ran it against the source volume:
>
>ICKDSF - MVS/ESA    DEVICE SUPPORT FACILITIES 17.0
>
>   FLASHCPY QUERY DDNAME(FCVOL)
>ICK00700I DEVICE INFORMATION FOR 833B IS CURRENTLY AS FOLLOWS:
>          PHYSICAL DEVICE = 3390
>          STORAGE CONTROLLER = 2107
>          STORAGE CONTROL DESCRIPTOR = E8
>          DEVICE DESCRIPTOR = 0A
>          ADDITIONAL DEVICE INFORMATION = 4800003C
>          TRKS/CYL = 15, # PRIMARY CYLS = 3339
>ICK04000I DEVICE IS IN SIMPLEX STATE
>ICK03091I EXISTING VOLUME SERIAL READ = PPRD46
>
>FLASHCOPY VOLUME CAPABILITY INFORMATION TABLE
>              MAXIMUM      MAXIMUM
> *EXISTING*     ALLOWED      RELATIONS
> *RELATIONS*    RELATIONS    EXCEEDED     CAPABILITY
> ---------    ---------    ---------    ----------
>     *0*          50099         NO         SRC CAP
>ICKDSF - MVS/ESA    DEVICE SUPPORT FACILITIES 17.0
>                                         TGT CAP
>
>Any help is appreciated!
>*
>*


George,

Have you checked out (I always search the internet for messages you post) the 
REDBOOK  z/OS Version 1 Release 13 Implementation

It has the following section:

6.21 Fast replication ARC1809I messages

Fast replication backup processing issues excessive ARC1809I messages when 
reporting
the reason why a target volume cannot be paired to a source volume.
The ARC1809I RC2 message indicates that a source and target cannot be paired 
because
the target volume has already been matched with a different source. For a 
single FRBACKUP
command, the ARC1809I RC2 can be issued many times for each target volume.

In previous releases, a patch command can be used to turn off all ARC1809I 
messages. In
z/OS V1R13 a new SETSYS command called FASTREPLICATION will replace the existing
patch to enable or disable the redundant ARC1809I messages.
This enhancement will decrease the number of ARC1809I RC2 messages such that the
message will be issued no more than once per target volume for each storage 
group in the
copy pool.

If you currently have PATCH .FRGCB.+9 BITS(.1......) in your ARCCMDxx parmlib 
member,
you should replace the patch with the desired command as follows:
SETSYS FASTREPLICATION(VOLUMEPAIRMESSAGES(YES|NO))
YES YES indicates that the ARC1809I RC2 messages should be issued when a target
volume cannot be paired with a source volume.
NO NO indicates that the ARC1809I RC2 messages should not be issued.



You might want to see if the ARC1809I is reasonable or not.


Lizette

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

Reply via email to