z/OS V1R11 ADCD

[warezit2000]

Not my upload, but https://archive.org/details/rdz-unit-te ... op-install appears to include a complete ADCD of z/OS V1R11. I was able to IPL the system under Hercules with the following config:

Code: Select all

CPUMODEL  3090
CPUSERIAL 012345
MAINSIZE  1500
CNSLPORT  3270
NUMCPU    4
LOADPARM 0A82CS
ARCHLVL zArch
OSTAILOR z/OS 
PGMPRDOS LICENSED
CNSLPORT  3270

#####################
# Display Terminals #
#####################
0700    3270
0701    3270
0702    3270
0703    3270
0704    3270
0705    3270

################
# DASD Devices #
################

0a80 3390 sbres1.cckd sf=shadow/sbres1_*.shadow
0a81 3390 sbres2.cckd sf=shadow/sbres2_*.shadow
0a82 3390 sbsys1.cckd sf=shadow/sbsys1_*.shadow
0a83 3390 sbuss1.cckd sf=shadow/sbuss1_*.shadow
0a84 3390 sbbbn1.cckd sf=shadow/sbbbn1_*.shadow
0a85 3390 sbbbn2.cckd sf=shadow/sbbbn2_*.shadow
0a86 3390 sbprd1.cckd sf=shadow/sbprd1_*.shadow
0a87 3390 sbprd2.cckd sf=shadow/sbprd2_*.shadow
0a88 3390 sbprd3.cckd sf=shadow/sbprd3_*.shadow
0a89 3390 sbdis1.cckd sf=shadow/sbdis1_*.shadow
0a8a 3390 sbdis2.cckd sf=shadow/sbdis2_*.shadow
0a8b 3390 sbdis3.cckd sf=shadow/sbdis3_*.shadow
0a8c 3390 sbdis4.cckd sf=shadow/sbdis4_*.shadow
0a8d 3390 sbdis5.cckd sf=shadow/sbdis5_*.shadow
0a8e 3390 sbdis6.cckd sf=shadow/sbdis6_*.shadow
0a8f 3390 sares1.cckd sf=shadow/sares1_*.shadow
0a90 3390 sbwas1.cckd sf=shadow/sbwas1_*.shadow
0a91 3390 sbwas2.cckd sf=shadow/sbwas2_*.shadow
0a92 3390 sbwas3.cckd sf=shadow/sbwas3_*.shadow
0a93 3390 sbdb91.cckd sf=shadow/sbdb91_*.shadow
0a94 3390 sbdb92.cckd sf=shadow/sbdb92_*.shadow
0a95 3390 sbdb93.cckd sf=shadow/sbdb93_*.shadow
0a96 3390 sbcic1.cckd sf=shadow/sbcic1_*.shadow
0a97 3390 sbims1.cckd sf=shadow/sbims1_*.shadow
0a98 3390 sbims2.cckd sf=shadow/sbims2_*.shadow
0a99 3390 sbims3.cckd sf=shadow/sbims3_*.shadow

The cckd are generated from the gzipped volumes on the ISOs with dasdcopy. After starting Hercules, enter sf+* in the console to initialize the shadow files, then ipl 0a80 to IPL. When prompted to initialize sysplex, enter .R 00,I and then .VARY CN(*),ACTIVATE to start the system. At this point you should be able to login on VTAM on a 3270 as ibmuser/ibmuser. I haven't tried networking yet but all the necessary components seem to be there and enabled by default. There's also volumes for DB2 and WAS included, which should be fun to play with.

[vbdasc]

Can you check what software it does contain, or at least compilers for what languages?

[the_doctor2]

Can you check what software it does contain, or at least compilers for what languages?

Almost everything but the kitchen sink. Take a look at http://guangxingliu.com/?id=39 for a comparable list of products.
Btw. it also contains zpdt as well. It is surprisingly easy to convince it to work for free

[cfant]

Btw. it also contains zpdt as well. It is surprisingly easy to convince it to work for free

I was able to install zPDT, but how did you convince it to work? It needs usb key.

[qsecofr]

It is my upload actually, and you don't need to use Hercules - it includes a copy of the emulator IBM ships, which is _a lot_ faster than Hercules (roughly a factor 10). It does need a software protection dongle or de-dongling though.

Not my upload, but https://archive.org/details/rdz-unit-te ... op-install appears to include a complete ADCD of z/OS V1R11. I was able to IPL the system under Hercules with the following config:

Code: Select all

CPUMODEL  3090
CPUSERIAL 012345
MAINSIZE  1500
CNSLPORT  3270
NUMCPU    4
LOADPARM 0A82CS
ARCHLVL zArch
OSTAILOR z/OS 
PGMPRDOS LICENSED
CNSLPORT  3270

#####################
# Display Terminals #
#####################
0700    3270
0701    3270
0702    3270
0703    3270
0704    3270
0705    3270

################
# DASD Devices #
################

0a80 3390 sbres1.cckd sf=shadow/sbres1_*.shadow
0a81 3390 sbres2.cckd sf=shadow/sbres2_*.shadow
0a82 3390 sbsys1.cckd sf=shadow/sbsys1_*.shadow
0a83 3390 sbuss1.cckd sf=shadow/sbuss1_*.shadow
0a84 3390 sbbbn1.cckd sf=shadow/sbbbn1_*.shadow
0a85 3390 sbbbn2.cckd sf=shadow/sbbbn2_*.shadow
0a86 3390 sbprd1.cckd sf=shadow/sbprd1_*.shadow
0a87 3390 sbprd2.cckd sf=shadow/sbprd2_*.shadow
0a88 3390 sbprd3.cckd sf=shadow/sbprd3_*.shadow
0a89 3390 sbdis1.cckd sf=shadow/sbdis1_*.shadow
0a8a 3390 sbdis2.cckd sf=shadow/sbdis2_*.shadow
0a8b 3390 sbdis3.cckd sf=shadow/sbdis3_*.shadow
0a8c 3390 sbdis4.cckd sf=shadow/sbdis4_*.shadow
0a8d 3390 sbdis5.cckd sf=shadow/sbdis5_*.shadow
0a8e 3390 sbdis6.cckd sf=shadow/sbdis6_*.shadow
0a8f 3390 sares1.cckd sf=shadow/sares1_*.shadow
0a90 3390 sbwas1.cckd sf=shadow/sbwas1_*.shadow
0a91 3390 sbwas2.cckd sf=shadow/sbwas2_*.shadow
0a92 3390 sbwas3.cckd sf=shadow/sbwas3_*.shadow
0a93 3390 sbdb91.cckd sf=shadow/sbdb91_*.shadow
0a94 3390 sbdb92.cckd sf=shadow/sbdb92_*.shadow
0a95 3390 sbdb93.cckd sf=shadow/sbdb93_*.shadow
0a96 3390 sbcic1.cckd sf=shadow/sbcic1_*.shadow
0a97 3390 sbims1.cckd sf=shadow/sbims1_*.shadow
0a98 3390 sbims2.cckd sf=shadow/sbims2_*.shadow
0a99 3390 sbims3.cckd sf=shadow/sbims3_*.shadow

The cckd are generated from the gzipped volumes on the ISOs with dasdcopy. After starting Hercules, enter sf+* in the console to initialize the shadow files, then ipl 0a80 to IPL. When prompted to initialize sysplex, enter .R 00,I and then .VARY CN(*),ACTIVATE to start the system. At this point you should be able to login on VTAM on a 3270 as ibmuser/ibmuser. I haven't tried networking yet but all the necessary components seem to be there and enabled by default. There's also volumes for DB2 and WAS included, which should be fun to play with.

[qsecofr]

Convincing it to work for free is trivial, but you still need the decryption key inside the USB dongle to run (iirc) V1R15 onwards because the IPL volume is encrypted. It does get decrypted on first run though, but it's watermarked with your dongle ID, which is mapped to your payment details.

This is also why there aren't any V2Rx public leaks, with V2R4 being (privately) available and V2R5 incoming.

Can you check what software it does contain, or at least compilers for what languages?

Almost everything but the kitchen sink. Take a look at http://guangxingliu.com/?id=39 for a comparable list of products.
Btw. it also contains zpdt as well. It is surprisingly easy to convince it to work for free

[IBlowMyMind]

Convincing it to work for free is trivial, but you still need the decryption key inside the USB dongle to run (iirc) V1R15 onwards because the IPL volume is encrypted. It does get decrypted on first run though, but it's watermarked with your dongle ID, which is mapped to your payment details.

This is also why there aren't any V2Rx public leaks, with V2R4 being (privately) available and V2R5 incoming.

Hello,

Excuse me for barging into the conversation, lol- I'd like to ask a question about "convincing it to work for free":
How exactly does one do this? I have ideas in mind, but I haven't seen anything related to this subject until now.

