Hello,

After some issues we were able to move volumes from existing ZOS to ZD&T.

At IPL getting folowing message :IEA347A SPECIFY MASTER CATALOG PARAMETER

Command:

IPL 5E51 parm 5E51T7

On the master console we receive the message :

OPRMSG:   *   IEA347A SPECIFY MASTER CATALOG PARAMETER
OPRMSG: Beep!
OPRMSG: PROMPT:   R 00,

The SYSCAT master is part of the LOADT7 file in SYS0.IPLPARM lib.

Best regards,

JP

Could you share the devmap and what's the ipl command you have used?

IPL 5E51 parm 5E51T7 command that we use.

devmap file :

# This file was generated at 20180831_183439 +0200

[system]
processors      3
memory  14848m
3270port        3270

[manager]
name    aws3274 0002    #define a few 3270 terminals
device  0700    3279    3274    mstcon
device  0701    3279    3274    tso1
device  0702    3279    3274    tso2
device  0703    3279    3274    tso3
device  0704    3279    3274    tso4

[manager]
name    awsrdr  010C    #define a card reader for job submission
device  00C     2540    2821    /data/VM02/zdt/volumes/../cards/*

[manager]
name    awsosa  0009    --path=A0       --pathtype=OSD  --tunnel_intf=y #QDIO mode
device  400     osa     3274    --unitadd=0
device  401     osa     3274    --unitadd=1
device  402     osa     3274    --unitadd=2

[manager]
name    awsckd  0001
device  0A83    3390    3390    /data/VM02/zdt/volumes/A3PAGC
device  0A84    3390    3390    /data/VM02/zdt/volumes/A3PAGB
device  0A85    3390    3390    /data/VM02/zdt/volumes/A3PAGA
device  0A80    3390    3390    /data/VM02/zdt/volumes/A3RES1
device  0A86    3390    3390    /data/VM02/zdt/volumes/SARES1
device  0A81    3390    3390    /data/VM02/zdt/volumes/A3RES2
device  0A87    3390    3390    /data/VM02/zdt/volumes/A3DBB1
device  0A88    3390    3390    /data/VM02/zdt/volumes/A3CFG1
device  0A89    3390    3390    /data/VM02/zdt/volumes/A3BLZ1
device  0A8A    3390    3390    /data/VM02/zdt/volumes/A3DIS1
device  0A8B    3390    3390    /data/VM02/zdt/volumes/A3USS2
device  0A8C    3390    3390    /data/VM02/zdt/volumes/A3DIS3
device  0A8D    3390    3390    /data/VM02/zdt/volumes/A3USR1
device  0A8E    3390    3390    /data/VM02/zdt/volumes/A3USS1
device  0A8F    3390    3390    /data/VM02/zdt/volumes/A3DIS2
device  0A82    3390    3390    /data/VM02/zdt/volumes/A3SYS1
device  0A90    3390    3390    /data/VM02/zdt/volumes/A3DBAR
device  0A91    3390    3390    /data/VM02/zdt/volumes/A3DBB2
device  0A92    3390    3390    /data/VM02/zdt/volumes/A3PRD3
device  0A93    3390    3390    /data/VM02/zdt/volumes/A3PRD2
device  0A94    3390    3390    /data/VM02/zdt/volumes/A3PRD1
device  5E51    3390    3390    /data/VM02/zdt/volumes/TRES25
device  501A    3390    3390    /data/VM02/zdt/volumes/COMM01
device  501F    3390    3390    /data/VM02/zdt/volumes/COMM06
device  5021    3390    3390    /data/VM02/zdt/volumes/COMM08
device  512D    3390    3390    /data/VM02/zdt/volumes/COMM12
device  5E15    3390    3390    /data/VM02/zdt/volumes/SYSIOD
device  5E18    3390    3390    /data/VM02/zdt/volumes/TCDS01
device  5E19    3390    3390    /data/VM02/zdt/volumes/TCDS02
device  5E1A    3390    3390    /data/VM02/zdt/volumes/TCKPT1
device  5E1B    3390    3390    /data/VM02/zdt/volumes/TCKPT2
device  5301    3390    3390    /data/VM02/zdt/volumes/TPAG20
device  5E33    3390    3390    /data/VM02/zdt/volumes/TPAG21
device  5E24    3390    3390    /data/VM02/zdt/volumes/TSPL01
device  5E25    3390    3390    /data/VM02/zdt/volumes/TSPL02
device  5E26    3390    3390    /data/VM02/zdt/volumes/TSPL03
device  5E27    3390    3390    /data/VM02/zdt/volumes/TSTA01
device  5E28    3390    3390    /data/VM02/zdt/volumes/TSTA02
device  5F04    3390    3390    /data/VM02/zdt/volumes/TSYS01
device  5F05    3390    3390    /data/VM02/zdt/volumes/TSYS02
device  5F07    3390    3390    /data/VM02/zdt/volumes/TSYS04
device  5F08    3390    3390    /data/VM02/zdt/volumes/TSYS05
device  5F09    3390    3390    /data/VM02/zdt/volumes/TSYS06
device  5F0A    3390    3390    /data/VM02/zdt/volumes/TSYS07
device  5F0B    3390    3390    /data/VM02/zdt/volumes/TSYS08
device  5F2A    3390    3390    /data/VM02/zdt/volumes/TSYS10
device  5F0D    3390    3390    /data/VM02/zdt/volumes/TSYS12
device  5F0F    3390    3390    /data/VM02/zdt/volumes/TSYS14
device  5F10    3390    3390    /data/VM02/zdt/volumes/TSYS15
device  5F11    3390    3390    /data/VM02/zdt/volumes/TSYS16
device  5F12    3390    3390    /data/VM02/zdt/volumes/TSYS17
device  5F13    3390    3390    /data/VM02/zdt/volumes/TSYS19
device  5F17    3390    3390    /data/VM02/zdt/volumes/TSYS23
device  5F46    3390    3390    /data/VM02/zdt/volumes/TSYS27
device  5F47    3390    3390    /data/VM02/zdt/volumes/TSYS30
device  5F19    3390    3390    /data/VM02/zdt/volumes/TSYS31
device  5F48    3390    3390    /data/VM02/zdt/volumes/TSYS32
device  5F4A    3390    3390    /data/VM02/zdt/volumes/TUSS24
device  5E34    3390    3390    /data/VM02/zdt/volumes/TPAG22
device  5E35    3390    3390    /data/VM02/zdt/volumes/TPAG23
device  5E36    3390    3390    /data/VM02/zdt/volumes/TPAG24
device  5E37    3390    3390    /data/VM02/zdt/volumes/TPAG25
device  5E38    3390    3390    /data/VM02/zdt/volumes/TPAG26
device  5E39    3390    3390    /data/VM02/zdt/volumes/TPAG27
device  5E3A    3390    3390    /data/VM02/zdt/volumes/TPAG28
device  5E3B    3390    3390    /data/VM02/zdt/volumes/TPAG29
device  5E3C    3390    3390    /data/VM02/zdt/volumes/TPAG30
device  5E3D    3390    3390    /data/VM02/zdt/volumes/TPAG31
device  5E3E    3390    3390    /data/VM02/zdt/volumes/TPAG32
device  5E3F    3390    3390    /data/VM02/zdt/volumes/TPAG33
device  5E40    3390    3390    /data/VM02/zdt/volumes/TPAG34
device  5E41    3390    3390    /data/VM02/zdt/volumes/TPAG35
device  0A96    3390    3390    /data/VM02/zdt/volumes/VOLU01
device  0A97    3390    3390    /data/VM02/zdt/volumes/VOLU02
device  0A98    3390    3390    /data/VM02/zdt/volumes/VOLU03
device  0A99    3390    3390    /data/VM02/zdt/volumes/VOLU04
device  0AA0    3390    3390    /data/VM02/zdt/volumes/VOLU05
device  0AA1    3390    3390    /data/VM02/zdt/volumes/VOLU06
device  0AA2    3390    3390    /data/VM02/zdt/volumes/VOLU07

Try this command ipl 0a80 parm 0a82cs

This is working but is not corresponding to what we like to do.

The goal is to start with the image of the existing ZOS.

Volumes has been moved respecting recommanded procedure.

Best regards.

Hi,

Did you check with your Mainframe System Administrator? 

This is below the sample of LOADAL. We are keeping LOADAL in the A3SYS1 library. That's why our command becomes ipl 0a80 parm 0a82AL where 0A82 is A3SYS1 and 0A80 is the res1 volume.

IODF     99 SYS1                                                        
INITSQA  0000M 0008M                                                    
SYSCAT   D2SYS1113CCATALOG.Z22D.MASTER                                  
SYSPARM  AL                                                             
IEASYM   00                                                             
NUCLST   00                                                             
PARMLIB  USER.Z22D.PARMLIB                            D2CFG1            
PARMLIB  FEU.Z22D.PARMLIB                             D2CFG1            
PARMLIB  ADCD.Z22D.PARMLIB                            D2SYS1            
PARMLIB  SYS1.PARMLIB                                 D2RES1            
NUCLEUS  1                                                              
SYSPLEX  ADCDPL 

I can't comment on the content of your volume. But, I feel that you are referring RES1 only.  IPL may not be able to find the you LOADT7. Could you check it again by IPLing with the command ipl 0a80 parm 0a82cs and then make necessary changes to your Load.

Sorry my mistake we use the correct ipl command I just misstiped it on the forum.

our resident : 5E51 our iodf volume where the parmlib and the main catalog is referring : 5E15 load file LOADT7 referring to the syscat.

I've added M at the end meaning message here is the result :

[ibmsys1@sfpl-zpdt-02:~]$ ipl 5E51 parm 5E15T7M -> commande lancé pour faire l'IPL　

AWSMIP008I zArchitecture IPL mode (ZARCH_ONLY=ON)　

[ibmsys1@sfpl-zpdt-02:~]$ screenOPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5900 NOT FOUND IN UDT CBDES002.　

OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5980 NOT FOUND IN UDT CBDES002.　

OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5A00 NOT FOUND IN UDT CBDES002.　

OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5A80 NOT FOUND IN UDT CBDES002.　

OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5B00 NOT FOUND IN UDT CBDES002.　

OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5B80 NOT FOUND IN UDT CBDES002.　

OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5C00 NOT FOUND IN UDT CBDES002.　

OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5C80 NOT FOUND IN UDT CBDES002.　

OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5D00 NOT FOUND IN UDT CBDES002.　

OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5D80 NOT FOUND IN UDT CBDES002.　

OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5E00 NOT FOUND IN UDT CBDES002.　

OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5E80 NOT FOUND IN UDT CBDES002.　

OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5F00 NOT FOUND IN UDT CBDES002.　

OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5F80 NOT FOUND IN UDT CBDES002.　

OPRMSG: IEA524I NO DEVICES DEFINED FOR SUBCHANNEL SET 1　

OPRMSG: IEA091I NUCLEUS 1 SELECTED　

-OPRMSG: * IEA347A SPECIFY MASTER CATALOG PARAMETER　

OPRMSG: Beep!　

OPRMSG: PROMPT: R 00,

Is 5E51 where your SYS1.IPLPARM is? This needs to be the device you are referring to:

IPL sysres_device PARM sys1.iplparm_device

If you IPL with the standard ADCD, i.e. IPL 0a80 parm 0a8200, you can logon to the system and under 3.4, look at volume TRES25 to check that the required datasets are in fact there and set-up correctly including your LOADxx member.

Sebastian

Hello Sebastian,

Yes if I start from the zdnt default ipl command no problem. I boot on the zdnt system with volumes created vi ADCD.

What we are trying to do here boot on our copie of our main production z/os. to do this we have copied all volumes and put them on the zdnt.

so we will not use the resident from the zdnt to boot but the copied resident from our production mainframe.

problem seems to come from the catalog.

I don't know if we can start the ipl without the catalog just to be sure that system can be boot.

Regards,

David

Add a T or M IMSI character to the back of your load parms

It was still done before these are the messages:

[ibmsys1@sfpl-zpdt-02:~]$
ipl 5E51 parm 5E15T7M -> IPL Command
AWSMIP008I zArchitecture IPL mode (ZARCH_ONLY=ON) 
[ibmsys1@sfpl-zpdt-02:~]$ screen
OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5900 NOT FOUND IN UDT CBDES002. 
OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5980 NOT FOUND IN UDT CBDES002. 
OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5A00 NOT FOUND IN UDT CBDES002. 
OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5A80 NOT FOUND IN UDT CBDES002. 
OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5B00 NOT FOUND IN UDT CBDES002. 
OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5B80 NOT FOUND IN UDT CBDES002. 
OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5C00 NOT FOUND IN UDT CBDES002. 
OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5C80 NOT FOUND IN UDT CBDES002. 
OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5D00 NOT FOUND IN UDT CBDES002. 
OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5D80 NOT FOUND IN UDT CBDES002. 
OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5E00 NOT FOUND IN UDT CBDES002. 
OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5E80 NOT FOUND IN UDT CBDES002. 
OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5F00 NOT FOUND IN UDT CBDES002. 
OPRMSG: CBDA381I PARAMETER 34 FOR DEVICE 5F80 NOT FOUND IN UDT CBDES002. 
OPRMSG: IEA524I NO DEVICES DEFINED FOR SUBCHANNEL SET 1 
OPRMSG: IEA091I NUCLEUS 1 SELECTED 
-OPRMSG: * IEA347A SPECIFY MASTER CATALOG PARAMETER 
OPRMSG: Beep! 
OPRMSG: PROMPT: R 00,