zVM 6.4 on Hercules 3.12 does not start

classic Classic list List threaded Threaded
27 messages Options
12
Reply | Threaded
Open this post in threaded view
|

zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
Hi listers,

I have restored a zvm 6.4 runing on a system z to my hercules 3.12. When I start it I get these messages:
A zvm 6.30 starts without problems on the same hercules version and configuration.

09:15:22 z/VM  V6 R4.0  SERVICE LEVEL 1601 (64-BIT)
09:15:23 SYSTEM NUCLEUS CREATED ON 2017-03-21 AT 07:00:53, LOADED FROM 640RES
09:15:23
09:15:23 ****************************************************************
09:15:23 * LICENSED MATERIALS - PROPERTY OF IBM*                        *
09:15:23 *                                                              *
09:15:23 * 5741-A07 (C) COPYRIGHT IBM CORP. 1983, 2016. ALL RIGHTS      *
09:15:23 * RESERVED. US GOVERNMENT USERS RESTRICTED RIGHTS - USE,       *
09:15:23 * DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE     *
09:15:23 * CONTRACT WITH IBM CORP.                                      *
09:15:23 *                                                              *
09:15:23 * * TRADEMARK OF INTERNATIONAL BUSINESS MACHINES.              *
09:15:23 ****************************************************************
09:15:23
 09:15:23 HCPZCO6718I Using parm disk 1 on volume 64COM1 (device 0643).
 09:15:23 HCPZCO6718I Parm disk resides on cylinders 1 through 120.
09:15:23 Start ((Warm!Force!COLD!CLEAN) (DRain) (DIsable)  (NODIRect)
09:15:23       (NOAUTOlog)) or (SHUTDOWN)
09:28:00
09:28:00 NOW 09:28:00 EDT WEDNESDAY 2017-03-22
09:28:00 Change TOD clock (Yes!No)
09:28:02
09:28:02 HCPERP500I  DASD  0640 AN OPERATION WAS TERMINATED BECAUSE A
09:28:02 HCPERP500I  COMMAND REJECT ERROR OCCURRED
09:28:02 HCPERP6300I SENSE DATA FORMAT = 00       MSG CODE = 01
09:28:02 HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = N/A HPF
09:28:02 HCPERP6302I SEEK ADDRESS =   000000000000
09:28:02 HCPERP6303I SENSE = 80000000 00FFFF01 00000000 00000000 00000000
09:28:02 HCPERP6303I 00000000 00000080 00000000
09:28:02 HCPERP6304I IRB = 00C24017 1FDDD008 0E400040 00800000
09:28:02 HCPERP6305I USERID = SYSTEM
09:28:02 HCPERP2216I CHANNEL PATH ID = 06
09:28:02 HCPUDS1777E The directory on volume 640RES could not be initialized.
09:28:02 HCPUDS1752E No directory could be initialized.
09:28:02 HCPERP500I  DASD  0640 AN OPERATION WAS TERMINATED BECAUSE A
09:28:02 HCPERP500I  COMMAND REJECT ERROR OCCURRED
09:28:02 HCPERP6300I SENSE DATA FORMAT = 00       MSG CODE = 01
09:28:02 HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = N/A HPF
09:28:02 HCPERP6302I SEEK ADDRESS =   000000000000
09:28:02 HCPERP6303I SENSE = 80000000 00FFFF01 00000000 00000000 00000000
09:28:02 HCPERP6303I 00000000 00000080 00000000
09:28:12 HCPWRP959I ZVM6401  SYSTEM TERMINATION IN PROGRESS ON 2017-03-22

I think the HCPERP500I command reject is the relevant msg. Before restoring it from a running system I have tried to install it in second level. The installation ran successfully until the restart before the postload activities. During this ipl there were the same error msgs as above. I first thought it is because of a problem with the installation material. Therefore I installed it with the same installation dvd on a real z and it worked without problems. Then I have done a ddr backup and restored it to my hercules. I got the same error again as with the second level installation. What might be wrong? Does zvm 6.4 do things other during ipl as zvm 6.3?

I tried then to start with hercules 4.00 rc0 (downloaded yesterday) but on this version I cannot get any zvm up and running neither 6.4 nor 6.3. I get the following error

HCPRFI9030W CP REQUIRES HARDWARE FEATURES NOT AVAILABLE ON THIS PROCESSOR.                                        
HHC00809I Processor CP00: disabled wait state 0002000000000000 0000000000009030    
 

 Does anybody have an idea on problem 1 (zvm 6.4 on Hercules 3.12) or problem 2 (any zvm on hercules 4.00 RC0)?
 

 I assume that Hercules 4.00 is currently not ready to run zvm. Right?

 

 

 

 Here is my hercules config
 #
# Hercules Emulator Control file...
# Description: Standalone DDR
# MaxShutdownSecs: 99
#
#
# System parameters
#

CPUSERIAL 004920
CPUMODEL  2965                # CPU model number
MAINSIZE  2048
CNSLPORT  3270
NUMCPU    4
# ARCHMODE  ESA/390
ARCHLVL   z/ARCH
ARCHLVL   ENABLE
ARCHLVL   ENABLE PROBSTATE_DIAGF08
ARCHLVL   ENABLE VIRTUAL_MACHINE
ARCHLVL   ENABLE QDIO_ASSIST
ARCHLVL   ENABLE QDIO_TDD
ARCHLVL   ENABLE asn_lx_reuse
DIAG8CMD  ENABLE
ECPSVM    ENABLE
LOADPARM  0A00....
LPARNUM   1
LPARNAME  ZVM1
SYSEPOCH  1900
TZOFFSET  +0100
OSTAILOR  QUIET
PANRATE   1000
PGMPRDOS  LICENSED
DEVTMAX   150
# neue Prio-Werte ab Version 3.05
HERCPRIO  0
TODPRIO   -20
DEVPRIO   8
CPUPRIO   15
# alte Werte vor offizieller Version 3.05
# HERCPRIO     0
# DEVPRIO     -8
# TODPRIO      0
# CPUPRIO      0
# Card Readers

#000C    3505    e:/daten/ipl390/standalone/iplddrxa.rdr ebcdic
#001C    3505    e:/daten/ipl390/standalone/iplickdsf.rdr ebcdic
#002C    3505    e:/daten/ipl390/standalone/iplsalipl.rdr ebcdic

# Line Printers

000E    1403    d:/temp/prt00e.txt crlf

# DASD Devices

#0430    3390    E:/daten/ipl390/dasd/430res.zvm cu=3990   sf=E:/daten/ipl390/dasd/430res_1.zvm
#0431    3390    E:/daten/ipl390/dasd/430w01.zvm cu=3990   sf=E:/daten/ipl390/dasd/430w01_1.zvm
#0432    3390    E:/daten/ipl390/dasd/430w02.zvm cu=3990   sf=E:/daten/ipl390/dasd/430w02_1.zvm
#0433    3390    E:/daten/ipl390/dasd/430w03.zvm cu=3990   sf=E:/daten/ipl390/dasd/430w03_1.zvm
#0440    3390    E:/daten/ipl390/dasd/440res.zvm cu=3990   sf=E:/daten/ipl390/dasd/440res_1.zvm
#0441    3390    E:/daten/ipl390/dasd/440w01.zvm cu=3990   sf=E:/daten/ipl390/dasd/440w01_1.zvm
#0442    3390    E:/daten/ipl390/dasd/440w02.zvm cu=3990   sf=E:/daten/ipl390/dasd/440w02_1.zvm
0600    3390    E:/daten/ipl390/dasd/VSErs1.zvm cu=3990   sf=E:/daten/ipl390/dasd/VSErs1_1.zvm
0601    3390    E:/daten/ipl390/dasd/VSErs2.zvm cu=3990   sf=E:/daten/ipl390/dasd/VSErs2_1.zvm
0602    3390    E:/daten/ipl390/dasd/VSEsys.zvm cu=3990   sf=E:/daten/ipl390/dasd/VSEsys_1.zvm
0603    3390    E:/daten/ipl390/dasd/VSEVSM.zvm cu=3990   sf=E:/daten/ipl390/dasd/VSEVSM_1.zvm
0604    3380    E:/daten/ipl390/dasd/VSE231.zvm cu=3990   sf=E:/daten/ipl390/dasd/VSE231_1.zvm
0605    3380    E:/daten/ipl390/dasd/VSE232.zvm cu=3990   sf=E:/daten/ipl390/dasd/VSE232_1.zvm
0606    3380    E:/daten/ipl390/dasd/VSEDAT.zvm cu=3990   sf=E:/daten/ipl390/dasd/VSEDAT_1.zvm
0607    3390    E:/daten/ipl390/dasd/V31RES.zvm cu=3990   sf=E:/daten/ipl390/dasd/V31RES_1.zvm
0608    3390    E:/daten/ipl390/dasd/V31WK1.zvm cu=3990   sf=E:/daten/ipl390/dasd/V31WK1_1.zvm
0609    3390    E:/daten/ipl390/dasd/V41RSA.zvm cu=3990   sf=E:/daten/ipl390/dasd/V41RSA_1.zvm
060A    3390    E:/daten/ipl390/dasd/V41W1A.zvm cu=3990   sf=E:/daten/ipl390/dasd/V41W1A_1.zvm
060B    3390    E:/daten/ipl390/dasd/VSESY1.zvm cu=3990   sf=E:/daten/ipl390/dasd/VSESY1_1.zvm
060C    3390    E:/daten/ipl390/dasd/VSESY2.zvm cu=3990   sf=E:/daten/ipl390/dasd/VSESY2_1.zvm
060D    3390    E:/daten/ipl390/dasd/VSESY3.zvm cu=3990   sf=E:/daten/ipl390/dasd/VSESY3_1.zvm
060E    3390    E:/daten/ipl390/dasd/VTAP01.zvm cu=3990   sf=E:/daten/ipl390/dasd/VTAP01_1.zvm
0619    3390    E:/daten/ipl390/dasd/V41RSB.zvm cu=3990   sf=E:/daten/ipl390/dasd/V41RSB_1.zvm
061A    3390    E:/daten/ipl390/dasd/V41W1B.zvm cu=3990   sf=E:/daten/ipl390/dasd/V41W1B_1.zvm
511A    3390    E:/daten/ipl390/dasd/V51RES.zvm cu=3990   sf=E:/daten/ipl390/dasd/V51RES_1.zvm
511B    3390    E:/daten/ipl390/dasd/V51WK1.zvm cu=3990   sf=E:/daten/ipl390/dasd/V51WK1_1.zvm
512A    3390    E:/daten/ipl390/dasd/VSE512.zvm cu=3990   sf=E:/daten/ipl390/dasd/VSE512_1.zvm
0700    3390    E:/daten/ipl390/dasd/zvmadd.zvm cu=3990   sf=E:/daten/ipl390/dasd/zvmadd_1.zvm
0701    3390    E:/daten/ipl390/dasd/cmswk1.zvm cu=3990   sf=E:/daten/ipl390/dasd/cmswk1_1.zvm
0702    3390    E:/daten/ipl390/dasd/BCUSR1.zvm cu=3990   sf=E:/daten/ipl390/dasd/BCUSR1_1.zvm
0703    3390    E:/daten/ipl390/dasd/T33901.zvm cu=3990
0704    3390    E:/daten/ipl390/dasd/cmswk2.zvm cu=3990   sf=E:/daten/ipl390/dasd/cmswk2_1.zvm
0705    3390    E:/daten/ipl390/dasd/cmswk3.zvm cu=3990   sf=E:/daten/ipl390/dasd/cmswk3_1.zvm
0706    3390    E:/daten/ipl390/dasd/BCUSR2.zvm cu=3990   sf=E:/daten/ipl390/dasd/BCUSR2_1.zvm
# VM-Systeme
0530    3390    E:/daten/ipl390/dasd/530res.zvm cu=3990   sf=E:/daten/ipl390/dasd/530res_1.zvm
0531    3390    E:/daten/ipl390/dasd/530pag.zvm cu=3990   sf=E:/daten/ipl390/dasd/530pag_1.zvm
0532    3390    E:/daten/ipl390/dasd/530spl.zvm cu=3990   sf=E:/daten/ipl390/dasd/530spl_1.zvm
0533    3390    E:/daten/ipl390/dasd/530w01.zvm cu=3990   sf=E:/daten/ipl390/dasd/530w01_1.zvm
0540    3390    E:/daten/ipl390/dasd/540res.zvm cu=3990   sf=E:/daten/ipl390/dasd/540res_1.zvm
0541    3390    E:/daten/ipl390/dasd/540pag.zvm cu=3990   sf=E:/daten/ipl390/dasd/540pag_1.zvm
0542    3390    E:/daten/ipl390/dasd/540spl.zvm cu=3990   sf=E:/daten/ipl390/dasd/540spl_1.zvm
0620    3390    E:/daten/ipl390/dasd/m01res.zvm62 cu=3990   sf=E:/daten/ipl390/dasd/m01res_1.zvm62
0621    3390    E:/daten/ipl390/dasd/m01s01.zvm62 cu=3990   sf=E:/daten/ipl390/dasd/m01s01_1.zvm62
0622    3390    E:/daten/ipl390/dasd/m01p01.zvm62 cu=3990   sf=E:/daten/ipl390/dasd/m01p01_1.zvm62
0623    3390    E:/daten/ipl390/dasd/vmcom1.zvm62 cu=3990   sf=E:/daten/ipl390/dasd/vmcom1_1.zvm62
0624    3390    E:/daten/ipl390/dasd/620rl1.zvm62 cu=3990   sf=E:/daten/ipl390/dasd/620rl1_1.zvm62
0630    3390    E:/daten/ipl390/dasd/630res.zvm cu=3990   sf=E:/daten/ipl390/dasd/630res_1.zvm
0631    3390    E:/daten/ipl390/dasd/630pg1.zvm cu=3990   sf=E:/daten/ipl390/dasd/630pg1_1.zvm
0632    3390    E:/daten/ipl390/dasd/630sp1.zvm cu=3990   sf=E:/daten/ipl390/dasd/630sp1_1.zvm
0633    3390    E:/daten/ipl390/dasd/630com.zvm cu=3990   sf=E:/daten/ipl390/dasd/630com_1.zvm
0634    3390    E:/daten/ipl390/dasd/630rl1.zvm cu=3990   sf=E:/daten/ipl390/dasd/630rl1_1.zvm
0635    3390    E:/daten/ipl390/dasd/630w01.zvm cu=3990   sf=E:/daten/ipl390/dasd/630w01_1.zvm
0640    3390    E:/daten/ipl390/dasd/640res.zvm cu=3990   sf=E:/daten/ipl390/dasd/640res_1.zvm
0641    3390    E:/daten/ipl390/dasd/640s01.zvm cu=3990   sf=E:/daten/ipl390/dasd/640s01_1.zvm
0642    3390    E:/daten/ipl390/dasd/640p01.zvm cu=3990   sf=E:/daten/ipl390/dasd/640p01_1.zvm
0643    3390    E:/daten/ipl390/dasd/64com1.zvm cu=3990   sf=E:/daten/ipl390/dasd/64com1_1.zvm
0644    3390    E:/daten/ipl390/dasd/640rl1.zvm cu=3990   sf=E:/daten/ipl390/dasd/640rl1_1.zvm
0645    3390    E:/daten/ipl390/dasd/640W01.zvm cu=3990   sf=E:/daten/ipl390/dasd/640W01_1.zvm
FF01    3390    E:/daten/ipl390/dasd/TEMP01.zvm cu=3990   sf=E:/daten/ipl390/dasd/TEMP01_1.zvm
FF02    3390    E:/daten/ipl390/dasd/TEMP02.zvm cu=3990   sf=E:/daten/ipl390/dasd/TEMP02_1.zvm
# Test für VSEDASD-Rexx
FF03    3390    E:/daten/ipl390/dasd/TEMP03.zvm  cu=3990   sf=E:/daten/ipl390/dasd/TEMP03_1.zvm
# WM SE VSE01 Systemplatten für FSU
FF10    3390    E:/daten/ipl390/dasd/WMVS01.zvm  cu=3990   sf=E:/daten/ipl390/dasd/WMVS01_1.zvm
FF99    3390    E:/daten/ipl390/dasd/VTAP01.zvmx cu=3990   sf=E:/daten/ipl390/dasd/VTAP01_1.zvmx
*
# Pagespace
3000    3390    e:/daten/ipl390/dasd/BGETM1.zVM   cu=3990 sf=e:/daten/ipl390/dasd/BGETM1_1.zvm
3001    3390    e:/daten/ipl390/dasd/BGETM2.zVM   cu=3990 sf=e:/daten/ipl390/dasd/BGETM2_1.zvm
# TAPE Devices

