Thank you Moshix! I just went through all of the steps: including the errors! Bwah ha ha ha! A great learning experience ... I wasn't a systems programmer, but it's amazing how many steps (and all of the numerous systems commands you have to remember) are needed to accomplish these types of tasks! Be Well & Stay Safe! ;))
Thanks for another good video. Moshix, to make the font bigger go to profile preference ( video at 11:56 ) and click the custom font and choose a bigger font.
Thanks Moshix! 😃 I tried it on both Mvs and z/os. Worked great! On z/os I made an 3390 instead, and I had to mount it with "m /0A9B,vol=(sl,darpa),use=private" (a slash before the device. I think it has to do with
Hi Moshix, Thanks this it great. 1) To fix the shutdown segment error, once you have enabled multiple cpu's, edit scripts/shutdown , change "NUMCPU:=1" to "NUMCPU:=2". Problem solved. 2) By the way, you can compress your new disk device. It works just fine with "dasdinit -a -bz2 moshix.242 3350 MOSHIX".
I ran into the same trap: compressed volumes don't work in TK4-, but in my opinion it is not necessary anyway. In windows you can change the Hercules/dasd directory attribute to compressed. This has reduced the size of the entire directory from 850 MB to 250 MB. Hercules/MVS has no problems with it and runs fine. I suppose Linux has a similar feature.
It was failing because you have omitted the -a option when creating the first image. The first image was 555 cyls in size, and the second one was 560 cyls. The error message said that there was an I/O error on track CCHH=X'022B 0000', and 0x22B = 555. It tried to access the alternative tracks which were not there without -a option.
But it's not mentioned in the video. At 32:40 you're saing that "it was a compression that was trowing it off" and then suggest that dasdinit from your Hercules was slighthly newer than Hercules shipped inside TK4-. Likewise the guy in the comments below is blaming compression. However, the root cause is different - absense of '-a' option to dasdinit, and it is not mentioned anywhere. I think it is interesting to discover the root cause, even a year later :)
Is there a way to use the shared device server under MVS? This uses bare Hercules to drive devices. The device server is a hercules instance configured to run by itself. Other Hercules instances actually run an IPLed OS
With MVS3.8-TK4 updated 8 and command "/d u,dasd,online", I see the following lines 11.19.05 IEE450I 11.19.05 UNIT STATUS 489 UNIT TYPE STATUS VOLSER VOLSTATE UNIT TYPE STATUS VOLSER VOLSTATE 131 2314 O SORT01 PUB/RSDNT 132 2314 O SORT02 PUB/RSDNT 133 2314 O SORT03 PUB/RSDNT 134 2314 O SORT04 PUB/RSDNT 135 2314 O SORT05 PUB/RSDNT 136 2314 O SORT06 PUB/RSDNT 140 3350 O WORK00 PUB/RSDNT 148 3350 S MVSRES PRIV/RSDNT 149 3350 O SMP001 PRIV/RSDNT 14A 3350 O SMP002 PRIV/RSDNT 14B 3350 O SMP003 PRIV/RSDNT 14C 3350 O SMP004 PRIV/RSDNT 152 3330 A HASP00 PRIV/RSERV 160 3340 A PAGE00 PRIV/RSDNT 161 3340 A PAGE01 PRIV/RSDNT 170 3375 O WORK01 PUB/RSERV 180 3380 O WORK02 PUB/RSERV 190 3390 O WORK03 PUB/RSERV 191 3390 A MVSCAT STRG/RSERV 240 3350 A PUB000 STRG/RSDNT 241 3350 A PUB010 STRG/RSDNT 242 3350 O MOSHIX PUB/RSDNT 243 3350 O MSHX00 PRIV/RSDNT 244 3350 O MSHX01 PRIV/RSDNT 248 3350 A MVSDLB PRIV/RSDNT 270 3375 A PUB001 STRG/RSERV 271 3375 O PUB011 STRG/RSERV 280 3380 O PUB002 STRG/RSERV 281 3380 O PUB012 STRG/RSERV 290 3390 A PUB003 STRG/RSERV 291 3390 O PUB013 STRG/RSERV herc =====>
Thank you Moshix! I just went through all of the steps: including the errors! Bwah ha ha ha! A great learning experience ... I wasn't a systems programmer, but it's amazing how many steps (and all of the numerous systems commands you have to remember) are needed to accomplish these types of tasks! Be Well & Stay Safe! ;))
Thank you for watching !
Thanks for another good video.
Moshix, to make the font bigger go to profile preference ( video at 11:56 ) and click the custom font and choose a bigger font.
Thanks Moshix! 😃 I tried it on both Mvs and z/os. Worked great! On z/os I made an 3390 instead, and I had to mount it with "m /0A9B,vol=(sl,darpa),use=private" (a slash before the device. I think it has to do with
I think it has to do with if you use more than 3 characters?
correct, yes.
Thanks Moshix! I can finally add more disks to my MVS lab :-) Great video!
Hi Moshix, Thanks this it great. 1) To fix the shutdown segment error, once you have enabled multiple cpu's, edit scripts/shutdown , change "NUMCPU:=1" to "NUMCPU:=2". Problem solved. 2) By the way, you can compress your new disk device. It works just fine with "dasdinit -a -bz2 moshix.242 3350 MOSHIX".
thanks for an excellent video! Mind me asking what's the name of the track which is playing in the beginning?
Thanks. Satellite One
I ran into the same trap: compressed volumes don't work in TK4-, but in my opinion it is not necessary anyway. In windows you can change the Hercules/dasd directory attribute to compressed. This has reduced the size of the entire directory from 850 MB to 250 MB. Hercules/MVS has no problems with it and runs fine. I suppose Linux has a similar feature.
It was failing because you have omitted the -a option when creating the first image.
The first image was 555 cyls in size, and the second one was 560 cyls.
The error message said that there was an I/O error on track CCHH=X'022B 0000', and 0x22B = 555. It tried to access the alternative tracks which were not there without -a option.
Yes, I realize. I think I did mention it in the video
But it's not mentioned in the video. At 32:40 you're saing that "it was a compression that was trowing it off" and then suggest that dasdinit from your Hercules was slighthly newer than Hercules shipped inside TK4-.
Likewise the guy in the comments below is blaming compression. However, the root cause is different - absense of '-a' option to dasdinit, and it is not mentioned anywhere.
I think it is interesting to discover the root cause, even a year later :)
Yes but I did the -a switch in the gideon
Yes but I did the -a switch in the video
I mean there was no -a swtich first time you created the image at 11:00
all videos all amazing thanks so much
Is there a way to use the shared device server under MVS? This uses bare Hercules to drive devices. The device server is a hercules instance configured to run by itself. Other Hercules instances actually run an IPLed OS
Yes see Hercules manualnfor shared dasd configuration. Real easy to set up. You can see that working in my JES3 video in this channel
What's the best way to shut down MVS?
For fast and soothing relief: pull the power cord. Otherwise watch my videos
How to work with tape drives and tapes ?
Watch the other videos
@@moshixmainframechannel OK, I found it "Get data in and out of the IBM mainframe- Enhanced - M5". Thank You !
With MVS3.8-TK4 updated 8 and command "/d u,dasd,online", I see the following lines
11.19.05 IEE450I 11.19.05 UNIT STATUS 489
UNIT TYPE STATUS VOLSER VOLSTATE UNIT TYPE STATUS VOLSER VOLSTATE
131 2314 O SORT01 PUB/RSDNT 132 2314 O SORT02 PUB/RSDNT
133 2314 O SORT03 PUB/RSDNT 134 2314 O SORT04 PUB/RSDNT
135 2314 O SORT05 PUB/RSDNT 136 2314 O SORT06 PUB/RSDNT
140 3350 O WORK00 PUB/RSDNT 148 3350 S MVSRES PRIV/RSDNT
149 3350 O SMP001 PRIV/RSDNT 14A 3350 O SMP002 PRIV/RSDNT
14B 3350 O SMP003 PRIV/RSDNT 14C 3350 O SMP004 PRIV/RSDNT
152 3330 A HASP00 PRIV/RSERV 160 3340 A PAGE00 PRIV/RSDNT
161 3340 A PAGE01 PRIV/RSDNT 170 3375 O WORK01 PUB/RSERV
180 3380 O WORK02 PUB/RSERV 190 3390 O WORK03 PUB/RSERV
191 3390 A MVSCAT STRG/RSERV 240 3350 A PUB000 STRG/RSDNT
241 3350 A PUB010 STRG/RSDNT 242 3350 O MOSHIX PUB/RSDNT
243 3350 O MSHX00 PRIV/RSDNT 244 3350 O MSHX01 PRIV/RSDNT
248 3350 A MVSDLB PRIV/RSDNT 270 3375 A PUB001 STRG/RSERV
271 3375 O PUB011 STRG/RSERV 280 3380 O PUB002 STRG/RSERV
281 3380 O PUB012 STRG/RSERV 290 3390 A PUB003 STRG/RSERV
291 3390 O PUB013 STRG/RSERV
herc =====>
Great