Oppolzer - Informatik / Blog

Hello,

I have done this some time ago and I don't recall the details, but it was
difficult.

My config file looks like this:

141     3350    /herc370/vm/vm3350-1.141.cckd ro sf=/herc370/shadows/vm3350_1_
241     3350    /herc370/vm/vm3350-2.241.cckd ro sf=/herc370/shadows/vm3350_2_
34f     3350    /herc370/vm/vm3350-3.34f.cckd ro sf=/herc370/shadows/vm3350_3_
440     3350    /herc370/vm/vm3350-4.440.cckd ro sf=/herc370/shadows/vm3350_4_
540     3350    /herc370/vm/vm3350-5.540.cckd ro sf=/herc370/shadows/vm3350_5_
541     3350    /herc370/vm/vmpack6.dsk       ro sf=/herc370/shadows/vm3350_6_

the five disks up to 540 were included in the standard configuration, and 541 is
the one that I added.

I recall that I had some problems because I first thought that I could choose
the device number freely, but that is not true; the device number has to be a
3350 in a certain definition macro (which I did not want to change, because if I
did, I had to build the system again, in my understanding), so it works only
with certain device numbers like 541 for example.

The file vmpack6.dsk looks very different from the others regarding size:

 Volume in Laufwerk C: hat keine Bezeichnung.
 Volumeseriennummer: AC72-DC5A

 Verzeichnis von C:\herc370\vm

08.12.2014  09:41    <DIR>          .
08.12.2014  09:41    <DIR>          ..
29.09.2011  20:28             6.148 .DS_Store
29.10.2011  13:01    <DIR>          backup
29.10.2011  15:58         1.640.665 pascal.aws
29.10.2011  15:59           290.268 PASCAL.ZIP
15.01.2012  10:36    <DIR>          prt
15.01.2012  10:35    <DIR>          pun
04.12.2011  20:12    <DIR>          rdr
29.10.2011  15:58         1.640.665 tape1.aws
29.09.2011  20:28        21.298.435 vm3350-1.141.cckd
29.09.2011  20:28        23.058.999 vm3350-2.241.cckd
29.09.2011  20:28        12.424.452 vm3350-3.34f.cckd
29.09.2011  20:28         7.329.729 vm3350-4.440.cckd
29.09.2011  20:28        20.006.231 vm3350-5.540.cckd
16.10.2011  09:29           137.280 vmpack6.dsk
08.12.2014  09:41                 0 x
              11 Datei(en)     87.832.872 Bytes
               6 Verzeichnis(se),  5.544.980.480 Bytes frei

because I used some flag, which I don't recall (compression? shadow?).

Looking at shadows:

 Volume in Laufwerk C: hat keine Bezeichnung.
 Volumeseriennummer: AC72-DC5A

 Verzeichnis von C:\herc370\shadows

08.12.2014  09:43    <DIR>          .
08.12.2014  09:43    <DIR>          ..
04.02.2014  18:47             1.288 mcat011
04.02.2014  18:47             1.288 sysres1
04.02.2014  18:47         2.732.747 vm3350_11
04.02.2014  18:46         6.566.199 vm3350_21
04.02.2014  18:47         5.258.151 vm3350_31
04.02.2014  18:47           100.568 vm3350_41
04.02.2014  18:47           103.802 vm3350_51
04.02.2014  18:47        14.692.159 vm3350_61
08.12.2014  09:43                 0 x
               9 Datei(en)     29.456.202 Bytes
               2 Verzeichnis(se),  5.545.635.840 Bytes frei

you see a large shadows file for disk 6

All works well :-)

unfortunately I have not much time to work with hercules and VM370 R6, so I lost
some of the details.

Kind regards

Bernd



