I am running IBM's zPDT data migration server to migrate a DASD volume from z/OS to linux (zRDT) system, and getting RACHECK failed RACROUTE RC=4, How can this error be addressed?

Document ID : KB000011854
Last Modified Date : 14/02/2018
Show Technical Document Details
Question:

I am running IBM's zPDT data migration server to migrate a DASD volume from z/OS to linux (zRDT) system,and getting RACHECK failed RACROUTE RC=4, How can this error be addressed?

Answer:

The ACF2 SECTRACE shows the 'RACHECK failed RACROUTE RC=4' is due to a RACROUTE REQUEST=AUTH,CLASS='DASDVOL',ENTITY=('HEBSTG') that is being ignored by the internal SAFDEF= DASDVOLA INTERNAL MODE= IGNORE. To address the error a SAFDEF can be INSERTed to validate(MODE=GLOBAL) the calls and rules can be written.

Sample SADFEF for ZPDTMSRV(entered from TSO, ACF): 

ACF
SET CONTROL(GSO)
INSERT SAFDEF.ZPD ID(zpd) MODE(GLOBAL) PROGRAM(ZPDT****) RB=ZPDT****)
RACROUTE(REQUEST=AUTH,CLASS=DASDVOL) 

F ACF2,REFRESH(SAFDEF) 

Note you can mask the program and RB as shown above or explicitly specify ZPDTMSRV. 

Appropriate rules should be coded for VOLUME.@volser or @volser.VOLUME format, depending on the VOLRULE|NOVOLRULE parameter specification in the GSO RULEOPTS record. In this format, volser represents the volume serial number, and VOLUME is literally the word VOLUME. 

For example if the GSO RULEOPTS specifies(the default) NOVOLRULE, the format is @volser.VOLUME: 

$KEY(@IDMT01)
volume UID(uid for logonid) R(A) W(A) 

or if GSO RULEOPTS specifies VOLRULE, the pseudo data set name format is VOLUME.@volser. 

$KEY(volume) 

@IDMT01 UID(uid for logonid) R(A) W(A)