¿ªÔÆÌåÓý

OSA/SF up and running, was Re: [h390-vm] VM/ESA ADCD package setup?


 

On 2/28/23 09:56, Martin Taylor via groups.io wrote:
I believe that to enable a product it needs to be added to the SYSTEM CONFIG file on the CF1 disk. Look at the entries for those currently ¡°installed¡±.
which can be displayed by a Q PRODUCT. The format is product id with the possible addition of a suffix letter. The DIRECT P390 on MAINT has a list of products
available. Note I used the last letter of the userid as the suffix letter. ?Do you have instructions on how to do the SYSTEM CONFIG update ?
Yes, I extrapolated from the installation procedure for dirmaint to get that far.

And, as luck would have it, I was able to get it all done today. It turns out that the release of OSA/SF for VM/ESA is the same as that for z/VM v4, and the same installation documentation applies, and I was able to find that.

As was the case with dirmaint, the ADCD distribution's OSA/SF has had some of the installation steps performed already. Specifically, the copying in of the example files had already been done.

But first it's necessary to enable the product:

LINK MAINT 51D 51D M
ACCESS 51D D
VMFINS ENABLE PPF 2VMVMV20 OSA

This creates 2VMVMV20 PRODSYS A. Place the contents of this file (one line) in the appropriate place in the SYSTEM CONFIG file on CF1 using the normal process for accessing CP-owned minidisks.

Then, log on as 2VMVMV20 and pick up from section 6.6 in the Program Directory for OSA/SF for zVM V4 manual, to perform these steps:

access 100 e
access 200 f
vmfcopy * * e = = f (prodid 2VMVMV20%OSA olddate replace

access 300 e
access 400 f
vmfcopy * * e = = f (prodid 2VMVMV20%OSA olddate replace

access 7f00 e
access 8f00 f
vmfcopy * * e = = f (prodid 2VMVMV20%OSA olddate replace

access 2c2 e
access 200 f
vmfcopy * sampprof e = = f (prodid 2VMVMV20%OSA olddate replace

Then log off from 2VMVMV20. It should now be possible to log on as OSADMIN1, and execute IOACMD commands.

For safety's sake, I first tested all of this under Hercules, before going over to LSSM and doing it on the S/390. There, I was able to use IOACMD GET_OAT to successfully pull out the OAT data from a functional OSA-2 board this this evening. Later this week I will attempt to reinitialize and configure the second OSA-2 board.

Thanks to everyone here who pointed me in the right direction!

-Dave

--
Dave McGuire, AK4HZ
New Kensington, PA