This release seems to include quite a bit of stuff, though, even stuff like OVMS (UNIX compatibility layer), Java 6 (IBM's own JVM implementation of it), Web services for remote management (READ: edit 1) are included.

The default user IBMUSER and password SYS1 are used, but you should really change those on a production system!
Other than that, z/OS is a fascinating operating system, and I'm glad we can get proper access! IBM's "Master the Mainframe" provides you with almost nothing in terms of system configurability.

Oddly enough, though, CTCI-WIN doesn't like Npcap (even in WinPcap compatibility mode) nor Win10Pcap (not being able to open a TUNTAP device with either). Only WinPcap, which isn't maintained and doesn't officially support Win10, and is filled with security holes. I might try to get in touch with the developer to report this.

EDIT: Seems like the z/OS Management Facility (the remote management web services I talked about) isn't actually installed? The folder for it exists under /usr/lpp/zosmf in OVMS, so I assumed that it'd come with that installed, but nope! Folder's empty. Wonder if we could get some LPs & additional products unearthed..

[Dartagnan]

Hi,
I too am curious about how trivial it is to convince it to work for charity!

[IBlowMyMind]

Another edit:

z/OSMF is actually shipped with the DVDs and can be installed, but I haven't been able to figure out how.
Documentation states that it must be Receive-Apply-Accepted with SMP/E before files appear in /usr/lpp/zosmf, and there are sample jobs in IZU.SIZUJCL, however I haven't been able to get it working.

Can anyone help me out?

[Dartagnan]

z/OSMF is already SMP/E installed, so you need to perform the steps to configure WASOEM and z/OSMF. It looks like the WASOEM and z/OSMF were configured, but not all the necessary zfs files were delivered hence the need to reconfigure. I've managed to get it running, not without a lot of trial and error along the way.

Things to do to help the installation:-
1. Allocate another USS dasd volume e.g. sbuss2 and move some hfs/zfs files from sbuss1 onto it. I moved the USERS and TMP along with the VARWBEM. sbuss1 has no room for growth and the setup scripts kept crashing.
2. Update the bpxprm member to include mountpoints for the BNN and IZU files, examples of which can be found in BPXPRMMF. Make sure MAXFILEPROC is set to 2000.
3. Pre Allocate BBN.V7R0.CONFIG1.PROCLIB
4. Update the certificate expiry date in usr/lpp/zWebSphereOEM/V7R0/zOS-config/zpmt/samples/wasOEMDefault.responseFile to a year in the future e.g. 2030.

IPL the system and confirm these changes are applied, then start with the config process. I definitely recommend you download the following guides to get you going:-
GA32-0631-01 IBM WebSphere Application Server OEM Edition for z/OS V7.0 Configuration Guide
SA38-0652-02 IBM z/OS Management Facility V1R11.0 (z/OSMF V1R11.0) User's Guide

You should start with WAS viz. "WASOEM.sh -create /etc/zWebSphereOEM/V7R0/conf/CONFIG1"
then the z/OSMF izusetup scripts starting with "izusetup.sh -file /ADCD/etc/zosmf/izudflt.cfg -config"

All of the RACF setup appears to be in place, so you really only need to recreate the expired certificates and update the keyrings.

The setup shell scripts take a long time and use plenty cpu (using Hercules), so be prepared for long wait times. It's a pity the_doctor2 and/or qsecofr did not offer guidance with getting z/pdt to work. It would have been nice to confirm qsecofr's claim that it is 10 times faster than Hercules.

[cfant]

Do you need a web browser with java applet enabled?

[Dartagnan]

Yes, you do. Not too many browsers that support this any more. I used Internet Explorer in a Windows 7 virtual machine.

[cfant]

Thx. That is what I am planing to do.

[IBlowMyMind]

z/OSMF is already SMP/E installed, so you need to perform the steps to configure WASOEM and z/OSMF. It looks like the WASOEM and z/OSMF were configured, but not all the necessary zfs files were delivered hence the need to reconfigure. I've managed to get it running, not without a lot of trial and error along the way.

Things to do to help the installation:-
1. Allocate another USS dasd volume e.g. sbuss2 and move some hfs/zfs files from sbuss1 onto it. I moved the USERS and TMP along with the VARWBEM. sbuss1 has no room for growth and the setup scripts kept crashing.
2. Update the bpxprm member to include mountpoints for the BNN and IZU files, examples of which can be found in BPXPRMMF. Make sure MAXFILEPROC is set to 2000.
3. Pre Allocate BBN.V7R0.CONFIG1.PROCLIB
4. Update the certificate expiry date in usr/lpp/zWebSphereOEM/V7R0/zOS-config/zpmt/samples/wasOEMDefault.responseFile to a year in the future e.g. 2030.

IPL the system and confirm these changes are applied, then start with the config process. I definitely recommend you download the following guides to get you going:-
GA32-0631-01 IBM WebSphere Application Server OEM Edition for z/OS V7.0 Configuration Guide
SA38-0652-02 IBM z/OS Management Facility V1R11.0 (z/OSMF V1R11.0) User's Guide

You should start with WAS viz. "WASOEM.sh -create /etc/zWebSphereOEM/V7R0/conf/CONFIG1"
then the z/OSMF izusetup scripts starting with "izusetup.sh -file /ADCD/etc/zosmf/izudflt.cfg -config"

All of the RACF setup appears to be in place, so you really only need to recreate the expired certificates and update the keyrings.

The setup shell scripts take a long time and use plenty cpu (using Hercules), so be prepared for long wait times. It's a pity the_doctor2 and/or qsecofr did not offer guidance with getting z/pdt to work. It would have been nice to confirm qsecofr's claim that it is 10 times faster than Hercules.

Hello,

I couldn't seem to quite get it to work. I edited ADCD.Z111S.PARMLIB(BPXPRM00) and inserted the changed lines in ADCD.Z111S.PARMLIB(BPXPRMMF) into it, saved and re-IPL'ed, but the filesystems won't show up.
IZU.SIZUFS seems to be in *VSAM* and viewing it returns "VSAM processing unavail." in Dslist. Is this because I might've partially done the steps wrong before and quit halfway?

Could you post instructions with more detail?
Thanks!

[Dartagnan]

You need to edit the BPXPRMxx member that your configuration is using. For this ADCD system, if your LoadParm is 0A82CS.. then edit member BPXPRMCS. If it's 0A82DB.. then edit BPXPRMDB, and so on......

[IBlowMyMind]

Ahh, that makes much more sense. Will try when I can.

[IBlowMyMind]

BXPPRMDC seems to be missing. (I use 0A82DC to IPL)

[IBlowMyMind]

However, ADCD.Z111S.PARMLIB(IEASYSDC) indicates OMVS=DB, so BXPPRMDB is used. Will edit that!

[IBlowMyMind]

Did not mount. What else could I be missing?

[Dartagnan]

If you updated BPXPRMDB correctly, then BBN.SBBN7ZFS and IZU.SIZUZFS should have mounted successfully. What messages are you seeing in the syslog for these mountpoints?
The other 2 filesystems are only created in the setup scripts, so you need not worry about them at this point.
These are the lines you should have added to BPXPRMDB:-

MOUNT FILESYSTEM('BBN.SBBN7ZFS')
MOUNTPOINT('/usr/lpp/zWebSphereOEM/V7R0')
TYPE(ZFS) MODE(RDWR)

MOUNT FILESYSTEM('BBN.V7R0.CONFIG1.ZFS')
MOUNTPOINT('/zWebSphereOEM/V7R0/config1')
TYPE(ZFS) MODE(RDWR) PARM('AGGRGROW')

MOUNT FILESYSTEM('IZU.SIZUZFS')
MOUNTPOINT('/usr/lpp/zosmf/V1R11/')
TYPE(ZFS) MODE(READ)

MOUNT FILESYSTEM('IZU.SIZUDATA')
MOUNTPOINT('/var/zosmf/data')
TYPE(ZFS) MODE(RDWR) UNMOUNT

[IBlowMyMind]

I think I should just restore the system and start over again, I’m pretty sure I broke something..
I think I somehow unallocated IZU.SIZUZFS by mistake as it doesn’t show up in any volume physically, appearing under *VSAM* if i do a Dslist to locate it.
Besides, I think I’m doing some things wrong too (couldnt get SDSF to pick up printers 000E-F in IODF and all my jobs get stuck at awaiting hardcopy) so I might as well just start from scratch. I didn’t do much, anyway.
I was waiting for instructions on how to “get zPDT to work” to do this, but I’m not really sure how to do that lol
Will report after I reset & try again. Thanks!

[Hunterkll]

Looking for information on convincing zPDT to work as well. Haven't been able to find anything online myself.