0181    3490    *
0182    3490    *
0183    3490    *
0184    3490    *

# 3270 Display

0A00    3270 ZVMCONS
0A01    3270
0A02    3270
0A03    3270
00F0    3270 zos
00F1    3270 zos
00F3    3270 zos
0040    3270 CONSOLE

# Network Connection
# zVM
1000-1001 ctci -k 1024 -i 128 -n 42-00-47-11-08-15 192.168.147.1 0.0.0.0
1002-1003 ctci -n 42-00-47-11-08-15 192.168.147.2 0.0.0.0
1004-1005 ctci -n 42-00-47-11-08-15 192.168.147.3 0.0.0.0
1006-1007 ctci -n 42-00-47-11-08-15 192.168.147.4 0.0.0.0
1008-1009 ctci -n 42-00-47-11-08-15 192.168.147.5 0.0.0.0
 

 Thanks in advance for your help
 Franz Josef

 

Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
Hi Franz,

Answer to question #1
I can run z/VM 6.4 on Hercules 3.12 and even on Hercules 3.11 without any problem.

Answer to question #2

I don't use Hercules 4.0 as I had many problems with the last versions of z/VM and z/OS...

Perhaps it's better to discuss further this matter privately :-)

My mail is

crc*at*alce1.tuttopmi.it ('*at*' stands for '@')

Regards

Paul
Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
In reply to this post by Hercules390 - General mailing list

> HCPRFI9030W CP REQUIRES HARDWARE FEATURES NOT AVAILABLE ON THIS
> PROCESSOR.
> HHC00809I Processor CP00: disabled wait state 0002000000000000
> 0000000000009030
Franz,

Try "ARCHLVL ENABLE BIT44" under hercules 4.00

--Ivan



[Non-text portions of this message have been removed]

Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
In reply to this post by Hercules390 - General mailing list
You don’t need to put your e-mail address into the post. When viewing e-mails its in the bottom of the mail.

On the web site click “reply”, then to the left of the subject there are two “V” signs nested inside one another,

click on that and the header expands to show the “to” field in a drop down box.

There are five options,

 

1. The Group
2. The sender
3. The sender and the group
4. The Group Owner (moderators)
5. The Group Owner and the sender.

 

Number 2 allows you to reply to the sender.

 

Dave

 

 

From: [hidden email] [mailto:[hidden email]]
Sent: 23 March 2017 11:59
To: [hidden email]
Subject: [hercules-390] Re: zVM 6.4 on Hercules 3.12 does not start

 



Hi Franz,

Answer to question #1
I can run z/VM 6.4 on Hercules 3.12 and even on Hercules 3.11 without any problem.

Answer to question #2

I don't use Hercules 4.0 as I had many problems with the last versions of z/VM and z/OS...

Perhaps it's better to discuss further this matter privately :-)

My mail is

crc*at*alce1.tuttopmi.it ('*at*' stands for '@')

Regards

Paul






Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
Thanks,

I'm trying this method with you :-)

Regards

Paul
Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
In reply to this post by Hercules390 - General mailing list
>You don’t need to put your e-mail address into the post. When viewing e-mails its in the bottom of the mail.
 On the web site click “reply”, then to the left of the subject there are two “V” signs nested inside one another,
 click on that and the header expands to show the “to” field in a drop down box.
 There are five options,
 
 The Group The sender The sender and the group The Group Owner (moderators) The Group Owner and the sender.  
 Number 2 allows you to reply to the sender.
 
 >Dave
 

 Thanks!
 

 I'm trying this method with you :-)
 

 Paul

Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
In reply to this post by Hercules390 - General mailing list
Hello Ivan,

I have tried your recommendation ARCHLVL ENABLE BIT44. The msg
HCPRFI9030W doesn't appear any longer but now after the standalone
loader screen and PF10 there is an X SYSTEM in the emulation window and
suddenly afterwards a PROG708. This means that an SNA msg was received
before the begin of the data transmission. I use Personal Communication
as a console emulation as always and had never problems before.


Any help is welcome.

--
kind regards
Franz Josef Pohlen

Am 23.03.2017 um 14:21 schrieb Ivan Warren [hidden email]
[hercules-390]:

> > HCPRFI9030W CP REQUIRES HARDWARE FEATURES NOT AVAILABLE ON THIS
> > PROCESSOR.
> > HHC00809I Processor CP00: disabled wait state 0002000000000000
> > 0000000000009030
> Franz,
>
> Try "ARCHLVL ENABLE BIT44" under hercules 4.00
>
> --Ivan
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
> Posted by: Ivan Warren <[hidden email]>
> ------------------------------------
>
> Community email addresses:
>    Post message: [hidden email]
>    Subscribe:    [hidden email]
>    Unsubscribe:  [hidden email]
>    List owner:   [hidden email]
>
> Files and archives at:
>    http://groups.yahoo.com/group/hercules-390
>
> Get the latest version of Hercules from:
>    http://www.hercules-390.org
>
>
> ------------------------------------
>
> Yahoo Groups Links
>
>
>
>





------------------------------------

------------------------------------

Community email addresses:
  Post message: [hidden email]
  Subscribe:    [hidden email]
  Unsubscribe:  [hidden email]
  List owner:   [hidden email]

Files and archives at:
  http://groups.yahoo.com/group/hercules-390

Get the latest version of Hercules from:
  http://www.hercules-390.org


------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/hercules-390/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/hercules-390/join
    (Yahoo! ID required)

<*> To change settings via email:
    [hidden email]
    [hidden email]

<*> To unsubscribe from this group, send an email to:
    [hidden email]

<*> Your use of Yahoo Groups is subject to:
    https://info.yahoo.com/legal/us/yahoo/utos/terms/

Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
Hello all,

as the Hercules 4.0 doesn't seem to be working for the current zvm. I
will try to get the zvm 6.4 running with Hercules 3.12 (Win 64Bit). I
get an error during IPL after I have confirmed the time question. It
cancels with command reject on the IPL device. For documentation I have
started a ccw trace on the ipl device and ipled the zvm 6.4 with
cons=sysc. So the zVM messages and the ccw trace is in the log. I hope
that someone of you developers can see there what's going wrong. My old
zvm 6.3 starts without problems on this hercules configuration. I have
also attached my hercules config. There might still be some settings for
Hercules 4.0 but they were ignored during start with Hercules 3.12.

Thanks in advance for your help and have a nice weekend

Franz Josef

Hercules Config

#
# Hercules Emulator Control file...
# Description: Standalone DDR
# MaxShutdownSecs: 99
#
#
# System parameters
#

CPUSERIAL 004920
CPUMODEL  2965                # CPU model number
MAINSIZE  2048
CNSLPORT  3270
NUMCPU    4
# ARCHMODE  ESA/390
ARCHLVL   z/ARCH
ARCHLVL   ENABLE
ARCHLVL   ENABLE PROBSTATE_DIAGF08
ARCHLVL   ENABLE VIRTUAL_MACHINE
ARCHLVL   ENABLE QDIO_ASSIST
ARCHLVL   ENABLE QDIO_TDD
ARCHLVL   ENABLE asn_lx_reuse
ARCHLVL   ENABLE BIT44
DIAG8CMD  ENABLE
ECPSVM    ENABLE
LOADPARM  0A00....
LPARNUM   1
LPARNAME  ZVM1
SYSEPOCH  1900
TZOFFSET  +0100
OSTAILOR  QUIET
PANRATE   1000
PGMPRDOS  LICENSED
DEVTMAX   150
# neue Prio-Werte ab Version 3.05
HERCPRIO  0
TODPRIO   -20
DEVPRIO   8
CPUPRIO   15
# alte Werte vor offizieller Version 3.05
# HERCPRIO     0
# DEVPRIO     -8
# TODPRIO      0
# CPUPRIO      0
# cckd parameter
# cckd compparm=5
# Card Readers

#000C    3505    e:/daten/ipl390/standalone/iplddrxa.rdr ebcdic
#001C    3505    e:/daten/ipl390/standalone/iplickdsf.rdr ebcdic
#002C    3505    e:/daten/ipl390/standalone/iplsalipl.rdr ebcdic

# Line Printers

000E    1403    d:/temp/prt00e.txt crlf

# DASD Devices

#0430    3390    E:/daten/ipl390/dasd/430res.zvm cu=3990
sf=E:/daten/ipl390/dasd/430res_1.zvm
#0431    3390    E:/daten/ipl390/dasd/430w01.zvm cu=3990
sf=E:/daten/ipl390/dasd/430w01_1.zvm
#0432    3390    E:/daten/ipl390/dasd/430w02.zvm cu=3990
sf=E:/daten/ipl390/dasd/430w02_1.zvm
#0433    3390    E:/daten/ipl390/dasd/430w03.zvm cu=3990
sf=E:/daten/ipl390/dasd/430w03_1.zvm
#0440    3390    E:/daten/ipl390/dasd/440res.zvm cu=3990
sf=E:/daten/ipl390/dasd/440res_1.zvm
#0441    3390    E:/daten/ipl390/dasd/440w01.zvm cu=3990
sf=E:/daten/ipl390/dasd/440w01_1.zvm
#0442    3390    E:/daten/ipl390/dasd/440w02.zvm cu=3990
sf=E:/daten/ipl390/dasd/440w02_1.zvm
0600    3390    E:/daten/ipl390/dasd/VSErs1.zvm cu=3990
sf=E:/daten/ipl390/dasd/VSErs1_1.zvm
0601    3390    E:/daten/ipl390/dasd/VSErs2.zvm cu=3990
sf=E:/daten/ipl390/dasd/VSErs2_1.zvm
0602    3390    E:/daten/ipl390/dasd/VSEsys.zvm cu=3990
sf=E:/daten/ipl390/dasd/VSEsys_1.zvm
0603    3390    E:/daten/ipl390/dasd/VSEVSM.zvm cu=3990
sf=E:/daten/ipl390/dasd/VSEVSM_1.zvm
0604    3380    E:/daten/ipl390/dasd/VSE231.zvm cu=3990
sf=E:/daten/ipl390/dasd/VSE231_1.zvm
0605    3380    E:/daten/ipl390/dasd/VSE232.zvm cu=3990
sf=E:/daten/ipl390/dasd/VSE232_1.zvm
0606    3380    E:/daten/ipl390/dasd/VSEDAT.zvm cu=3990
sf=E:/daten/ipl390/dasd/VSEDAT_1.zvm
0607    3390    E:/daten/ipl390/dasd/V31RES.zvm cu=3990
sf=E:/daten/ipl390/dasd/V31RES_1.zvm
0608    3390    E:/daten/ipl390/dasd/V31WK1.zvm cu=3990
sf=E:/daten/ipl390/dasd/V31WK1_1.zvm
0609    3390    E:/daten/ipl390/dasd/V41RSA.zvm cu=3990
sf=E:/daten/ipl390/dasd/V41RSA_1.zvm
060A    3390    E:/daten/ipl390/dasd/V41W1A.zvm cu=3990
sf=E:/daten/ipl390/dasd/V41W1A_1.zvm
060B    3390    E:/daten/ipl390/dasd/VSESY1.zvm cu=3990
sf=E:/daten/ipl390/dasd/VSESY1_1.zvm
060C    3390    E:/daten/ipl390/dasd/VSESY2.zvm cu=3990
sf=E:/daten/ipl390/dasd/VSESY2_1.zvm
060D    3390    E:/daten/ipl390/dasd/VSESY3.zvm cu=3990
sf=E:/daten/ipl390/dasd/VSESY3_1.zvm
060E    3390    E:/daten/ipl390/dasd/VTAP01.zvm cu=3990
sf=E:/daten/ipl390/dasd/VTAP01_1.zvm
0619    3390    E:/daten/ipl390/dasd/V41RSB.zvm cu=3990
sf=E:/daten/ipl390/dasd/V41RSB_1.zvm
061A    3390    E:/daten/ipl390/dasd/V41W1B.zvm cu=3990
sf=E:/daten/ipl390/dasd/V41W1B_1.zvm
511A    3390    E:/daten/ipl390/dasd/V51RES.zvm cu=3990
sf=E:/daten/ipl390/dasd/V51RES_1.zvm
511B    3390    E:/daten/ipl390/dasd/V51WK1.zvm cu=3990
sf=E:/daten/ipl390/dasd/V51WK1_1.zvm
512A    3390    E:/daten/ipl390/dasd/VSE512.zvm cu=3990
sf=E:/daten/ipl390/dasd/VSE512_1.zvm
0700    3390    E:/daten/ipl390/dasd/zvmadd.zvm cu=3990
sf=E:/daten/ipl390/dasd/zvmadd_1.zvm
0701    3390    E:/daten/ipl390/dasd/cmswk1.zvm cu=3990
sf=E:/daten/ipl390/dasd/cmswk1_1.zvm
0702    3390    E:/daten/ipl390/dasd/BCUSR1.zvm cu=3990
sf=E:/daten/ipl390/dasd/BCUSR1_1.zvm
0703    3390    E:/daten/ipl390/dasd/T33901.zvm cu=3990
0704    3390    E:/daten/ipl390/dasd/cmswk2.zvm cu=3990
sf=E:/daten/ipl390/dasd/cmswk2_1.zvm
0705    3390    E:/daten/ipl390/dasd/cmswk3.zvm cu=3990
sf=E:/daten/ipl390/dasd/cmswk3_1.zvm
0706    3390    E:/daten/ipl390/dasd/BCUSR2.zvm cu=3990
sf=E:/daten/ipl390/dasd/BCUSR2_1.zvm
# VM-Systeme
0530    3390    E:/daten/ipl390/dasd/530res.zvm cu=3990
sf=E:/daten/ipl390/dasd/530res_1.zvm
0531    3390    E:/daten/ipl390/dasd/530pag.zvm cu=3990
sf=E:/daten/ipl390/dasd/530pag_1.zvm
0532    3390    E:/daten/ipl390/dasd/530spl.zvm cu=3990
sf=E:/daten/ipl390/dasd/530spl_1.zvm
0533    3390    E:/daten/ipl390/dasd/530w01.zvm cu=3990
sf=E:/daten/ipl390/dasd/530w01_1.zvm
0540    3390    E:/daten/ipl390/dasd/540res.zvm cu=3990
sf=E:/daten/ipl390/dasd/540res_1.zvm
0541    3390    E:/daten/ipl390/dasd/540pag.zvm cu=3990
sf=E:/daten/ipl390/dasd/540pag_1.zvm
0542    3390    E:/daten/ipl390/dasd/540spl.zvm cu=3990
sf=E:/daten/ipl390/dasd/540spl_1.zvm
0620    3390    E:/daten/ipl390/dasd/m01res.zvm62 cu=3990
sf=E:/daten/ipl390/dasd/m01res_1.zvm62
0621    3390    E:/daten/ipl390/dasd/m01s01.zvm62 cu=3990
sf=E:/daten/ipl390/dasd/m01s01_1.zvm62
0622    3390    E:/daten/ipl390/dasd/m01p01.zvm62 cu=3990
sf=E:/daten/ipl390/dasd/m01p01_1.zvm62
0623    3390    E:/daten/ipl390/dasd/vmcom1.zvm62 cu=3990
sf=E:/daten/ipl390/dasd/vmcom1_1.zvm62
0624    3390    E:/daten/ipl390/dasd/620rl1.zvm62 cu=3990
sf=E:/daten/ipl390/dasd/620rl1_1.zvm62
0630    3390    E:/daten/ipl390/dasd/630res.zvm cu=3990
sf=E:/daten/ipl390/dasd/630res_1.zvm
0631    3390    E:/daten/ipl390/dasd/630pg1.zvm cu=3990
sf=E:/daten/ipl390/dasd/630pg1_1.zvm
0632    3390    E:/daten/ipl390/dasd/630sp1.zvm cu=3990
sf=E:/daten/ipl390/dasd/630sp1_1.zvm
0633    3390    E:/daten/ipl390/dasd/630com.zvm cu=3990
sf=E:/daten/ipl390/dasd/630com_1.zvm
0634    3390    E:/daten/ipl390/dasd/630rl1.zvm cu=3990
sf=E:/daten/ipl390/dasd/630rl1_1.zvm
0635    3390    E:/daten/ipl390/dasd/630w01.zvm cu=3990
sf=E:/daten/ipl390/dasd/630w01_1.zvm
#0640    3390    E:/daten/ipl390/dasd/640res.zvm cu=3990
sf=E:/daten/ipl390/dasd/640res_1.zvm
#0641    3390    E:/daten/ipl390/dasd/640s01.zvm cu=3990
sf=E:/daten/ipl390/dasd/640s01_1.zvm
#0642    3390    E:/daten/ipl390/dasd/640p01.zvm cu=3990
sf=E:/daten/ipl390/dasd/640p01_1.zvm
#0643    3390    E:/daten/ipl390/dasd/64com1.zvm cu=3990
sf=E:/daten/ipl390/dasd/64com1_1.zvm
#0644    3390    E:/daten/ipl390/dasd/640rl1.zvm cu=3990
sf=E:/daten/ipl390/dasd/640rl1_1.zvm
#0645    3390    E:/daten/ipl390/dasd/640W01.zvm cu=3990
sf=E:/daten/ipl390/dasd/640W01_1.zvm
1206    3390    E:/daten/ipl390/dasd/640res.zvm cu=3990
sf=E:/daten/ipl390/dasd/640res_1.zvm
1207    3390    E:/daten/ipl390/dasd/640s01.zvm cu=3990
sf=E:/daten/ipl390/dasd/640s01_1.zvm
1208    3390    E:/daten/ipl390/dasd/640p01.zvm cu=3990
sf=E:/daten/ipl390/dasd/640p01_1.zvm
1209    3390    E:/daten/ipl390/dasd/64com1.zvm cu=3990
sf=E:/daten/ipl390/dasd/64com1_1.zvm
120A    3390    E:/daten/ipl390/dasd/640rl1.zvm cu=3990
sf=E:/daten/ipl390/dasd/640rl1_1.zvm
120B    3390    E:/daten/ipl390/dasd/640W01.zvm cu=3990
sf=E:/daten/ipl390/dasd/640W01_1.zvm
FF01    3390    E:/daten/ipl390/dasd/TEMP01.zvm cu=3990
sf=E:/daten/ipl390/dasd/TEMP01_1.zvm
FF02    3390    E:/daten/ipl390/dasd/TEMP02.zvm cu=3990
sf=E:/daten/ipl390/dasd/TEMP02_1.zvm
# Test für VSEDASD-Rexx
FF03    3390    E:/daten/ipl390/dasd/TEMP03.zvm  cu=3990
sf=E:/daten/ipl390/dasd/TEMP03_1.zvm
# WM SE VSE01 Systemplatten für FSU
FF10    3390    E:/daten/ipl390/dasd/WMVS01.zvm  cu=3990
sf=E:/daten/ipl390/dasd/WMVS01_1.zvm
FF99    3390    E:/daten/ipl390/dasd/VTAP01.zvmx cu=3990
sf=E:/daten/ipl390/dasd/VTAP01_1.zvmx
*
3000    3390    e:/daten/ipl390/dasd/BGETM1.zVM   cu=3990
sf=e:/daten/ipl390/dasd/BGETM1_1.zvm
3001    3390    e:/daten/ipl390/dasd/BGETM2.zVM   cu=3990
sf=e:/daten/ipl390/dasd/BGETM2_1.zvm
3002    3390    e:/daten/ipl390/dasd/BGETM3.zVM   cu=3990
sf=e:/daten/ipl390/dasd/BGETM3_1.zvm
* neue VSE-Systeme
A422    3390    e:/daten/ipl390/dasd/VS422A.zVM   cu=3990
sf=e:/daten/ipl390/dasd/VS422A_1.zvm
B422    3390    e:/daten/ipl390/dasd/VS422B.zVM   cu=3990
sf=e:/daten/ipl390/dasd/VS422B_1.zvm

