Re: Re: Problems with IPL-ing 1.13 ( again)

>The issue is the following, in my files, somewhere between the disks, I also have 2 conf files which I used and ***were working.***

"were working".

What has changed ?    (external drive ? )


Mike

On 5/25/19, gheorghedragos1988-/[email protected] [hercules-390]
<[email protected]> wrote:
> Mike,
>
>
>  Many thanks for taking your time to read my painful story. The issue is the
> following, in my files, somewhere between the disks, I also have 2 conf
> files which I used and were working. Both have these lines :
>
>
>
>  ARCHMODE             z/Arch # (Hercules 3.x)
> ALRF                 DISABLE
>
>
>  When I copy these lines to new conf file with new setup ( dir paths etc ),
> Hercules tells me that these two lines are invalid. Could it be Hercules
> probem ? And the file suffix it should be ok also, as he MEGA and MEGAZFS
> disks are created by me and could be mounted without any issues.
>
>  Again, I used the DASDDLS and DASDCAT utilities, the IODF and IPLPARM
> datasets are there(also the disk file can be read so a corruption is out of
> question ) . Such as :
>
>
>
> 09:36:48.343 00002994 SYS1.RACFDS
> 09:36:48.343 00002994 SYS1.IPLPARM
> 09:36:48.343 00002994 SYS1.SMS.CNTL
> 09:36:48.343 00002994 SYS1.ACDS.DATA
> 09:36:48.343 00002994 SYS1.IODF00
> 09:36:48.343 00002994 SYS1.IODF01
> 09:36:48.343 00002994 SYS1.IODF99
>
>
>  and DASDCAT SYS1.IPLPARM shows
>
>
>
>  09:37:48.511 00000560 loadac
> 09:37:48.511 00000560 loadaw
> 09:37:48.511 00000560 loadcc
> 09:37:48.511 00000560 loadcs
> 09:37:48.511 00000560 loadcw
> 09:37:48.511 00000560 loaddc
> 09:37:48.511 00000560 loaddw
> 09:37:48.511 00000560 loadhc
> 09:37:48.511 00000560 loadhw
> 09:37:48.511 00000560 loadic
> 09:37:48.511 00000560 loadiw
> 09:37:48.511 00000560 loadws
> 09:37:48.511 00000560 load00
> 09:37:48.511 00000560 load1c
> 09:37:48.511 00000560 load1w
> 09:37:48.511 00000560 load4c
> 09:37:48.511 00000560 load4w
> 09:37:48.511 00000560 load7c
> 09:37:48.511 00000560 load7w
> 09:37:48.511 00000560 load8c
> 09:37:48.511 00000560 load8w
> 09:37:48.511 00000560 load9c
> 09:37:48.511 00000560 load9w
> 09:37:48.511 00000560 nuclst00
>
>
>
>  and yet when I try to IPL from SDRES1 with loadparm, again, pointing to
> SDSYS1 0380AW.. or 0380AWM1 gives me :
>
>
>
>  09:39:11.004 00000E44 loadparm
> 09:39:11.004 00000E44 HHCPN051I LOADPARM=0380AW
> 09:39:20.060 00000E44 loadparm 0380csm1
> 09:40:13.563 00000E44 ipl 37e
> 09:40:13.563 00000E44 HHCCP007I CPU0000 architecture mode set to ESA/390
> 09:40:13.563 00000E44 CPU0000: SIGP Set architecture mode (12) CPU0000, PARM
> 00000001: CC 0
> 09:40:13.564 00000E44 HHCCP007I CPU0000 architecture mode set to z/Arch
> 09:40:13.570 00000E44 CPU0000: SIGP Unassigned (14) CPU0000, PARM
> 0000000064000000: CC 1 STATUS 00000002
> 09:40:15.584 00000E44 HHCCP011I CPU0000: Disabled wait state
> 09:40:15.584 00000E44           PSW=00020000 00000000 0000000000000031
>
>
>
>  and IBM website for 0031 shows us
>
>
>
>  031 Explanation The system did not find a unit control block for the device
> containing the system residence (SYSRES) volume, for one of the following
> reasons: The system was IPLed using the wrong SYSRES volume The SYSRES
> volume was not specified in the I/O configuration definition The system did
> not select the desired I/O configuration. But I ask .. how is this possible,
> since the configuration is pointing in the right location ( SYS RES UCB).
>
>
>  ......
>
>
>
>
>
>