RE: RE: Does Herc support DIAG 540?

Peter J. Farley wrote:

> Further progress -- Apparently VM/ESA does not like
> a full 2G main storage size.  2047M seems to work
> and it boots to the OPERATOR on the console.

GREAT!  Glad to hear you figured it out.  :)


> Next issue is that it does not know what the printers and
> tape drives are.  I have pasted messages from the Hercules
> log and the OPERATOR console below.
> 
> I tried changing the printers 00E and 00F to 3211 devices
> with no difference.  I also added LEGASYSENSEID ENABLE to
> the Hercules configuration with no change in the results
> for 00E/F and the tapes 580/1.
> 
> Again, TIA for any help you can provide.

As Ivan explained in his reply:

   "Once you are up and running you can always change
    your SYSTEM CONFIG file on maint's CF1 disk"


I don't have VM/ESA but I do have z/VM for testing purposes, and on z/VM the SYSTEM CONFIG file is on MAIN630's CF1 disk, not MAINT's.  VM/ESA may use different userids than current z/VM does, so maybe it is indeed userid MAINT that owns the SYSTEM CONFIG file, I don't know.

Regardless of which userid owns the SYSTEM CONFIG file, you need to add a "Rdevice" entry to it for each of your real printers (I myself have never found the need for defining more than one!):


/**********************************************************************/
/* Define a generic printer (device type determined via SNSID) (Fish) */
/**********************************************************************/

    Rdevice  000E        Type  Impact_Printer,
                               Classes A


You might want to review everything in the "Features," section too, to make sure all of the system options are the way you want them.  The delivered default might not be what you want.  Check the "CP Planning and Administration" manual for details (e.g. SC24-6178-09 for zVM 6.3)

And finally, unless the rules change, you might wish to also define some additional Daylight Saving Time "Timezone_Boundary" rules to the Timezone section so you don't have to worry about that for a few years:


/**********************************************************************/
/*                        Timezone Definitions                        */
/**********************************************************************/

    Timezone_Definition EDT West 04.00.00
    Timezone_Definition EST West 05.00.00
    Timezone_Definition CDT West 05.00.00
    Timezone_Definition CST West 06.00.00
    Timezone_Definition MDT West 06.00.00
    Timezone_Definition MST West 07.00.00
    Timezone_Definition PDT West 07.00.00
    Timezone_Definition PST West 08.00.00

    Timezone_Boundary on 2017-03-12 at 02:00:00 to PDT
    Timezone_Boundary on 2017-11-05 at 02:00:00 to PST

    Timezone_Boundary on 2018-03-11 at 02:00:00 to PDT
    Timezone_Boundary on 2018-11-04 at 02:00:00 to PST

    Timezone_Boundary on 2019-03-10 at 02:00:00 to PDT
    Timezone_Boundary on 2019-11-03 at 02:00:00 to PST

    Timezone_Boundary on 2020-03-08 at 02:00:00 to PDT
    Timezone_Boundary on 2020-11-01 at 02:00:00 to PST

    Timezone_Boundary on 2021-03-14 at 02:00:00 to PDT
    Timezone_Boundary on 2021-11-07 at 02:00:00 to PST

    Timezone_Boundary on 2022-03-13 at 02:00:00 to PDT
    Timezone_Boundary on 2022-11-06 at 02:00:00 to PST

    Timezone_Boundary on 2023-03-12 at 02:00:00 to PDT
    Timezone_Boundary on 2023-11-05 at 02:00:00 to PST

    Timezone_Boundary on 2024-03-10 at 02:00:00 to PDT
    Timezone_Boundary on 2024-11-03 at 02:00:00 to PST

    Timezone_Boundary on 2025-03-09 at 02:00:00 to PDT
    Timezone_Boundary on 2025-11-02 at 02:00:00 to PST

    Timezone_Boundary on 2026-03-08 at 02:00:00 to PDT
    Timezone_Boundary on 2026-11-01 at 02:00:00 to PST

    Timezone_Boundary on 2027-03-14 at 02:00:00 to PDT
    Timezone_Boundary on 2027-11-07 at 02:00:00 to PST

    Timezone_Boundary on 2028-03-12 at 02:00:00 to PDT
    Timezone_Boundary on 2028-11-05 at 02:00:00 to PST

    Timezone_Boundary on 2029-03-11 at 02:00:00 to PDT
    Timezone_Boundary on 2029-11-04 at 02:00:00 to PST

    Timezone_Boundary on 2030-03-10 at 02:00:00 to PDT
    Timezone_Boundary on 2030-11-03 at 02:00:00 to PST

    Timezone_Boundary on 2031-03-09 at 02:00:00 to PDT
    Timezone_Boundary on 2031-11-02 at 02:00:00 to PST

    Timezone_Boundary on 2032-03-14 at 02:00:00 to PDT
    Timezone_Boundary on 2032-11-07 at 02:00:00 to PST

    Timezone_Boundary on 2033-03-13 at 02:00:00 to PDT
    Timezone_Boundary on 2033-11-06 at 02:00:00 to PST

    Timezone_Boundary on 2034-03-12 at 02:00:00 to PDT
    Timezone_Boundary on 2034-11-05 at 02:00:00 to PST

    Timezone_Boundary on 2035-03-11 at 02:00:00 to PDT
    Timezone_Boundary on 2035-11-04 at 02:00:00 to PST

    Timezone_Boundary on 2036-03-09 at 02:00:00 to PDT
    Timezone_Boundary on 2036-11-02 at 02:00:00 to PST

    Timezone_Boundary on 2037-03-08 at 02:00:00 to PDT
    Timezone_Boundary on 2037-11-01 at 02:00:00 to PST

    Timezone_Boundary on 2038-03-14 at 02:00:00 to PDT
    Timezone_Boundary on 2038-11-07 at 02:00:00 to PST

    Timezone_Boundary on 2039-03-13 at 02:00:00 to PDT
    Timezone_Boundary on 2039-11-06 at 02:00:00 to PST

    Timezone_Boundary on 2040-03-11 at 02:00:00 to PDT
    Timezone_Boundary on 2040-11-04 at 02:00:00 to PST

    Timezone_Boundary on 2041-03-10 at 02:00:00 to PDT
    Timezone_Boundary on 2041-11-03 at 02:00:00 to PST



The "CP Planning and Administration" manual (e.g. SC24-6178-09 for zVM 6.3) contains all the details for all of the SYSTEM CONFIG statements.

And it goes without saying that after you change your SYSTEM CONFIG, you will of course need to completely shutdown your VM/ESA system and re-IPL it before any of your SYSTEM CONFIG changes will take effect.

Hope that helps!

-- 
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com
mail: [email protected]