30.09.2012 Views

z/OS MVS System Initialization Logic - Messmer The Brain House

z/OS MVS System Initialization Logic - Messmer The Brain House

z/OS MVS System Initialization Logic - Messmer The Brain House

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

DASD Pathing…<br />

� Dynamic Pathing Error Messages…<br />

Zürich | 26. Oktober 2004<br />

NIP Resource <strong>Initialization</strong><br />

IGGN505A SPECIFY UNIT FOR SYS1.PRODXY.LINKLIB ON DCSYS2 OR CANCEL<br />

R 00,1A60<br />

IEE600I REPLY TO 00 IS;1A60<br />

If the busy condition still exists I<strong>OS</strong>120A will be issued<br />

*I<strong>OS</strong>120A DEVICE 1A60 SHARED, REPLY ‘CONT‘ OR ‘WAIT‘<br />

I<strong>OS</strong>600I REPLY TO 00 IS ‘WAIT‘<br />

*I<strong>OS</strong>124A STILL WAITING FOR RESPONSE FROM DEVICE 1A60, TOTAL WAIT TIME<br />

IS 46 SECONDS, REPLY ‘CONT‘ OR ‘WAIT‘<br />

*I<strong>OS</strong>120A DEVICE 1A60 SHARED, REPLY ‘CONT‘ OR ‘WAIT‘<br />

I<strong>OS</strong>600I REPLY TO 00 IS ‘WAIT‘<br />

IGGN306I 1A60,UNIT UNACCEPTABLE, 00000004<br />

IGGN505A SPECIFY UNIT FOR SYS1.PRODXY.LINKLIB ON DCSYS2 OR CANCEL<br />

IGGN504A or IGGN505A message issued if required dataset is on a volume that was busy during DASD<br />

pathing and the dataset is required for the IPL to complete<br />

Issue D U,VOL=vvvvvv on an active system that shares the DASD device to obtain the device number<br />

associated with the VOLSER<br />

© 2004 IBM Corporation 25

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!