Am 07.12.2014 23:55, schrieb G.L.:
>
>
> Hello!
> From what I recall Mike's answers are all correct. However........ You
> do win the prize for the only question and responding answer on a slow
> day today.
>
> And Dave W this is all on you, and Vanya this is your fault.
>
> -----
> G.L.
> "This signature fought the Time Wars, time and again."
>
> On Sun, Dec 7, 2014 at 5:50 PM, M.S. wrote:
> > Hi M.,
> >
> > http://comments.gmane.org/gmane.comp.emulators.hercules390.general/45534
> >
> > This is *still* not documented in the Hercules manual.
> >
> > Shadow files are only supported on compressed dasd. (Traditionally
> > given a .cckd extension for documentation purposes)
> >
> > So either create the dasd with dasdinit -z or -bz2 option or don't
> > use the <ro sf= .....>
> >
> > Personally I always use -z (and that is how the system VmR6 disks are
> > formatted).
> >
> > Also, while probably not a problem with VmR6, be aware there is a 4gig
> > limit on the *physical* (host) size of a compressed dasd.
> >
> > M.
> >
> >
> >
> >
> > On 12/7/14, M.T..wrote:
> >> Hello H390-VM Group
> >> I have being trying to add new users to the VM370 Sixpack 1.2 system with
> >> limited success. I have updated the DIRECTORY but cannot get any of the DASD
> >> I have create to be accepted by VM/370 ( or maybe Hercules). My setup is as
> >> follows;
> >>
> >>
> >> PC: Apple G5 2.3GHZ Dual 6Gig
> >>
> >>
> >> Hercules: 3.07 ( used as this is the last pre-built for Power PC
> >>
> >>
> >> So the first step is to create the 3350 DASD
> >>
> >>
> >> Create the DASD
> >> ------------------------
> >>
> >>
> >> PowerMac-G5-23:disks martin$ dasdinit vm3350-A.6f4 3350 VM50-A
> >> HHCDU044I Creating 3350 volume VM50-A: 555 cyls, 30 trks/cyl, 19456
> >> bytes/track
> >> HHCDU041I 555 cylinders successfully written to file vm3350-A.6f4
> >> HHCDI001I DASD initialization successfully completed.
> >>
> >>
> >> New DASD is added to a .conf file
> >>
> >>
> >> Hercules CONF file entry
> >> ----------------------------------
> >> # The 10th dedicated to the ROUTER userid.
> >> 06f4 3350 Disks/vm3350-A.6f4.cckd ro sf=Disks/Shadows/vm3350-A_
> >>
> >>
> >> Here is the directory entry for the new user.
> >>
> >>
> >> Directory file entry
> >> -------------------------
> >> USER ROUTER ROUTER 15M 16M G
> >> SIX0073
> >> IPL CMS
> >> SIX0074
> >> CONSOLE 009 3215
> >> SIX0075
> >> LINK MAINT 190 190 RR
> >> SIX0076
> >> LINK MAINT 19D 19D RR
> >> SIX0077
> >> LINK MAINT 19E 19E RR
> >> SIX0078
> >> * userid cuu type adr num volser mode readpw writepw multpw
> >> SIX0079
> >> MDISK 191 3350 001 115 VM50-A MR ALL WRITE MULT
> >> SIX0080
> >> SPOOL 00E 1403 A
> >> SIX0085
> >> SPOOL 00C 2540 READ *
> >> SIX0086
> >> SPOOL 00D 2540 PUNCH A
> >>
> >>
> >> VARY ONLINE issued for the new DASD. Logged on the the new userid to format
> >> the A-DISK
> >>
> >>
> >> In userid ROUTER
> >> ----------------------------
> >> q da
> >> DASD 190 3350 VM50-1 R/O 0061 CYL
> >> DASD 191 3350 VM50-A R/W 0115 CYL
> >> DASD 19D 3350 VM50-2 R/O 0070 CYL
> >> DASD 19E 3350 VM50-2 R/O 0070 CYL
> >> Ready; T=0.01/0.01 14:01:12
> >> format 191 a
> >> DMSFOR603R FORMAT WILL ERASE ALL FILES ON DISK 'A(191)'. DO YOU WISH TO
> >> CONTINUE
> >> ? (YES|NO):
> >> yes
> >> DMSFOR605R ENTER DISK LABEL:
> >> ADISK
> >> FORMATTING DISK 'A'.
> >> DMSFOR125S PERMANENT UNIT CHECK ON DISK 'A(191)'.
> >> '0' CYLINDERS FORMATTED ON 'A(191)'.
> >> Ready(00100); T=0.01/0.06 14:01:27
> >>
> >>
> >> The format fails, messages are issued to the VM operator console indicating
> >> some form of
> >> equipment check.
> >>
> >>
> >> on Operator Console
> >> -----------------------------
> >> 14:01:27 DMKDAS503I DASD 6F4 EQUIP CK CMD= 1D
> >>
> >> SNS= 100200000801001000000000000000000000000000000000
> >>
> >> CSW= 00FFE200 0E000008 USERID= ROUTER BBCCHH= 000000010000
> >>
> >>
> >>
> >> /(0009) q da
> >>
> >> 14:03:05
> >>
> >> 14:03:05 DASD 141 CP OWNED VM50-1 017
> >>
> >> 14:03:05 DASD 241 CP OWNED VM50-2 008
> >>
> >> 14:03:05 DASD 34F CP OWNED VM50-3 003
> >>
> >> 14:03:05 DASD 440 CP OWNED VM50-4 003
> >>
> >> 14:03:05 DASD 540 CP SYSTEM VM50-5 001
> >>
> >> 14:03:05 DASD 6F4 CP SYSTEM VM50-A 001
> >>
> >>
> >> So I tried to format the new volume using CP FORMAT, again no joy :-(
> >>
> >>
> >> From MAINT
> >> -----------------
> >> ipl 00c ( previously punched IPL FMT B
> >> VM/370 FORMAT/ALLOCATE PROGRAM RELEASE 6
> >> ENTER FORMAT OR ALLOCATE:
> >> DASD 147 ATTACHED
> >> f
> >> FORMAT FUNCTION SELECTED
> >> ENTER DEVICE ADDRESS (CUU):
> >> 147
> >> ENTER DEVICE TYPE:
> >> 3350
> >> ENTER START CYLINDER (XXX OR XXXX) OR "LABEL":
> >> LABEL
> >> ENTER DEVICE LABEL:
> >> VM50-A
> >> DMKFMT736E IO ERROR 147 CCHHR = 0000000003
> >> SENSE=100200000800001000000000000000000000000000000000
> >> DMKFMT735E FATAL DASD I/O ERROR CSW=00002CA00E000000
> >> ENTER FORMAT OR ALLOCATE:
> >>
> >>
> >> So looking at the Hercules guide on creating DASD I tried the IBCDASD
> >> program to format the volume.
> >> I used the file IBCDASDI.rdr-mvs downloaded from H390 files section
> >>
> >>
> >> Running IBCDASDI Telnet Session
> >> -------------------------------------------------
> >> running on PowerMac-G5-23.loca (Darwin-9.8.0.Darwin Kernel Version 9.8.0:
> >> Wed Jul 15 16:57:01 Power Macintosh MP=2)
> >> Connected to device 0:0009
> >>
> >>
> >> IBC105A DEFINE INPUT DEVICE. DASDI 7.92
> >> HHCTE006A Enter input for console device 0009
> >> input=1442 00C
> >> DASDI 7.92
> >> WORK01 JOB 'INITIALIZE 3330 WORK VOLUME'
> >> MSG TODEV=1052,TOADDR=009
> >> DADEF TODEV=3350,TOADDR=151,IPL=NO,VOLID=VM50-A,BYPASS=YES
> >> VLD NEWVOLID=VM50-A,OWNERID=HERCULES
> >> VTOCD STRTADR=1,EXTENT=1
> >> END
> >>
> >>
> >> The TELNET session seemed to hang but on the Operator console a repeated
> >> set of error message is seen.
> >> From Operator Console
> >> ---------------------------------
> >> HHCCP075I 0151:Stat=0E00 Count=0000
> >> HHCCP076I 0151:Sense=80000000 40000004 00000000 00000000 00000000 00000000
> >> HHCCP077I 0151:Sense=CMDREJ
> >> HHCCP048I 0151:CCW=0700485A 40000006=>0000022B 0000011D 00C1C1C2 C0C9C2C3
> >> .........AAB{IBC
> >> ..... repeated
> >>
> >>
> >> So Team can you help me, what have I missed out or doing wrong. For another
> >> userid I got round this problem by copying the VM50-6 pack and formatting it
> >> which work just fine, however this is a cheat !
> >>
> >>
> >> I do have two related question;
> >>
> >>
> >> 1) In DMKRIO in that what is the purpose of the SYSUSR macro ?
> >>
> >>
> >> 2) I noted that the 192 in my working userid is automatically given the
> >> mode letter D why is this or where
> >> is this automatic allocation controlled.
> >>
> >>
> >> If further info is required let me know.
> >>
> >>
> >> Regards,
> >>
> >> M.T.
> >>
> >>
> >>