Example 2. DUMP FULL with CONCURRENT COPY

You can use the volume being dumped without the dump being affected, much sooner than with the normal full volume dump. You might want to use this method when the Linux partitions that are being backed up need to be available in read/write mode.

On the DUMP FULL command, include the keyword CONCURRENT.

Figure 1 shows an example of the JCL.

Figure 1. Sample JCL for DUMP FULL with CONCURRENT COPY.

//LXD2D2BB JOB ,'IBMUSER',MSGLEVEL=(1,1),TIME=(5,0),REGION=4096K,
//      MSGCLASS=H,CLASS=A
//STEPT02  EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//SOURCE   DD UNIT=3390,VOL=SER=LNX200,DISP=OLD
//TARGET   DD UNIT=TAPE,VOL=(PRIVAT,SER=111111),DISP=(NEW,CATLG),
//            DSN=TDS.DUMP200,LABEL=(1,SL) 
//SYSIN    DD *  
 DUMP FULL INDDNAME(SOURCE) OUTDDNAME(TARGET) -
       CONCURRENT ALLEXCP
/*

The dump will reflect whatever data was present when the concurrent copy job started.

When you see message ADR734I as shown in the following example, you can remount the partitions to the Linux system and continue using them:

ADR734I (001)-T0MI (03), 2001.168 14:38:22 CONCURRENT COPY INITIALIZATION
SUCCESSFUL FOR VOLUME LNX200. SERIALIZATION FOR THIS DATA IS RELEASED IF DFSMSDSS
HELD IT. THE INTERMEDIATE RETURN CODE IS 0000.