# TAPE Devices

0181    3490    *
0182    3490    *
0183    3490    *
0184    3490    *
0310    3490    *
0311    3490    *
0312    3490    *
0313    3490    *
0314    3490    *
0315    3490    *
0316    3490    *
0317    3490    *
0318    3490    *
0319    3490    *
0320    3490    *
0321    3490    *
0322    3490    *
0323    3490    *
0324    3490    *
0325    3490    *
0326    3490    *
0327    3490    *
0328    3490    *
0329    3490    *
0330    3490    *
0331    3490    *
0332    3490    *
0333    3490    *
0334    3490    *
0335    3490    *
0336    3490    *
0337    3490    *
0338    3490    *
0339    3490    *
0340    3490    *
0341    3490    *
0342    3490    *
0343    3490    *
0344    3490    *
0345    3490    *
0346    3490    *
0347    3490    *
0348    3490    *
0349    3490    *
0350    3490    *
0351    3490    *
0352    3490    *
0353    3490    *
0354    3490    *
0355    3490    *
0356    3490    *
0357    3490    *
0358    3490    *
0359    3490    *
0360    3490    *
0361    3490    *
0362    3490    *
0363    3490    *
0364    3490    *
0365    3490    *
0366    3490    *
0367    3490    *
0368    3490    *
0369    3490    *
0370    3490    *
0371    3490    *
0372    3490    *
0373    3490    *
0374    3490    *
0375    3490    *
0376    3490    *
0377    3490    *
0378    3490    *
0379    3490    *

# 3270 Display

0A00    3270 ZVMCONS
0A01    3270
0A02    3270
0A03    3270
00F0    3270 zos
00F1    3270 zos
00F3    3270 zos
0040    3270 CONSOLE

# Network Connection
# zVM
1000-1001 ctci -k 1024 -i 128 -n 42-00-47-11-08-15 192.168.147.1 0.0.0.0
1002-1003 ctci -n 42-00-47-11-08-15 192.168.147.2 0.0.0.0
1004-1005 ctci -n 42-00-47-11-08-15 192.168.147.3 0.0.0.0
1006-1007 ctci -n 42-00-47-11-08-15 192.168.147.4 0.0.0.0
1008-1009 ctci -n 42-00-47-11-08-15 192.168.147.5 0.0.0.0
#E10-E1A LCS -n 42-00-47-11-08-15 -o
e:/programme/hercules/herccfg/hercosa.oat

Hercules Log

13:49:09 HHCCP075I 1206:Stat=0C00 Count=0000 =>08CC8009 00000000
00000000 40000000 ............ ...
13:49:09 1206:end i/o bufcur 0 cache[207] waiters 0
13:49:09 HHCCP050I 1206:SCSW=00C04007 Stat=0C00 Count=0000 CCW=3FFA7250
13:49:09 08:49:09 z/VM  V6 R4.0  SERVICE LEVEL 1601 (64-BIT)
13:49:09 08:49:09 SYSTEM NUCLEUS CREATED ON 2017-03-21 AT 07:00:53,
LOADED FROM 640RES
13:49:09 08:49:09
13:49:09 08:49:09
****************************************************************
13:49:09 08:49:09 * LICENSED MATERIALS - PROPERTY OF
IBM*                        *
13:49:09 08:49:09
*                                                              *
13:49:09 08:49:09 * 5741-A07 (C) COPYRIGHT IBM CORP. 1983, 2016. ALL
RIGHTS      *
13:49:09 08:49:09 * RESERVED. US GOVERNMENT USERS RESTRICTED RIGHTS -
USE,       *
13:49:09 <pnl,color(green,black)>08:49:09 * DUPLICATION OR DISCLOSURE
RESTRICTED BY GSA ADP SCHEDULE     *
13:49:09 08:49:09 * CONTRACT WITH IBM
CORP.                                      *
13:49:09 08:49:09
*                                                              *
13:49:09 08:49:09 * * TRADEMARK OF INTERNATIONAL BUSINESS
MACHINES.              *
13:49:09 08:49:09
****************************************************************
13:49:09 08:49:09
13:49:09 08:49:09 HCPZCO6718I Using parm disk 1 on volume 64COM1 (device
1209).
13:49:09 08:49:09 HCPZCO6718I Parm disk resides on cylinders 1 through 120.
13:49:09 08:49:09 Start ((Warm Force COLD CLEAN) (DRain) (DIsable)  
(NODIRect)
13:49:09 08:49:09       (NOAUTOlog)) or (SHUTDOWN)
13:49:09 HCPSED6013A A CP read is pending.
13:49:20 scp
13:49:20 08:49:20
13:49:20 08:49:20 NOW 08:49:20 EDT THURSDAY 2017-04-20
13:49:20 08:49:20 Change TOD clock (Yes No)
13:49:20 HCPSED6013A A CP read is pending.
13:49:24 scp
13:49:24 1206:start i/o file[0] bufcur 0 cache[207]
13:49:24 1206:synchronous  I/O ccw addr 3ffa7318
13:49:24 HHCCP048I 1206:CCW=63400010 3FFA7330=>40C00050 00000000
00000000 00000000  {.&............
13:49:24 HHCCP075I 1206:Stat=0C00 Count=0000
13:49:24 HHCCP048I 1206:CCW=47600010 3FFA7340=>16000001 00000000
00000000 03000000 ................
13:49:24 1206:HHCDA038I seeking to cyl 0 head 0
13:49:24 1206:HHCDA041I read count orientation is index
13:49:24 1206:HHCDA043I cyl 0 head 0 record 0 kl 0 dl 8 of 0
13:49:24 1206:HHCDA041I read count orientation is count
13:49:24 1206:HHCDA043I cyl 0 head 0 record 1 kl 0 dl 24 of 0
13:49:24 1206:HHCDA041I read count orientation is count
13:49:24 1206:HHCDA043I cyl 0 head 0 record 2 kl 0 dl 4096 of 0
13:49:24 1206:HHCDA041I read count orientation is count
13:49:24 1206:HHCDA043I cyl 0 head 0 record 3 kl 4 dl 80 of 0
13:49:24 HHCCP075I 1206:Stat=0C00 Count=0000
13:49:24 HHCCP048I 1206:CCW=86200050 5FFA71A8=>00000000 00000000
00000000 00000000 ................
13:49:24 1206:HHCDA045I read data 80 bytes
13:49:24 HHCCP075I 1206:Stat=0C00 Count=0000 =>E5D6D3F1 F6F4F0D9
C5E2F000 00000005 VOL1640RES0.....
13:49:24 1206:end i/o bufcur 0 cache[207] waiters 0
13:49:24 HHCCP050I 1206:SCSW=00C04007 Stat=0C00 Count=0000 CCW=3FFA7330
13:49:24 1206:start i/o file[0] bufcur 0 cache[207]
13:49:24 1206:synchronous  I/O ccw addr 3ffa7388
13:49:24 HHCCP048I 1206:CCW=63400010 3FFA73A0=>40C01000 00000000
00000000 00000000  {..............
13:49:24 HHCCP075I 1206:Stat=0C00 Count=0000
13:49:24 HHCCP048I 1206:CCW=47600010 3FFA73B0=>16000001 00000000
00000000 04000000 ................
13:49:24 1206:HHCDA038I seeking to cyl 0 head 0
13:49:24 1206:HHCDA041I read count orientation is index
13:49:24 1206:HHCDA043I cyl 0 head 0 record 0 kl 0 dl 8 of 0
13:49:24 1206:HHCDA041I read count orientation is count
13:49:24 1206:HHCDA043I cyl 0 head 0 record 1 kl 0 dl 24 of 0
13:49:24 1206:HHCDA041I read count orientation is count
13:49:24 1206:HHCDA043I cyl 0 head 0 record 2 kl 0 dl 4096 of 0
13:49:24 1206:HHCDA041I read count orientation is count
13:49:24 1206:HHCDA043I cyl 0 head 0 record 3 kl 4 dl 80 of 0
13:49:24 1206:HHCDA041I read count orientation is count
13:49:24 1206:HHCDA043I cyl 0 head 0 record 4 kl 0 dl 4096 of 0
13:49:24 HHCCP075I 1206:Stat=0C00 Count=0000
13:49:24 HHCCP048I 1206:CCW=86201000 3FD32000=>00000000 00000000
00000000 00000000 ................
13:49:24 1206:HHCDA045I read data 4096 bytes
13:49:24 HHCCP075I 1206:Stat=0C00 Count=0000 =>08CC8009 00000000
00000000 40000000 ............ ...
13:49:24 1206:end i/o bufcur 0 cache[207] waiters 0
13:49:24 HHCCP050I 1206:SCSW=00C04007 Stat=0C00 Count=0000 CCW=3FFA73A0
13:49:24 1206:start i/o file[0] bufcur 0 cache[207]
13:49:24 1206:synchronous  I/O ccw addr 1fddd000
13:49:24 HHCCP048I 1206:CCW=E7400040 1FDDDF50=>01800000 00000000
00000000 40C01000 ............ {..
13:49:24 HHCCP075I 1206:Stat=0E40 Count=0040
13:49:24 HHCCP076I 1206:Sense=80000000 00FFFF01 00000000 00000000
00000000 00000000
13:49:24 HHCCP077I 1206:Sense=CMDREJ
13:49:24 1206:end i/o bufcur 0 cache[207] waiters 0
13:49:24 HHCCP050I 1206:SCSW=00C24017 Stat=0E40 Count=0040 CCW=1FDDD008
13:49:24 08:49:24
13:49:24 1206:start i/o file[0] bufcur 0 cache[207]
13:49:24 1206:synchronous  I/O ccw addr 3fd3c000
13:49:24 HHCCP048I 1206:CCW=E7400040 3FD3CF50=>01800000 00000000
00000000 40C01000 ............ {..
13:49:24 HHCCP075I 1206:Stat=0E40 Count=0040
13:49:24 HHCCP076I 1206:Sense=80000000 00FFFF01 00000000 00000000
00000000 00000000
13:49:24 HHCCP077I 1206:Sense=CMDREJ
13:49:24 1206:end i/o bufcur 0 cache[207] waiters 0
13:49:24 HHCCP050I 1206:SCSW=00C24017 Stat=0E40 Count=0040 CCW=3FD3C008
13:49:24 08:49:24 HCPERP500I  DASD  1206 AN OPERATION WAS TERMINATED
BECAUSE A
13:49:24 08:49:24 HCPERP500I  COMMAND REJECT ERROR OCCURRED
13:49:24 08:49:24 HCPERP6300I SENSE DATA FORMAT = 00       MSG CODE = 01
13:49:24 08:49:24 HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = N/A HPF
13:49:24 08:49:24 HCPERP6302I SEEK ADDRESS =   000000000000
13:49:24 08:49:24 HCPERP6303I SENSE = 80000000 00FFFF01 00000000
00000000 00000000
13:49:24 08:49:24 HCPERP6303I 00000000 00000080 00000000
13:49:24 08:49:24 HCPERP6304I IRB = 00C24017 1FDDD008 0E400040 00800000
13:49:24 08:49:24 HCPERP6305I USERID = SYSTEM
13:49:24 08:49:24 HCPERP2216I CHANNEL PATH ID = 12
13:49:24 08:49:24 HCPUDS1777E The directory on volume 640RES could not
be initialized.
13:49:24 08:49:24 HCPUDS1752E No directory could be initialized.
13:49:24 08:49:24 HCPERP500I  DASD  1206 AN OPERATION WAS TERMINATED
BECAUSE A
13:49:24 08:49:24 HCPERP500I  COMMAND REJECT ERROR OCCURRED
13:49:24 08:49:24 HCPERP6300I SENSE DATA FORMAT = 00       MSG CODE = 01
13:49:24 08:49:24 HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = N/A HPF
13:49:24 08:49:24 HCPERP6302I SEEK ADDRESS =   000000000000
13:49:24 08:49:24 HCPERP6303I SENSE = 80000000 00FFFF01 00000000
00000000 00000000
13:49:24 08:49:24 HCPERP6303I 00000000 00000080 00000000
13:49:24 08:49:24 HCPERP6304I IRB = 00C24017 3FD3C008 0E400040 00800000
13:49:24 08:49:24 HCPERP6305I USERID = SYSTEM
13:49:24 08:49:24 HCPERP2216I CHANNEL PATH ID = 12
13:49:24 08:49:24 HCPWRM902W System recovery failure; fatal I/O error
13:49:24 08:49:24 HCPWRP959I ZVM6401  SYSTEM TERMINATION IN PROGRESS ON
2017-04-20
13:49:27 HHCCP011I CPU0000: Disabled wait state
13:49:27           PSW=00020000 00000000 0000000000000902


Am 27.03.2017 um 14:26 schrieb Franz Josef Pohlen
[hidden email] [hercules-390]:

> Hello Ivan,
>
> I have tried your recommendation ARCHLVL ENABLE BIT44. The msg
> HCPRFI9030W doesn't appear any longer but now after the standalone
> loader screen and PF10 there is an X SYSTEM in the emulation window and
> suddenly afterwards a PROG708. This means that an SNA msg was received
> before the begin of the data transmission. I use Personal Communication
> as a console emulation as always and had never problems before.
>
>
> Any help is welcome.
>


--
kind regards
Franz Josef Pohlen


------------------------------------

------------------------------------

Community email addresses:
  Post message: [hidden email]
  Subscribe:    [hidden email]
  Unsubscribe:  [hidden email]
  List owner:   [hidden email]

Files and archives at:
  http://groups.yahoo.com/group/hercules-390

Get the latest version of Hercules from:
  http://www.hercules-390.org


------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/hercules-390/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/hercules-390/join
    (Yahoo! ID required)

<*> To change settings via email:
    [hidden email]
    [hidden email]

<*> To unsubscribe from this group, send an email to:
    [hidden email]

<*> Your use of Yahoo Groups is subject to:
    https://info.yahoo.com/legal/us/yahoo/utos/terms/

Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
I have just seen this VM message in the log after the command reject.

HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = N/A HPF

I wonder if the word HPF may point to a check of zVM if High Perfomance Ficon is available and Hercules doesn't react on this as expected.

Am 21.04.2017 um 14:35 schrieb Franz Josef Pohlen
[hidden email] [hercules-390]:

> Hello all,
>
> as the Hercules 4.0 doesn't seem to be working for the current zvm. I
> will try to get the zvm 6.4 running with Hercules 3.12 (Win 64Bit). I
> get an error during IPL after I have confirmed the time question. It
> cancels with command reject on the IPL device. For documentation I have
> started a ccw trace on the ipl device and ipled the zvm 6.4 with
> cons=sysc. So the zVM messages and the ccw trace is in the log. I hope
> that someone of you developers can see there what's going wrong. My old
> zvm 6.3 starts without problems on this hercules configuration. I have
> also attached my hercules config. There might still be some settings for
> Hercules 4.0 but they were ignored during start with Hercules 3.12.
>
> Thanks in advance for your help and have a nice weekend
>
> Franz Josef
>
> Hercules Config
>
> #
> # Hercules Emulator Control file...
> # Description: Standalone DDR
> # MaxShutdownSecs: 99
> #
> #
> # System parameters
> #
>
> CPUSERIAL 004920
> CPUMODEL  2965                # CPU model number
> MAINSIZE  2048
> CNSLPORT  3270
> NUMCPU    4
> # ARCHMODE  ESA/390
> ARCHLVL   z/ARCH
> ARCHLVL   ENABLE
> ARCHLVL   ENABLE PROBSTATE_DIAGF08
> ARCHLVL   ENABLE VIRTUAL_MACHINE
> ARCHLVL   ENABLE QDIO_ASSIST
> ARCHLVL   ENABLE QDIO_TDD
> ARCHLVL   ENABLE asn_lx_reuse
> ARCHLVL   ENABLE BIT44
> DIAG8CMD  ENABLE
> ECPSVM    ENABLE
> LOADPARM  0A00....
> LPARNUM   1
> LPARNAME  ZVM1
> SYSEPOCH  1900
> TZOFFSET  +0100
> OSTAILOR  QUIET
> PANRATE   1000
> PGMPRDOS  LICENSED
> DEVTMAX   150
> # neue Prio-Werte ab Version 3.05
> HERCPRIO  0
> TODPRIO   -20
> DEVPRIO   8
> CPUPRIO   15
> # alte Werte vor offizieller Version 3.05
> # HERCPRIO     0
> # DEVPRIO     -8
> # TODPRIO      0
> # CPUPRIO      0
> # cckd parameter
> # cckd compparm=5
> # Card Readers
>
> #000C    3505    e:/daten/ipl390/standalone/iplddrxa.rdr ebcdic
> #001C    3505    e:/daten/ipl390/standalone/iplickdsf.rdr ebcdic
> #002C    3505    e:/daten/ipl390/standalone/iplsalipl.rdr ebcdic
>
> # Line Printers
>
> 000E    1403    d:/temp/prt00e.txt crlf
>
> # DASD Devices
>
> #0430    3390    E:/daten/ipl390/dasd/430res.zvm cu=3990
> sf=E:/daten/ipl390/dasd/430res_1.zvm
> #0431    3390    E:/daten/ipl390/dasd/430w01.zvm cu=3990
> sf=E:/daten/ipl390/dasd/430w01_1.zvm
> #0432    3390    E:/daten/ipl390/dasd/430w02.zvm cu=3990
> sf=E:/daten/ipl390/dasd/430w02_1.zvm
> #0433    3390    E:/daten/ipl390/dasd/430w03.zvm cu=3990
> sf=E:/daten/ipl390/dasd/430w03_1.zvm
> #0440    3390    E:/daten/ipl390/dasd/440res.zvm cu=3990
> sf=E:/daten/ipl390/dasd/440res_1.zvm
> #0441    3390    E:/daten/ipl390/dasd/440w01.zvm cu=3990
> sf=E:/daten/ipl390/dasd/440w01_1.zvm
> #0442    3390    E:/daten/ipl390/dasd/440w02.zvm cu=3990
> sf=E:/daten/ipl390/dasd/440w02_1.zvm
> 0600    3390    E:/daten/ipl390/dasd/VSErs1.zvm cu=3990
> sf=E:/daten/ipl390/dasd/VSErs1_1.zvm
> 0601    3390    E:/daten/ipl390/dasd/VSErs2.zvm cu=3990
> sf=E:/daten/ipl390/dasd/VSErs2_1.zvm
> 0602    3390    E:/daten/ipl390/dasd/VSEsys.zvm cu=3990
> sf=E:/daten/ipl390/dasd/VSEsys_1.zvm
> 0603    3390    E:/daten/ipl390/dasd/VSEVSM.zvm cu=3990
> sf=E:/daten/ipl390/dasd/VSEVSM_1.zvm
> 0604    3380    E:/daten/ipl390/dasd/VSE231.zvm cu=3990
> sf=E:/daten/ipl390/dasd/VSE231_1.zvm
> 0605    3380    E:/daten/ipl390/dasd/VSE232.zvm cu=3990
> sf=E:/daten/ipl390/dasd/VSE232_1.zvm
> 0606    3380    E:/daten/ipl390/dasd/VSEDAT.zvm cu=3990
> sf=E:/daten/ipl390/dasd/VSEDAT_1.zvm
> 0607    3390    E:/daten/ipl390/dasd/V31RES.zvm cu=3990
> sf=E:/daten/ipl390/dasd/V31RES_1.zvm
> 0608    3390    E:/daten/ipl390/dasd/V31WK1.zvm cu=3990
> sf=E:/daten/ipl390/dasd/V31WK1_1.zvm
> 0609    3390    E:/daten/ipl390/dasd/V41RSA.zvm cu=3990
> sf=E:/daten/ipl390/dasd/V41RSA_1.zvm
> 060A    3390    E:/daten/ipl390/dasd/V41W1A.zvm cu=3990
> sf=E:/daten/ipl390/dasd/V41W1A_1.zvm
> 060B    3390    E:/daten/ipl390/dasd/VSESY1.zvm cu=3990
> sf=E:/daten/ipl390/dasd/VSESY1_1.zvm
> 060C    3390    E:/daten/ipl390/dasd/VSESY2.zvm cu=3990
> sf=E:/daten/ipl390/dasd/VSESY2_1.zvm
> 060D    3390    E:/daten/ipl390/dasd/VSESY3.zvm cu=3990
> sf=E:/daten/ipl390/dasd/VSESY3_1.zvm
> 060E    3390    E:/daten/ipl390/dasd/VTAP01.zvm cu=3990
> sf=E:/daten/ipl390/dasd/VTAP01_1.zvm
> 0619    3390    E:/daten/ipl390/dasd/V41RSB.zvm cu=3990
> sf=E:/daten/ipl390/dasd/V41RSB_1.zvm
> 061A    3390    E:/daten/ipl390/dasd/V41W1B.zvm cu=3990
> sf=E:/daten/ipl390/dasd/V41W1B_1.zvm
> 511A    3390    E:/daten/ipl390/dasd/V51RES.zvm cu=3990
> sf=E:/daten/ipl390/dasd/V51RES_1.zvm
> 511B    3390    E:/daten/ipl390/dasd/V51WK1.zvm cu=3990
> sf=E:/daten/ipl390/dasd/V51WK1_1.zvm
> 512A    3390    E:/daten/ipl390/dasd/VSE512.zvm cu=3990
> sf=E:/daten/ipl390/dasd/VSE512_1.zvm
> 0700    3390    E:/daten/ipl390/dasd/zvmadd.zvm cu=3990
> sf=E:/daten/ipl390/dasd/zvmadd_1.zvm
> 0701    3390    E:/daten/ipl390/dasd/cmswk1.zvm cu=3990
> sf=E:/daten/ipl390/dasd/cmswk1_1.zvm
> 0702    3390    E:/daten/ipl390/dasd/BCUSR1.zvm cu=3990
> sf=E:/daten/ipl390/dasd/BCUSR1_1.zvm
> 0703    3390    E:/daten/ipl390/dasd/T33901.zvm cu=3990
> 0704    3390    E:/daten/ipl390/dasd/cmswk2.zvm cu=3990
> sf=E:/daten/ipl390/dasd/cmswk2_1.zvm
> 0705    3390    E:/daten/ipl390/dasd/cmswk3.zvm cu=3990
> sf=E:/daten/ipl390/dasd/cmswk3_1.zvm
> 0706    3390    E:/daten/ipl390/dasd/BCUSR2.zvm cu=3990
> sf=E:/daten/ipl390/dasd/BCUSR2_1.zvm
> # VM-Systeme
> 0530    3390    E:/daten/ipl390/dasd/530res.zvm cu=3990
> sf=E:/daten/ipl390/dasd/530res_1.zvm
> 0531    3390    E:/daten/ipl390/dasd/530pag.zvm cu=3990
> sf=E:/daten/ipl390/dasd/530pag_1.zvm
> 0532    3390    E:/daten/ipl390/dasd/530spl.zvm cu=3990
> sf=E:/daten/ipl390/dasd/530spl_1.zvm
> 0533    3390    E:/daten/ipl390/dasd/530w01.zvm cu=3990
> sf=E:/daten/ipl390/dasd/530w01_1.zvm
> 0540    3390    E:/daten/ipl390/dasd/540res.zvm cu=3990
> sf=E:/daten/ipl390/dasd/540res_1.zvm
> 0541    3390    E:/daten/ipl390/dasd/540pag.zvm cu=3990
> sf=E:/daten/ipl390/dasd/540pag_1.zvm
> 0542    3390    E:/daten/ipl390/dasd/540spl.zvm cu=3990
> sf=E:/daten/ipl390/dasd/540spl_1.zvm
> 0620    3390    E:/daten/ipl390/dasd/m01res.zvm62 cu=3990
> sf=E:/daten/ipl390/dasd/m01res_1.zvm62
> 0621    3390    E:/daten/ipl390/dasd/m01s01.zvm62 cu=3990
> sf=E:/daten/ipl390/dasd/m01s01_1.zvm62
> 0622    3390    E:/daten/ipl390/dasd/m01p01.zvm62 cu=3990
> sf=E:/daten/ipl390/dasd/m01p01_1.zvm62
> 0623    3390    E:/daten/ipl390/dasd/vmcom1.zvm62 cu=3990
> sf=E:/daten/ipl390/dasd/vmcom1_1.zvm62
> 0624    3390    E:/daten/ipl390/dasd/620rl1.zvm62 cu=3990
> sf=E:/daten/ipl390/dasd/620rl1_1.zvm62
> 0630    3390    E:/daten/ipl390/dasd/630res.zvm cu=3990
> sf=E:/daten/ipl390/dasd/630res_1.zvm
> 0631    3390    E:/daten/ipl390/dasd/630pg1.zvm cu=3990
> sf=E:/daten/ipl390/dasd/630pg1_1.zvm
> 0632    3390    E:/daten/ipl390/dasd/630sp1.zvm cu=3990
> sf=E:/daten/ipl390/dasd/630sp1_1.zvm
> 0633    3390    E:/daten/ipl390/dasd/630com.zvm cu=3990
> sf=E:/daten/ipl390/dasd/630com_1.zvm
> 0634    3390    E:/daten/ipl390/dasd/630rl1.zvm cu=3990
> sf=E:/daten/ipl390/dasd/630rl1_1.zvm
> 0635    3390    E:/daten/ipl390/dasd/630w01.zvm cu=3990
> sf=E:/daten/ipl390/dasd/630w01_1.zvm
> #0640    3390    E:/daten/ipl390/dasd/640res.zvm cu=3990
> sf=E:/daten/ipl390/dasd/640res_1.zvm
> #0641    3390    E:/daten/ipl390/dasd/640s01.zvm cu=3990
> sf=E:/daten/ipl390/dasd/640s01_1.zvm
> #0642    3390    E:/daten/ipl390/dasd/640p01.zvm cu=3990
> sf=E:/daten/ipl390/dasd/640p01_1.zvm
> #0643    3390    E:/daten/ipl390/dasd/64com1.zvm cu=3990
> sf=E:/daten/ipl390/dasd/64com1_1.zvm
> #0644    3390    E:/daten/ipl390/dasd/640rl1.zvm cu=3990
> sf=E:/daten/ipl390/dasd/640rl1_1.zvm
> #0645    3390    E:/daten/ipl390/dasd/640W01.zvm cu=3990
> sf=E:/daten/ipl390/dasd/640W01_1.zvm
> 1206    3390    E:/daten/ipl390/dasd/640res.zvm cu=3990
> sf=E:/daten/ipl390/dasd/640res_1.zvm
> 1207    3390    E:/daten/ipl390/dasd/640s01.zvm cu=3990
> sf=E:/daten/ipl390/dasd/640s01_1.zvm
> 1208    3390    E:/daten/ipl390/dasd/640p01.zvm cu=3990
> sf=E:/daten/ipl390/dasd/640p01_1.zvm
> 1209    3390    E:/daten/ipl390/dasd/64com1.zvm cu=3990
> sf=E:/daten/ipl390/dasd/64com1_1.zvm
> 120A    3390    E:/daten/ipl390/dasd/640rl1.zvm cu=3990
> sf=E:/daten/ipl390/dasd/640rl1_1.zvm
> 120B    3390    E:/daten/ipl390/dasd/640W01.zvm cu=3990
> sf=E:/daten/ipl390/dasd/640W01_1.zvm
> FF01    3390    E:/daten/ipl390/dasd/TEMP01.zvm cu=3990
> sf=E:/daten/ipl390/dasd/TEMP01_1.zvm
> FF02    3390    E:/daten/ipl390/dasd/TEMP02.zvm cu=3990
> sf=E:/daten/ipl390/dasd/TEMP02_1.zvm
> # Test für VSEDASD-Rexx
> FF03    3390    E:/daten/ipl390/dasd/TEMP03.zvm  cu=3990
> sf=E:/daten/ipl390/dasd/TEMP03_1.zvm
> # WM SE VSE01 Systemplatten für FSU
> FF10    3390    E:/daten/ipl390/dasd/WMVS01.zvm  cu=3990
> sf=E:/daten/ipl390/dasd/WMVS01_1.zvm
> FF99    3390    E:/daten/ipl390/dasd/VTAP01.zvmx cu=3990
> sf=E:/daten/ipl390/dasd/VTAP01_1.zvmx
> *
> 3000    3390    e:/daten/ipl390/dasd/BGETM1.zVM   cu=3990
> sf=e:/daten/ipl390/dasd/BGETM1_1.zvm
> 3001    3390    e:/daten/ipl390/dasd/BGETM2.zVM   cu=3990
> sf=e:/daten/ipl390/dasd/BGETM2_1.zvm
> 3002    3390    e:/daten/ipl390/dasd/BGETM3.zVM   cu=3990
> sf=e:/daten/ipl390/dasd/BGETM3_1.zvm
> * neue VSE-Systeme
> A422    3390    e:/daten/ipl390/dasd/VS422A.zVM   cu=3990
> sf=e:/daten/ipl390/dasd/VS422A_1.zvm
> B422    3390    e:/daten/ipl390/dasd/VS422B.zVM   cu=3990
> sf=e:/daten/ipl390/dasd/VS422B_1.zvm
>
> # TAPE Devices
>
> 0181    3490    *
> 0182    3490    *
> 0183    3490    *
> 0184    3490    *
> 0310    3490    *
> 0311    3490    *
> 0312    3490    *
> 0313    3490    *
> 0314    3490    *
> 0315    3490    *
> 0316    3490    *
> 0317    3490    *
> 0318    3490    *
> 0319    3490    *
> 0320    3490    *
> 0321    3490    *
> 0322    3490    *
> 0323    3490    *
> 0324    3490    *
> 0325    3490    *
> 0326    3490    *
> 0327    3490    *
> 0328    3490    *
> 0329    3490    *
> 0330    3490    *
> 0331    3490    *
> 0332    3490    *
> 0333    3490    *
> 0334    3490    *
> 0335    3490    *
> 0336    3490    *
> 0337    3490    *
> 0338    3490    *
> 0339    3490    *
> 0340    3490    *
> 0341    3490    *
> 0342    3490    *
> 0343    3490    *
> 0344    3490    *
> 0345    3490    *
> 0346    3490    *
> 0347    3490    *
> 0348    3490    *
> 0349    3490    *
> 0350    3490    *
> 0351    3490    *
> 0352    3490    *
> 0353    3490    *
> 0354    3490    *
> 0355    3490    *
> 0356    3490    *
> 0357    3490    *
> 0358    3490    *
> 0359    3490    *
> 0360    3490    *
> 0361    3490    *
> 0362    3490    *
> 0363    3490    *
> 0364    3490    *
> 0365    3490    *
> 0366    3490    *
> 0367    3490    *
> 0368    3490    *
> 0369    3490    *
> 0370    3490    *
> 0371    3490    *
> 0372    3490    *
> 0373    3490    *
> 0374    3490    *
> 0375    3490    *
> 0376    3490    *
> 0377    3490    *
> 0378    3490    *
> 0379    3490    *
>
> # 3270 Display
>
> 0A00    3270 ZVMCONS
> 0A01    3270
> 0A02    3270
> 0A03    3270
> 00F0    3270 zos
> 00F1    3270 zos
> 00F3    3270 zos
> 0040    3270 CONSOLE
>
> # Network Connection
> # zVM
> 1000-1001 ctci -k 1024 -i 128 -n 42-00-47-11-08-15 192.168.147.1 0.0.0.0
> 1002-1003 ctci -n 42-00-47-11-08-15 192.168.147.2 0.0.0.0
> 1004-1005 ctci -n 42-00-47-11-08-15 192.168.147.3 0.0.0.0
> 1006-1007 ctci -n 42-00-47-11-08-15 192.168.147.4 0.0.0.0
> 1008-1009 ctci -n 42-00-47-11-08-15 192.168.147.5 0.0.0.0
> #E10-E1A LCS -n 42-00-47-11-08-15 -o
> e:/programme/hercules/herccfg/hercosa.oat
>
> Hercules Log
>
> 13:49:09 HHCCP075I 1206:Stat=0C00 Count=0000 =>08CC8009 00000000
> 00000000 40000000 ............ ...
> 13:49:09 1206:end i/o bufcur 0 cache[207] waiters 0
> 13:49:09 HHCCP050I 1206:SCSW=00C04007 Stat=0C00 Count=0000 CCW=3FFA7250
> 13:49:09 08:49:09 z/VM  V6 R4.0  SERVICE LEVEL 1601 (64-BIT)
> 13:49:09 08:49:09 SYSTEM NUCLEUS CREATED ON 2017-03-21 AT 07:00:53,
> LOADED FROM 640RES
> 13:49:09 08:49:09
> 13:49:09 08:49:09
> ****************************************************************
> 13:49:09 08:49:09 * LICENSED MATERIALS - PROPERTY OF
> IBM*                        *
> 13:49:09 08:49:09
> *                                                              *
> 13:49:09 08:49:09 * 5741-A07 (C) COPYRIGHT IBM CORP. 1983, 2016. ALL
> RIGHTS      *
> 13:49:09 08:49:09 * RESERVED. US GOVERNMENT USERS RESTRICTED RIGHTS -
> USE,       *
> 13:49:09 <pnl,color(green,black)>08:49:09 * DUPLICATION OR DISCLOSURE
> RESTRICTED BY GSA ADP SCHEDULE     *
> 13:49:09 08:49:09 * CONTRACT WITH IBM
> CORP.                                      *
> 13:49:09 08:49:09
> *                                                              *
> 13:49:09 08:49:09 * * TRADEMARK OF INTERNATIONAL BUSINESS
> MACHINES.              *
> 13:49:09 08:49:09
> ****************************************************************
> 13:49:09 08:49:09
> 13:49:09 08:49:09 HCPZCO6718I Using parm disk 1 on volume 64COM1 (device
> 1209).
> 13:49:09 08:49:09 HCPZCO6718I Parm disk resides on cylinders 1 through 120.
> 13:49:09 08:49:09 Start ((Warm Force COLD CLEAN) (DRain) (DIsable)
> (NODIRect)
> 13:49:09 08:49:09       (NOAUTOlog)) or (SHUTDOWN)
> 13:49:09 HCPSED6013A A CP read is pending.
> 13:49:20 scp
> 13:49:20 08:49:20
> 13:49:20 08:49:20 NOW 08:49:20 EDT THURSDAY 2017-04-20
> 13:49:20 08:49:20 Change TOD clock (Yes No)
> 13:49:20 HCPSED6013A A CP read is pending.
> 13:49:24 scp
> 13:49:24 1206:start i/o file[0] bufcur 0 cache[207]
> 13:49:24 1206:synchronous  I/O ccw addr 3ffa7318
> 13:49:24 HHCCP048I 1206:CCW=63400010 3FFA7330=>40C00050 00000000
> 00000000 00000000  {.&............
> 13:49:24 HHCCP075I 1206:Stat=0C00 Count=0000
> 13:49:24 HHCCP048I 1206:CCW=47600010 3FFA7340=>16000001 00000000
> 00000000 03000000 ................
> 13:49:24 1206:HHCDA038I seeking to cyl 0 head 0
> 13:49:24 1206:HHCDA041I read count orientation is index
> 13:49:24 1206:HHCDA043I cyl 0 head 0 record 0 kl 0 dl 8 of 0
> 13:49:24 1206:HHCDA041I read count orientation is count
> 13:49:24 1206:HHCDA043I cyl 0 head 0 record 1 kl 0 dl 24 of 0
> 13:49:24 1206:HHCDA041I read count orientation is count
> 13:49:24 1206:HHCDA043I cyl 0 head 0 record 2 kl 0 dl 4096 of 0
> 13:49:24 1206:HHCDA041I read count orientation is count
> 13:49:24 1206:HHCDA043I cyl 0 head 0 record 3 kl 4 dl 80 of 0
> 13:49:24 HHCCP075I 1206:Stat=0C00 Count=0000
> 13:49:24 HHCCP048I 1206:CCW=86200050 5FFA71A8=>00000000 00000000
> 00000000 00000000 ................
> 13:49:24 1206:HHCDA045I read data 80 bytes
> 13:49:24 HHCCP075I 1206:Stat=0C00 Count=0000 =>E5D6D3F1 F6F4F0D9
> C5E2F000 00000005 VOL1640RES0.....
> 13:49:24 1206:end i/o bufcur 0 cache[207] waiters 0
> 13:49:24 HHCCP050I 1206:SCSW=00C04007 Stat=0C00 Count=0000 CCW=3FFA7330
> 13:49:24 1206:start i/o file[0] bufcur 0 cache[207]
> 13:49:24 1206:synchronous  I/O ccw addr 3ffa7388
> 13:49:24 HHCCP048I 1206:CCW=63400010 3FFA73A0=>40C01000 00000000
> 00000000 00000000  {..............
> 13:49:24 HHCCP075I 1206:Stat=0C00 Count=0000
> 13:49:24 HHCCP048I 1206:CCW=47600010 3FFA73B0=>16000001 00000000
> 00000000 04000000 ................
> 13:49:24 1206:HHCDA038I seeking to cyl 0 head 0
> 13:49:24 1206:HHCDA041I read count orientation is index
> 13:49:24 1206:HHCDA043I cyl 0 head 0 record 0 kl 0 dl 8 of 0
> 13:49:24 1206:HHCDA041I read count orientation is count
> 13:49:24 1206:HHCDA043I cyl 0 head 0 record 1 kl 0 dl 24 of 0
> 13:49:24 1206:HHCDA041I read count orientation is count
> 13:49:24 1206:HHCDA043I cyl 0 head 0 record 2 kl 0 dl 4096 of 0
> 13:49:24 1206:HHCDA041I read count orientation is count
> 13:49:24 1206:HHCDA043I cyl 0 head 0 record 3 kl 4 dl 80 of 0
> 13:49:24 1206:HHCDA041I read count orientation is count
> 13:49:24 1206:HHCDA043I cyl 0 head 0 record 4 kl 0 dl 4096 of 0
> 13:49:24 HHCCP075I 1206:Stat=0C00 Count=0000
> 13:49:24 HHCCP048I 1206:CCW=86201000 3FD32000=>00000000 00000000
> 00000000 00000000 ................
> 13:49:24 1206:HHCDA045I read data 4096 bytes
> 13:49:24 HHCCP075I 1206:Stat=0C00 Count=0000 =>08CC8009 00000000
> 00000000 40000000 ............ ...
> 13:49:24 1206:end i/o bufcur 0 cache[207] waiters 0
> 13:49:24 HHCCP050I 1206:SCSW=00C04007 Stat=0C00 Count=0000 CCW=3FFA73A0
> 13:49:24 1206:start i/o file[0] bufcur 0 cache[207]
> 13:49:24 1206:synchronous  I/O ccw addr 1fddd000
> 13:49:24 HHCCP048I 1206:CCW=E7400040 1FDDDF50=>01800000 00000000
> 00000000 40C01000 ............ {..
> 13:49:24 HHCCP075I 1206:Stat=0E40 Count=0040
> 13:49:24 HHCCP076I 1206:Sense=80000000 00FFFF01 00000000 00000000
> 00000000 00000000
> 13:49:24 HHCCP077I 1206:Sense=CMDREJ
> 13:49:24 1206:end i/o bufcur 0 cache[207] waiters 0
> 13:49:24 HHCCP050I 1206:SCSW=00C24017 Stat=0E40 Count=0040 CCW=1FDDD008
> 13:49:24 08:49:24
> 13:49:24 1206:start i/o file[0] bufcur 0 cache[207]
> 13:49:24 1206:synchronous  I/O ccw addr 3fd3c000
> 13:49:24 HHCCP048I 1206:CCW=E7400040 3FD3CF50=>01800000 00000000
> 00000000 40C01000 ............ {..
> 13:49:24 HHCCP075I 1206:Stat=0E40 Count=0040
> 13:49:24 HHCCP076I 1206:Sense=80000000 00FFFF01 00000000 00000000
> 00000000 00000000
> 13:49:24 HHCCP077I 1206:Sense=CMDREJ
> 13:49:24 1206:end i/o bufcur 0 cache[207] waiters 0
> 13:49:24 HHCCP050I 1206:SCSW=00C24017 Stat=0E40 Count=0040 CCW=3FD3C008
> 13:49:24 08:49:24 HCPERP500I  DASD  1206 AN OPERATION WAS TERMINATED
> BECAUSE A
> 13:49:24 08:49:24 HCPERP500I  COMMAND REJECT ERROR OCCURRED
> 13:49:24 08:49:24 HCPERP6300I SENSE DATA FORMAT = 00       MSG CODE = 01
> 13:49:24 08:49:24 HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = N/A HPF
> 13:49:24 08:49:24 HCPERP6302I SEEK ADDRESS =   000000000000
> 13:49:24 08:49:24 HCPERP6303I SENSE = 80000000 00FFFF01 00000000
> 00000000 00000000
> 13:49:24 08:49:24 HCPERP6303I 00000000 00000080 00000000
> 13:49:24 08:49:24 HCPERP6304I IRB = 00C24017 1FDDD008 0E400040 00800000
> 13:49:24 08:49:24 HCPERP6305I USERID = SYSTEM
> 13:49:24 08:49:24 HCPERP2216I CHANNEL PATH ID = 12
> 13:49:24 08:49:24 HCPUDS1777E The directory on volume 640RES could not
> be initialized.
> 13:49:24 08:49:24 HCPUDS1752E No directory could be initialized.
> 13:49:24 08:49:24 HCPERP500I  DASD  1206 AN OPERATION WAS TERMINATED
> BECAUSE A
> 13:49:24 08:49:24 HCPERP500I  COMMAND REJECT ERROR OCCURRED
> 13:49:24 08:49:24 HCPERP6300I SENSE DATA FORMAT = 00       MSG CODE = 01
> 13:49:24 08:49:24 HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = N/A HPF
> 13:49:24 08:49:24 HCPERP6302I SEEK ADDRESS =   000000000000
> 13:49:24 08:49:24 HCPERP6303I SENSE = 80000000 00FFFF01 00000000
> 00000000 00000000
> 13:49:24 08:49:24 HCPERP6303I 00000000 00000080 00000000
> 13:49:24 08:49:24 HCPERP6304I IRB = 00C24017 3FD3C008 0E400040 00800000
> 13:49:24 08:49:24 HCPERP6305I USERID = SYSTEM
> 13:49:24 08:49:24 HCPERP2216I CHANNEL PATH ID = 12
> 13:49:24 08:49:24 HCPWRM902W System recovery failure; fatal I/O error
> 13:49:24 08:49:24 HCPWRP959I ZVM6401  SYSTEM TERMINATION IN PROGRESS ON
> 2017-04-20
> 13:49:27 HHCCP011I CPU0000: Disabled wait state
> 13:49:27           PSW=00020000 00000000 0000000000000902
>
>
> Am 27.03.2017 um 14:26 schrieb Franz Josef Pohlen
> [hidden email] [hercules-390]:
> > Hello Ivan,
> >
> > I have tried your recommendation ARCHLVL ENABLE BIT44. The msg
> > HCPRFI9030W doesn't appear any longer but now after the standalone
> > loader screen and PF10 there is an X SYSTEM in the emulation window and
> > suddenly afterwards a PROG708. This means that an SNA msg was received
> > before the begin of the data transmission. I use Personal Communication
> > as a console emulation as always and had never problems before.
> >
> >
> > Any help is welcome.
> >
>
>


--
kind regards
Franz Josef Pohlen


------------------------------------

------------------------------------

Community email addresses:
  Post message: [hidden email]
  Subscribe:    [hidden email]
  Unsubscribe:  [hidden email]
  List owner:   [hidden email]

Files and archives at:
  http://groups.yahoo.com/group/hercules-390

Get the latest version of Hercules from:
  http://www.hercules-390.org


------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/hercules-390/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/hercules-390/join
    (Yahoo! ID required)

<*> To change settings via email:
    [hidden email]
    [hidden email]

<*> To unsubscribe from this group, send an email to:
    [hidden email]

<*> Your use of Yahoo Groups is subject to:
    https://info.yahoo.com/legal/us/yahoo/utos/terms/

Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
In reply to this post by Hercules390 - General mailing list
There is no work around in Hercules for an unsupported CCW command (E7).

Can the command be implemented?  Depends upon whether documentation of
the command can be found and what it does and what it would take to
emulate it.  

I personally have no documentation about this command.  Someone else
might. This information is getting harder and harder to fine as time
goes on.  My most recent documentation is from 2000.  This command is
not documented there.

Can you get the operating system to _not_ issue the command?  There
might be a way to do that.  Purely speculation on my part.  It would
have to be through the device type, CU type or some OS configuration
somewhere.  I would not want to muck about with those without a backup
of the original volume.

Harold Grovesteen


On Fri, 2017-04-21 at 14:35 +0200, Franz Josef Pohlen
[hidden email] [hercules-390] wrote:

> Hello all,
>
> as the Hercules 4.0 doesn't seem to be working for the current zvm. I
> will try to get the zvm 6.4 running with Hercules 3.12 (Win 64Bit). I
> get an error during IPL after I have confirmed the time question. It
> cancels with command reject on the IPL device. For documentation I have
> started a ccw trace on the ipl device and ipled the zvm 6.4 with
> cons=sysc. So the zVM messages and the ccw trace is in the log. I hope
> that someone of you developers can see there what's going wrong. My old
> zvm 6.3 starts without problems on this hercules configuration. I have
> also attached my hercules config. There might still be some settings for
> Hercules 4.0 but they were ignored during start with Hercules 3.12.
>
> Thanks in advance for your help and have a nice weekend
>
> Franz Josef

> 13:49:24 1206:start i/o file[0] bufcur 0 cache[207]
> 13:49:24 1206:synchronous  I/O ccw addr 1fddd000
> 13:49:24 HHCCP048I 1206:CCW=E7400040 1FDDDF50=>01800000 00000000
> 00000000 40C01000 ............ {..
> 13:49:24 HHCCP075I 1206:Stat=0E40 Count=0040
> 13:49:24 HHCCP076I 1206:Sense=80000000 00FFFF01 00000000 00000000
> 00000000 00000000
> 13:49:24 HHCCP077I 1206:Sense=CMDREJ
> 13:49:24 1206:end i/o bufcur 0 cache[207] waiters 0
> 13:49:24 HHCCP050I 1206:SCSW=00C24017 Stat=0E40 Count=0040 CCW=1FDDD008
> 13:49:24 08:49:24
> 13:49:24 1206:start i/o file[0] bufcur 0 cache[207]
> 13:49:24 1206:synchronous  I/O ccw addr 3fd3c000
> 13:49:24 HHCCP048I 1206:CCW=E7400040 3FD3CF50=>01800000 00000000
> 00000000 40C01000 ............ {..
> 13:49:24 HHCCP075I 1206:Stat=0E40 Count=0040
> 13:49:24 HHCCP076I 1206:Sense=80000000 00FFFF01 00000000 00000000
> 00000000 00000000
> 13:49:24 HHCCP077I 1206:Sense=CMDREJ
> 13:49:24 1206:end i/o bufcur 0 cache[207] waiters 0
> 13:49:24 HHCCP050I 1206:SCSW=00C24017 Stat=0E40 Count=0040 CCW=3FD3C008


Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
In reply to this post by Hercules390 - General mailing list
Entirely possible.  Could be implying a level of functionality not
available with Hercules.  How to get the OS to do something else is way
beyond my personal knowledge.  Perhaps a CU model number as opposed to
omitting it might help or a change to the CU type.  Just speculation.

The documentation I have that does not have this command is for storage
servers 2105 models E10, E20, F10 and F20.  If you could get the OS to
think the DASD is on one of these control units, it might change the
behavior.

In the CCW trace, the volume label was successfully read.  So, it is
possible that there is something in the volume label that is also
causing the behavior.  I personally think that is a stretch, but it is
possible.

The trace does not contain the IPL commands, so it would seem that the
trace was started after the IPL.  So it is possible that the contents of
SENSE ID (device and CU type and model numbers) or READ DEVICE
CHARACTERISTICS (neither in the trace) is leading to the unsupported
commands.

Harold Grovesteen


On Fri, 2017-04-21 at 16:19 +0200, Franz Josef Pohlen
[hidden email] [hercules-390] wrote:

> I have just seen this VM message in the log after the command reject.
>
> HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = N/A HPF
>
> I wonder if the word HPF may point to a check of zVM if High Perfomance Ficon is available and Hercules doesn't react on this as expected.
>
> Am 21.04.2017 um 14:35 schrieb Franz Josef Pohlen
> [hidden email] [hercules-390]:
> > Hello all,
> >
> > as the Hercules 4.0 doesn't seem to be working for the current zvm. I
> > will try to get the zvm 6.4 running with Hercules 3.12 (Win 64Bit). I
> > get an error during IPL after I have confirmed the time question. It
> > cancels with command reject on the IPL device. For documentation I have
> > started a ccw trace on the ipl device and ipled the zvm 6.4 with
> > cons=sysc. So the zVM messages and the ccw trace is in the log. I hope
> > that someone of you developers can see there what's going wrong. My old
> > zvm 6.3 starts without problems on this hercules configuration. I have
> > also attached my hercules config. There might still be some settings for
> > Hercules 4.0 but they were ignored during start with Hercules 3.12.
> >
> > Thanks in advance for your help and have a nice weekend
> >
> > Franz Josef
> >
> > Hercules Config
> >
> >
> > 1206    3390    E:/daten/ipl390/dasd/640res.zvm cu=3990
> > sf=E:/daten/ipl390/dasd/640res_1.zvm


Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
Hi, This is related to Transport Mode I/O (ORB Byte 5, Bit x'04'). CCW
X'E7' is the 'Prefix' command and valid for ECKD in Command mode.
Best regards,

On Fri, Apr 21, 2017 at 11:01 AM, Harold Grovesteen [hidden email]
[hercules-390] <[hidden email]> wrote:

>
>
> Entirely possible. Could be implying a level of functionality not
> available with Hercules. How to get the OS to do something else is way
> beyond my personal knowledge. Perhaps a CU model number as opposed to
> omitting it might help or a change to the CU type. Just speculation.
>
> The documentation I have that does not have this command is for storage
> servers 2105 models E10, E20, F10 and F20. If you could get the OS to
> think the DASD is on one of these control units, it might change the
> behavior.
>
> In the CCW trace, the volume label was successfully read. So, it is
> possible that there is something in the volume label that is also
> causing the behavior. I personally think that is a stretch, but it is
> possible.
>
> The trace does not contain the IPL commands, so it would seem that the
> trace was started after the IPL. So it is possible that the contents of
> SENSE ID (device and CU type and model numbers) or READ DEVICE
> CHARACTERISTICS (neither in the trace) is leading to the unsupported
> commands.
>
> Harold Grovesteen
>
> On Fri, 2017-04-21 at 16:19 +0200, Franz Josef Pohlen
> [hidden email] [hercules-390] wrote:
> > I have just seen this VM message in the log after the command reject.
> >
> > HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = N/A HPF
> >
> > I wonder if the word HPF may point to a check of zVM if High Perfomance
> Ficon is available and Hercules doesn't react on this as expected.
> >
> > Am 21.04.2017 um 14:35 schrieb Franz Josef Pohlen
> > [hidden email] [hercules-390]:
> > > Hello all,
> > >
> > > as the Hercules 4.0 doesn't seem to be working for the current zvm. I
> > > will try to get the zvm 6.4 running with Hercules 3.12 (Win 64Bit). I
> > > get an error during IPL after I have confirmed the time question. It
> > > cancels with command reject on the IPL device. For documentation I have
> > > started a ccw trace on the ipl device and ipled the zvm 6.4 with
> > > cons=sysc. So the zVM messages and the ccw trace is in the log. I hope
> > > that someone of you developers can see there what's going wrong. My old
> > > zvm 6.3 starts without problems on this hercules configuration. I have
> > > also attached my hercules config. There might still be some settings
> for
> > > Hercules 4.0 but they were ignored during start with Hercules 3.12.
> > >
> > > Thanks in advance for your help and have a nice weekend
> > >
> > > Franz Josef
> > >
> > > Hercules Config
> > >
> > >
> > > 1206 3390 E:/daten/ipl390/dasd/640res.zvm cu=3990
> > > sf=E:/daten/ipl390/dasd/640res_1.zvm
>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
In reply to this post by Hercules390 - General mailing list
It is only a snip of the log. The whole log is more than 30000 records
(2,5 mb). Zipped it is only 240k but I think the list server does not
support attachments. So where I can send or upload the complete log?

Am 21.04.2017 um 17:01 schrieb Harold Grovesteen [hidden email]
[hercules-390]:

> Entirely possible.  Could be implying a level of functionality not
> available with Hercules.  How to get the OS to do something else is way
> beyond my personal knowledge.  Perhaps a CU model number as opposed to
> omitting it might help or a change to the CU type.  Just speculation.
>
> The documentation I have that does not have this command is for storage
> servers 2105 models E10, E20, F10 and F20.  If you could get the OS to
> think the DASD is on one of these control units, it might change the
> behavior.
>
> In the CCW trace, the volume label was successfully read.  So, it is
> possible that there is something in the volume label that is also
> causing the behavior.  I personally think that is a stretch, but it is
> possible.
>
> The trace does not contain the IPL commands, so it would seem that the
> trace was started after the IPL.  So it is possible that the contents of
> SENSE ID (device and CU type and model numbers) or READ DEVICE
> CHARACTERISTICS (neither in the trace) is leading to the unsupported
> commands.
>
> Harold Grovesteen
>
>
> On Fri, 2017-04-21 at 16:19 +0200, Franz Josef Pohlen
> [hidden email] [hercules-390] wrote:
> > I have just seen this VM message in the log after the command reject.
> >
> > HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = N/A HPF
> >
> > I wonder if the word HPF may point to a check of zVM if High Perfomance Ficon is available and Hercules doesn't react on this as expected.
> >
> > Am 21.04.2017 um 14:35 schrieb Franz Josef Pohlen
> > [hidden email] [hercules-390]:
> > > Hello all,
> > >
> > > as the Hercules 4.0 doesn't seem to be working for the current zvm. I
> > > will try to get the zvm 6.4 running with Hercules 3.12 (Win 64Bit). I
> > > get an error during IPL after I have confirmed the time question. It
> > > cancels with command reject on the IPL device. For documentation I have
> > > started a ccw trace on the ipl device and ipled the zvm 6.4 with
> > > cons=sysc. So the zVM messages and the ccw trace is in the log. I hope
> > > that someone of you developers can see there what's going wrong. My old
> > > zvm 6.3 starts without problems on this hercules configuration. I have
> > > also attached my hercules config. There might still be some settings for
> > > Hercules 4.0 but they were ignored during start with Hercules 3.12.
> > >
> > > Thanks in advance for your help and have a nice weekend
> > >
> > > Franz Josef
> > >
> > > Hercules Config
> > >
> > >
> > > 1206    3390    E:/daten/ipl390/dasd/640res.zvm cu=3990
> > > sf=E:/daten/ipl390/dasd/640res_1.zvm
>
>
>
>
> ------------------------------------
> Posted by: Harold Grovesteen <[hidden email]>
> ------------------------------------
>
> Community email addresses:
>    Post message: [hidden email]
>    Subscribe:    [hidden email]
>    Unsubscribe:  [hidden email]
>    List owner:   [hidden email]
>
> Files and archives at:
>    http://groups.yahoo.com/group/hercules-390
>
> Get the latest version of Hercules from:
>    http://www.hercules-390.org
>
>
> ------------------------------------
>
> Yahoo Groups Links
>
>
>
>


--
kind regards
Franz Josef Pohlen
Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
Hello Harold,

I have tried to change the CU to 3990-3 and on a second try to 3990-3
and the parameter syncio but nothing helps. The 2105 CU is not accepted
(type not in dasd table). The documentaion says that 3390 devices need
3990 CU. You can only select between 3990-3 and 3990-6. Nothing helps
unfortunately.

Am 21.04.2017 um 17:45 schrieb Franz Josef Pohlen
[hidden email] [hercules-390]:

> It is only a snip of the log. The whole log is more than 30000 records
> (2,5 mb). Zipped it is only 240k but I think the list server does not
> support attachments. So where I can send or upload the complete log?
>
> Am 21.04.2017 um 17:01 schrieb Harold Grovesteen [hidden email]
> [hercules-390]:
> > Entirely possible.  Could be implying a level of functionality not
> > available with Hercules.  How to get the OS to do something else is way
> > beyond my personal knowledge.  Perhaps a CU model number as opposed to
> > omitting it might help or a change to the CU type.  Just speculation.
> >
> > The documentation I have that does not have this command is for storage
> > servers 2105 models E10, E20, F10 and F20.  If you could get the OS to
> > think the DASD is on one of these control units, it might change the
> > behavior.
> >
> > In the CCW trace, the volume label was successfully read.  So, it is
> > possible that there is something in the volume label that is also
> > causing the behavior.  I personally think that is a stretch, but it is
> > possible.
> >
> > The trace does not contain the IPL commands, so it would seem that the
> > trace was started after the IPL.  So it is possible that the contents of
> > SENSE ID (device and CU type and model numbers) or READ DEVICE
> > CHARACTERISTICS (neither in the trace) is leading to the unsupported
> > commands.
> >
> > Harold Grovesteen
> >
> >
> > On Fri, 2017-04-21 at 16:19 +0200, Franz Josef Pohlen
> > [hidden email] [hercules-390] wrote:
> > > I have just seen this VM message in the log after the command reject.
> > >
> > > HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = N/A HPF
> > >
> > > I wonder if the word HPF may point to a check of zVM if High Perfomance Ficon is available and Hercules doesn't react on this as expected.
> > >
> > > Am 21.04.2017 um 14:35 schrieb Franz Josef Pohlen
> > > [hidden email] [hercules-390]:
> > > > Hello all,
> > > >
> > > > as the Hercules 4.0 doesn't seem to be working for the current zvm. I
> > > > will try to get the zvm 6.4 running with Hercules 3.12 (Win 64Bit). I
> > > > get an error during IPL after I have confirmed the time question. It
> > > > cancels with command reject on the IPL device. For documentation I have
> > > > started a ccw trace on the ipl device and ipled the zvm 6.4 with
> > > > cons=sysc. So the zVM messages and the ccw trace is in the log. I hope
> > > > that someone of you developers can see there what's going wrong. My old
> > > > zvm 6.3 starts without problems on this hercules configuration. I have
> > > > also attached my hercules config. There might still be some settings for
> > > > Hercules 4.0 but they were ignored during start with Hercules 3.12.
> > > >
> > > > Thanks in advance for your help and have a nice weekend
> > > >
> > > > Franz Josef
> > > >
> > > > Hercules Config
> > > >
> > > >
> > > > 1206    3390    E:/daten/ipl390/dasd/640res.zvm cu=3990
> > > > sf=E:/daten/ipl390/dasd/640res_1.zvm
> >
> >
> >
> >
> > ------------------------------------
> > Posted by: Harold Grovesteen <[hidden email]>
> > ------------------------------------
> >
> > Community email addresses:
> >    Post message: [hidden email]
> >    Subscribe:    [hidden email]
> >    Unsubscribe:  [hidden email]
> >    List owner:   [hidden email]
> >
> > Files and archives at:
> >    http://groups.yahoo.com/group/hercules-390
> >
> > Get the latest version of Hercules from:
> >    http://www.hercules-390.org
> >
> >
> > ------------------------------------
> >
> > Yahoo Groups Links
> >
> >
> >
> >
>
>


--
kind regards
Franz Josef Pohlen
Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
2105 is a shark.  I never got that to work with P390/Linux.  I'm not
surprised you cannot either.

On 04/21/2017 06:11 PM, Franz Josef Pohlen [hidden email]
[hercules-390] wrote:

>
>
> Hello Harold,
>
> I have tried to change the CU to 3990-3 and on a second try to 3990-3
> and the parameter syncio but nothing helps. The 2105 CU is not accepted
> (type not in dasd table). The documentaion says that 3390 devices need
> 3990 CU. You can only select between 3990-3 and 3990-6. Nothing helps
> unfortunately.
>
> Am 21.04.2017 um 17:45 schrieb Franz Josef Pohlen
> [hidden email] [hercules-390]:
Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
In reply to this post by Hercules390 - General mailing list
Hi, This is related to Transport Mode I/O (ORB Byte 5, Bit x'04'). CCW
X'E7' is the 'Prefix' command and valid for ECKD in Command mode.
Best regards,

On Fri, Apr 21, 2017 at 12:11 PM, Franz Josef Pohlen
[hidden email] [hercules-390] <[hidden email]>
wrote:

>
>
> Hello Harold,
>
> I have tried to change the CU to 3990-3 and on a second try to 3990-3
> and the parameter syncio but nothing helps. The 2105 CU is not accepted
> (type not in dasd table). The documentaion says that 3390 devices need
> 3990 CU. You can only select between 3990-3 and 3990-6. Nothing helps
> unfortunately.
>
> Am 21.04.2017 um 17:45 schrieb Franz Josef Pohlen
> [hidden email] [hercules-390]:
> > It is only a snip of the log. The whole log is more than 30000 records
> > (2,5 mb). Zipped it is only 240k but I think the list server does not
> > support attachments. So where I can send or upload the complete log?
> >
> > Am 21.04.2017 um 17:01 schrieb Harold Grovesteen [hidden email]
> > [hercules-390]:
> > > Entirely possible. Could be implying a level of functionality not
> > > available with Hercules. How to get the OS to do something else is way
> > > beyond my personal knowledge. Perhaps a CU model number as opposed to
> > > omitting it might help or a change to the CU type. Just speculation.
> > >
> > > The documentation I have that does not have this command is for storage
> > > servers 2105 models E10, E20, F10 and F20. If you could get the OS to
> > > think the DASD is on one of these control units, it might change the
> > > behavior.
> > >
> > > In the CCW trace, the volume label was successfully read. So, it is
> > > possible that there is something in the volume label that is also
> > > causing the behavior. I personally think that is a stretch, but it is
> > > possible.
> > >
> > > The trace does not contain the IPL commands, so it would seem that the
> > > trace was started after the IPL. So it is possible that the contents of
> > > SENSE ID (device and CU type and model numbers) or READ DEVICE
> > > CHARACTERISTICS (neither in the trace) is leading to the unsupported
> > > commands.
> > >
> > > Harold Grovesteen
> > >
> > >
> > > On Fri, 2017-04-21 at 16:19 +0200, Franz Josef Pohlen
> > > [hidden email] [hercules-390] wrote:
> > > > I have just seen this VM message in the log after the command reject.
> > > >
> > > > HCPERP6301I CHANNEL COMMAND WORD COMMAND CODE = N/A HPF
> > > >
> > > > I wonder if the word HPF may point to a check of zVM if High
> Perfomance Ficon is available and Hercules doesn't react on this as
> expected.
> > > >
> > > > Am 21.04.2017 um 14:35 schrieb Franz Josef Pohlen
> > > > [hidden email] [hercules-390]:
> > > > > Hello all,
> > > > >
> > > > > as the Hercules 4.0 doesn't seem to be working for the current
> zvm. I
> > > > > will try to get the zvm 6.4 running with Hercules 3.12 (Win
> 64Bit). I
> > > > > get an error during IPL after I have confirmed the time question.
> It
> > > > > cancels with command reject on the IPL device. For documentation I
> have
> > > > > started a ccw trace on the ipl device and ipled the zvm 6.4 with
> > > > > cons=sysc. So the zVM messages and the ccw trace is in the log. I
> hope
> > > > > that someone of you developers can see there what's going wrong.
> My old
> > > > > zvm 6.3 starts without problems on this hercules configuration. I
> have
> > > > > also attached my hercules config. There might still be some
> settings for
> > > > > Hercules 4.0 but they were ignored during start with Hercules 3.12.
> > > > >
> > > > > Thanks in advance for your help and have a nice weekend
> > > > >
> > > > > Franz Josef
> > > > >
> > > > > Hercules Config
> > > > >
> > > > >
> > > > > 1206 3390 E:/daten/ipl390/dasd/640res.zvm cu=3990
> > > > > sf=E:/daten/ipl390/dasd/640res_1.zvm
> > >
> > >
> > >
> > >
> > > ------------------------------------
> > > Posted by: Harold Grovesteen <[hidden email]>
> > > ------------------------------------
> > >
> > > Community email addresses:
> > > Post message: [hidden email]
> > > Subscribe: [hidden email]
> > > Unsubscribe: [hidden email]
> > > List owner: [hidden email]
> > >
> > > Files and archives at:
> > > http://groups.yahoo.com/group/hercules-390
> > >
> > > Get the latest version of Hercules from:
> > > http://www.hercules-390.org
> > >
> > >
> > > ------------------------------------
> > >
> > > Yahoo Groups Links
> > >
> > >
> > >
> > >
> >
> >
>
> --
> kind regards
> Franz Josef Pohlen
>
>
Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
Hi Franz,

as I said I can IPL z/VM 6.4 in Hercules 3.12 without any problem.

My environment: Windows/XP - Hercules 3.12 (of course 32 bit) -
VMCOM1 : 1000
M01RES  : 1002 (ipl device)

this is the snip of the trace: as you can see the directory is brought online and there's no evidence of the CCW E7 that causes a command reject in your system.
...............................................................................................................
  03:35:07 z/VM  V6 R4.0  SERVICE LEVEL 1601 (64-BIT)
  03:35:07 SYSTEM NUCLEUS CREATED ON 2017-02-09 AT 15:28:23, LOADED FROM M01RES
  03:35:07
  03:35:07 ****************************************************************
  03:35:07 * LICENSED MATERIALS - PROPERTY OF IBM*                        *
  03:35:07 *                                                              *
  03:35:07 * 5741-A07 (C) COPYRIGHT IBM CORP. 1983, 2016. ALL RIGHTS      *
  03:35:07 * RESERVED. US GOVERNMENT USERS RESTRICTED RIGHTS - USE,       *
  03:35:07 * DUPLICATION OR DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE     *
  03:35:07 * CONTRACT WITH IBM CORP.                                      *
  03:35:07 *                                                              *
  03:35:07 * * TRADEMARK OF INTERNATIONAL BUSINESS MACHINES.              *
  03:35:07 ****************************************************************
  03:35:07
  03:35:07 HCPZCO6718I Using parm disk 1 on volume VMCOM1 (device 1000).
  03:35:07 HCPZCO6718I Parm disk resides on cylinders 1 through 120.
  1002:start i/o file[1] bufcur 0 cache[29]
  1002:synchronous  I/O ccw addr 18a9c2a8
  HHCCP048I 1002:CCW=63400010 18A9C2C0=>40C00050 00000000 00000000 00000000  {.&............
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=47600010 18A9C2D0=>16000001 00000000 00000000 03000000 ................
  1002:HHCDA038I seeking to cyl 0 head 0
  1002:HHCDA041I read count orientation is index
  1002:HHCDA043I cyl 0 head 0 record 0 kl 0 dl 8 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 0 head 0 record 1 kl 0 dl 24 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 0 head 0 record 2 kl 0 dl 4096 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 0 head 0 record 3 kl 4 dl 80 of 0
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=86200050 18A9D0D8=>00000000 00000000 00000000 00000000 ................
  1002:HHCDA045I read data 80 bytes
  HHCCP075I 1002:Stat=0C00 Count=0000 =>E5D6D3F1 D4F0F1D9 C5E2F000 00000005 VOL1M01RES0.....
  1002:end i/o bufcur 0 cache[29] waiters 0
  HHCCP050I 1002:SCSW=00C04007 Stat=0C00 Count=0000  CCW=18A9C2C0
  1002:start i/o file[1] bufcur 0 cache[29]
  1002:synchronous  I/O ccw addr 18a9c318
  HHCCP048I 1002:CCW=63400010 18A9C330=>40C01000 00000000 00000000 00000000  {..............
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=47600010 18A9C340=>16000001 00000000 00000000 04000000 ................
  1002:HHCDA038I seeking to cyl 0 head 0
  1002:HHCDA041I read count orientation is index
  1002:HHCDA043I cyl 0 head 0 record 0 kl 0 dl 8 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 0 head 0 record 1 kl 0 dl 24 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 0 head 0 record 2 kl 0 dl 4096 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 0 head 0 record 3 kl 4 dl 80 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 0 head 0 record 4 kl 0 dl 4096 of 0
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=86201000 182DA000=>00000000 00000000 00000000 00000000 ................
  1002:HHCDA045I read data 4096 bytes
  HHCCP075I 1002:Stat=0C00 Count=0000 =>08CC8008 00000000 00000000 C0000000 ............{...
  1002:end i/o bufcur 0 cache[29] waiters 0
  HHCCP050I 1002:SCSW=00C04007 Stat=0C00 Count=0000  CCW=18A9C330
  1002:start i/o file[1] bufcur 0 cache[29]
  1002:synchronous  I/O ccw addr 18b68050
  HHCCP048I 1002:CCW=63400010 18B65A20=>80C01000 00000000 00000000 2720000E .{..............
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=47400010 18B68040=>16000001 00010000 00010000 02180000 ................
  1002:HHCDA038I seeking to cyl 1 head 0
  1002:read  trk   15 (synchronous)
  1002:0 rdtrk     15
  1002:0 rdtrk[44] 15 syncio cache miss
  1002:asynchronous I/O ccw addr 18b68058
  HHCCP048I 1002:CCW=47400010 18B68040=>16000001 00010000 00010000 02180000 ................
  1002:HHCDA038I seeking to cyl 1 head 0
  1002:read  trk   15 (asynchronous)
  1002:0 rdtrk     15
  1002:0 rdtrk[44] 15 cache miss
  1002:0 rdtrk[44] 15 dropping 1002:1389 from cache
  1002:0 rdtrk[44] 15 buf 226FCC98 len 56832
  1002:trk[15] read_trkimg
  1002:file[1] l2[0,15] trk[15] read_l2ent 0xffffffff
  1002:file[0] l2[0,15] trk[15] read_l2ent 0xd2c
  1002:file[0] read_l2 0 active 0 0 0
  1002:file[0] l2[0,15] trk[15] read_l2ent 0x678de8 5382 5382
  1002:file[0] fd[18] read, off 0x678de8 len 5382
  1002:0 rdtrk[44] 15 complete buf 226FCC98:0100010000
  1002:uncompress comp 1 len 5382 maxlen 56832 trk 15
  1002:uncompress zlib newlen 49277 rc 0
  1002:validating trk 15 len 49277 0000010000 0001000000000008
  1002:read  trk   15 uncompressed len 49277
  1002:HHCDA041I read count orientation is index
  1002:HHCDA043I cyl 1 head 0 record 0 kl 0 dl 8 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 1 head 0 record 1 kl 0 dl 4096 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 1 head 0 record 2 kl 0 dl 4096 of 0
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=86441000 18B68070=>00000000 182D9000 00000001 80E1CE00 ................
  1002:HHCDA045I read data 4096 bytes
  HHCCP064I 1002:IDAW=00000000182D9000 Len=1000
  1002:---------------------=>00000330 01020000 C4C9D9C5 C3E3D6D9 ........DIRECTOR
  HHCCP075I 1002:Stat=0C00 Count=0000 =>00000000 182D9000 00000001 80E1CE00 ................
  HHCCP048I 1002:CCW=03020000 18B680A0=>20441000 18B680B0 03200000 18B680E0 ...............\
  1002:end i/o bufcur 15 cache[44] waiters 0
  HHCCP073I Device 1002 suspended
  HHCCP050I 1002:SCSW=08C04029 Stat=0000 Count=0000  CCW=18B68070
  HHCCP074I Device 1002 resumed
  HHCCP062I 1002: Resume subchannel: cc=0
  1002:start i/o file[1] bufcur 15 cache[44]
  HHCCP048I 1002:CCW=08000000 18B68090=>63400010 18B65A20 47400010 18B68080 . ....!.. ......
  HHCCP048I 1002:CCW=63400010 18B65A20=>80C01000 00000000 00000000 2720000E .{..............
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=47400010 18B68080=>16000001 00010000 00010000 02180000 ................
  1002:HHCDA038I seeking to cyl 1 head 0
  1002:HHCDA041I read count orientation is index
  1002:HHCDA043I cyl 1 head 0 record 0 kl 0 dl 8 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 1 head 0 record 1 kl 0 dl 4096 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 1 head 0 record 2 kl 0 dl 4096 of 0
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=86441000 18B680B0=>00000000 07DF3000 00000001 80E1CE00 ................
  1002:HHCDA045I read data 4096 bytes
  HHCCP064I 1002:IDAW=0000000007DF3000 Len=1000
  1002:---------------------=>00000330 01020000 C4C9D9C5 C3E3D6D9 ........DIRECTOR
  HHCCP075I 1002:Stat=0C00 Count=0000 =>00000000 07DF3000 00000001 80E1CE00 ................
  HHCCP048I 1002:CCW=03020000 18B680E0=>20441000 18B680F0 03200000 18B68120 .......0......a.
  1002:end i/o bufcur 15 cache[44] waiters 0
  HHCCP073I Device 1002 suspended
  HHCCP050I 1002:SCSW=08C04029 Stat=0000 Count=0000  CCW=18B680B0
  HHCCP062I 1002: Resume subchannel: cc=0
  HHCCP074I Device 1002 resumed
  1002:start i/o file[1] bufcur 15 cache[44]
  HHCCP048I 1002:CCW=08000000 18B680D0=>63400010 18B65A20 47400010 18B680C0 . ....!.. .....{
  HHCCP048I 1002:CCW=63400010 18B65A20=>80C01000 00000000 00000000 2720000E .{..............
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=47400010 18B680C0=>16000001 00010000 00010000 01060000 ................
  1002:HHCDA038I seeking to cyl 1 head 0
  1002:HHCDA041I read count orientation is index
  1002:HHCDA043I cyl 1 head 0 record 0 kl 0 dl 8 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 1 head 0 record 1 kl 0 dl 4096 of 0
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=86441000 18B680F0=>00000000 182D9000 00000001 80F00A00 .............0..
  1002:HHCDA045I read data 4096 bytes
  HHCCP064I 1002:IDAW=00000000182D9000 Len=1000
  1002:---------------------=>00000000 00010000 C4C9D9C5 C3E3D6D9 ........DIRECTOR
  HHCCP075I 1002:Stat=0C00 Count=0000 =>00000000 182D9000 00000001 80F00A00 .............0..
  HHCCP048I 1002:CCW=03020000 18B68120=>20441000 18B68130 03200000 18B68160 ......a.......a-
  1002:end i/o bufcur 15 cache[44] waiters 0
  HHCCP073I Device 1002 suspended
  HHCCP050I 1002:SCSW=08C04029 Stat=0000 Count=0000  CCW=18B680F0
  HHCCP062I 1002: Resume subchannel: cc=0
  HHCCP074I Device 1002 resumed
  1002:start i/o file[1] bufcur 15 cache[44]
  HHCCP048I 1002:CCW=08000000 18B68110=>63400010 18B65A20 47400010 18B68100 . ....!.. ....a.
  HHCCP048I 1002:CCW=63400010 18B65A20=>80C01000 00000000 00000000 2720000E .{..............
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=47400010 18B68100=>16000001 00010000 00010000 03290000 ................
  1002:HHCDA038I seeking to cyl 1 head 0
  1002:HHCDA041I read count orientation is index
  1002:HHCDA043I cyl 1 head 0 record 0 kl 0 dl 8 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 1 head 0 record 1 kl 0 dl 4096 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 1 head 0 record 2 kl 0 dl 4096 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 1 head 0 record 3 kl 0 dl 4096 of 0
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=86441000 18B68130=>00000000 07DF3000 00000001 80F00A00 .............0..
  1002:HHCDA045I read data 4096 bytes
  HHCCP064I 1002:IDAW=0000000007DF3000 Len=1000
  1002:---------------------=>00000000 00010000 D7D6E2C9 E740E4C9 ........POSIX UI
  HHCCP075I 1002:Stat=0C00 Count=0000 =>00000000 07DF3000 00000001 80F00A00 .............0..
  HHCCP048I 1002:CCW=03020000 18B68160=>20441000 18B68170 03200000 18B681A0 ......a.......a.
  1002:end i/o bufcur 15 cache[44] waiters 0
  HHCCP073I Device 1002 suspended
  HHCCP050I 1002:SCSW=08C04029 Stat=0000 Count=0000  CCW=18B68130
  HHCCP062I 1002: Resume subchannel: cc=0
  HHCCP074I Device 1002 resumed
  1002:start i/o file[1] bufcur 15 cache[44]
  HHCCP048I 1002:CCW=08000000 18B68150=>63400010 18B65A20 47400010 18B68140 . ....!.. ....a
  HHCCP048I 1002:CCW=63400010 18B65A20=>80C01000 00000000 00000000 2720000E .{..............
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=47400010 18B68140=>16000001 00010000 00010000 043B0000 ................
  1002:HHCDA038I seeking to cyl 1 head 0
  1002:HHCDA041I read count orientation is index
  1002:HHCDA043I cyl 1 head 0 record 0 kl 0 dl 8 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 1 head 0 record 1 kl 0 dl 4096 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 1 head 0 record 2 kl 0 dl 4096 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 1 head 0 record 3 kl 0 dl 4096 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 1 head 0 record 4 kl 0 dl 4096 of 0
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=86441000 18B68170=>00000000 182D9000 00000001 80F00A00 .............0..
  1002:HHCDA045I read data 4096 bytes
  HHCCP064I 1002:IDAW=00000000182D9000 Len=1000
  1002:---------------------=>00000000 00090000 D7D6E2C9 E740C7C9 ........POSIX GI
  HHCCP075I 1002:Stat=0C00 Count=0000 =>00000000 182D9000 00000001 80F00A00 .............0..
  HHCCP048I 1002:CCW=03020000 18B681A0=>20441000 18B681B0 03200000 18B681E0 ......a.......a\
  1002:end i/o bufcur 15 cache[44] waiters 0
  HHCCP073I Device 1002 suspended
  HHCCP050I 1002:SCSW=08C04029 Stat=0000 Count=0000  CCW=18B68170
  HHCCP062I 1002: Resume subchannel: cc=0
  HHCCP074I Device 1002 resumed
  1002:start i/o file[1] bufcur 15 cache[44]
  HHCCP048I 1002:CCW=08000000 18B68190=>63400010 18B65A20 47400010 18B68180 . ....!.. ....a.
  HHCCP048I 1002:CCW=63400010 18B65A20=>80C01000 00000000 00000000 2720000E .{..............
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=47400010 18B68180=>16000001 00150000 00150000 01060000 ................
  1002:HHCDA038I seeking to cyl 21 head 0
  1002:read  trk   315 (asynchronous)
  1002:0 rdtrk     315
  1002:0 rdtrk[115] 315 cache miss
  1002:0 rdtrk[115] 315 dropping 1002:1231 from cache
  1002:0 rdtrk[115] 315 buf 230F0048 len 56832
  1002:trk[315] read_trkimg
  1002:file[1] l2[1,59] trk[315] read_l2ent 0xd2c
  1002:file[1] read_l2 1 active 0 0 0
  1002:l2[1,1] cache[799] miss
  1002:file[1] fd[19] read, off 0xd2c len 2048
  1002:file[1] cache[799] l2[1] read offset 0xd2c
  1002:file[1] l2[1,59] trk[315] read_l2ent 0x29eb9 1422 1422
  1002:file[1] fd[19] read, off 0x29eb9 len 1422
  1002:0 rdtrk[115] 315 complete buf 230F0048:0100150000
  1002:uncompress comp 1 len 1422 maxlen 56832 trk 315
  1002:uncompress zlib newlen 49277 rc 0
  1002:validating trk 315 len 49277 0000150000 0015000000000008
  1002:read  trk   315 uncompressed len 49277
  1002:HHCDA041I read count orientation is index
  1002:HHCDA043I cyl 21 head 0 record 0 kl 0 dl 8 of 0
  1002:HHCDA041I read count orientation is count
  1002:HHCDA043I cyl 21 head 0 record 1 kl 0 dl 4096 of 0
  HHCCP075I 1002:Stat=0C00 Count=0000
  HHCCP048I 1002:CCW=86441000 18B681B0=>00000000 07DF1000 00000001 80F02E00 .............0..
  1002:HHCDA045I read data 4096 bytes
  HHCCP064I 1002:IDAW=0000000007DF1000 Len=1000
  1002:---------------------=>C8C3D7C3 D2D7C2D2 00000000 00000000 HCPCKPBK........
  HHCCP075I 1002:Stat=0C00 Count=0000 =>00000000 07DF1000 00000001 80F02E00 .............0..
  HHCCP048I 1002:CCW=03020000 18B681E0=>20441000 18B681F0 03200000 18B68220 ......a0......b.
  1002:end i/o bufcur 315 cache[115] waiters 0
  HHCCP073I Device 1002 suspended
  HHCCP050I 1002:SCSW=08C04029 Stat=0000 Count=0000  CCW=18B681B0
  03:35:07 The directory on volume M01RES at address 1002 has been brought online.
.................................................................................................................................
I'm available for further tests if you like :-)

Regards

Paul
Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
hello all,

 exactly the same problem.
 any fix?
 what is the config file of the hercules 3.12 XP (32 bits) successfull ipl?
 

 regards
Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
Am 31.05.2017 um 10:47 schrieb [hidden email] [hercules-390]:

>
>
> hello all,
>
> exactly the same problem.
> any fix?
> what is the config file of the hercules 3.12 XP (32 bits) successfull ipl?
>
> regards
>
>
>

--
kind regards
Franz Josef Pohlen
Reply | Threaded
Open this post in threaded view
|

Re: zVM 6.4 on Hercules 3.12 does not start

Hercules390 - General mailing list
Hi,
I can IPL z/VM 6.4 with Hercules 3.09 - 3.11 - 3.12 (Windows XP)

Not tested with Hercules 3.10 but I bet it will be OK :)

With Hyperion (version 8213)I get a PRG004 after the first messages on the console

Here's my config file:
-----------------------------------------------------------------------------
#
# Hercules Emulator Control file - z/VM 6.4 ...

#

# System parameters
#

# definitions for Hercules 3.12 or Hercules 4.0 (Hyperion)

# definitions for Hercules 3.12
  ARCHMODE            Z/ARCH                 # Architecture mode


# definitions for Hyperion
# ARCHLVL   z/Arch
# ARCHLVL ENABLE STFL_EXTENDED
# ARCHLVL   ENABLE ASN_LX_REUSE
# ARCHLVL   ENABLE   bit44



DEFSYM CU3390 "cu=3990"

CNSLPORT  3270
CONKPALV  (3,1,10)
CPUMODEL  2096
CPUSERIAL 01131C
ECPSVM    NO
#HTTPPORT  8081
LOADPARM  001F....
LPARNAME  ZVM64
MAINSIZE  396
MOUNTED_TAPE_REINIT  DISALLOW
NUMCPU    3
OSTAILOR  VM
PANRATE   50
PGMPRDOS  LICENSED
SHCMDOPT  NODIAG8
SYSEPOCH  1900
TIMERINT  50
TZOFFSET  -0000
XPNDSIZE  128
YROFFSET  0

HERCPRIO  0
TODPRIO   -20
DEVPRIO   8
CPUPRIO   15
CCKD            ra=9,raq=16,rat=16,wr=8,gcparm=4
# Card Readers

000C 3505

# Card Punches

000D 3525  Q:/ZVM-6-1-Dave/punch00d.txt ascii crlf

# Line Printers

000E 3211  Q:/ZVM-6-1-Dave/print00e.txt crlf

# Integrated 3270 terminal
#0000    SYSG

# Display Terminals

# 001F 3270    *
0020 3270
0021 3270
0022 3270
0023 3270



# DASD Devices Z/VM 6.1 x STARTER Z/VM 6.4

200 3390    Q:/zVM-6.4/1000.dasd.cckd  ro sf=q:/zVM-6.4/shadow/1000.dasd_1 #cu=3990
201 3390    Q:/zVM-6.4/1001.dasd.cckd  ro sf=q:/zVM-6.4/shadow/2000.dasd_1 #cu=3990
202 3390    Q:/zVM-6.4/1002.dasd.cckd  ro sf=q:/zVM-6.4/shadow/3000.dasd_1 #cu=3990

# DASD Devices z/VM 6.4 - original addresses (VMCOM1 must be 1000 - SYSTEM.CONFIG is in minidisk CF0)

1000    3390    Q:/zVM-6.4/VMCOM1.CCKD ro sf=q:/zVM-6.4/shadow/vmcom1_1 #cu=3990
1001    3390    Q:/zVM-6.4/640RL1.CCKD ro sf=q:/zVM-6.4/shadow/640rl1_1 #cu=3990
1002    3390    Q:/zVM-6.4/M01RES.CCKD ro sf=q:/zVM-6.4/shadow/m01res_1 #cu=3990
1003    3390    Q:/zVM-6.4/M01S01.CCKD ro sf=q:/zVM-6.4/shadow/m01s01_1 #cu=3990
1004    3390    Q:/zVM-6.4/M01P01.CCKD ro sf=q:/zVM-6.4/shadow/m01p01_1 #cu=3990
1005    3390    Q:/zVM-6.4/M01W01.CCKD ro sf=q:/zVM-6.4/shadow/m01w01_1 #cu=3990
1006    3390    Q:/zVM-6.4/M01W02.CCKD  cu=3990

# cu=3990-3 gives error with shadow files #

# TAPE Devices
# 0580 3480   /home/dave/Desktop/VMESA24/sdiskadd.580
# 0580      3480   /z/VMESA24/VMPPNSS.580

# 0590    3590    C:/hercules/dasd/zvm53/HERCULES.000000.comp.het
# chunksize=4096 compress=1 method=1 level=4 maxsizeM=170
# eotmargin=131072

# CTC Adapters

# 0E20,0E21 CTCI 192.168.128.201 192.168.128.120
#044A LCS     -n   /dev/net/tun   192.168.128.200
#044B LCS     -n   /dev/net/tun   192.168.128.200

__________________________________________________________

Best regards

Paul
12