Top Secret

 View Only
  • 1.  DD Parmfile specification

    Posted May 12, 2021 10:56 AM
    Hello

    in TSS Proc there is a reference to Parmfile

    e.g

    //PARMFILE DD DISP=SHR,FREE=CLOSE,DSN=&PARMS(TSSPRM&SYM1)

    i have not tested it, but i think i can use a partitioned member concatenation here

    //PARMFILE DD DISP=SHR,FREE=CLOSE,DSN=&PARMS(TSSPRMX0)
    //                 DD DISP=SHR,FREE=CLOSE,DSN=&PARMS(TSSPRM&SYM1)

    X0 Member contains general parms
    the 2nd one lpar specific settings e.g. BACKUP(...)

    But in a concatenation free=close is ignored.

    It seems there is no good solution for this?

    tss should support a DD PARMFIL2 and if present use it togehter with PARMFILE?

    or free DD:Parmfile after it was read, so jcl free=close is not neccessary (mak a yes/no option for that)

    ?

    T.




    or parmfile can be a PDS without member and a TSS PARM Option specifies the member to read.

    ?

    T.







  • 2.  RE: DD Parmfile specification

    Posted May 12, 2021 11:17 AM
    You could add a step (just prior to the EXEC PGM=TSSMNGR4 step), that copies your main parmlib member + any system-specific concatenation into a temporary sequential dataset (or a named dataset if you wish to maintain protection).   Then, reference this copy of the parm data in your PARMFILE DD statement.  This would ensure you pick up the latest parm data, and would minimize the duration that your parmlib remains allocated to the TSS started task. 

    I have not tried this, but it seems that doing this would be a simple way to accommodate the ability to concatenate multiple parmlib sources, and would result in immediately releasing/de-allocating the parmlib library for the remainder of the TSS started task duration.

    ------------------------------
    Joe Denison
    joe@tssadmin.com
    CA Top Secret z/OS Productivity Specialist
    Access Solutions, Inc.
    Kansas City, Missouri / USA
    ------------------------------



  • 3.  RE: DD Parmfile specification

    Posted May 12, 2021 11:53 AM
    Thanks you Joe!. I have already thought about such a solution. but then tss startup has dependency to other utils.

    I have made (minor) mistakes in the past keeping the two files insync. 

    I am also thinking about why tss does not support parmlib search. This must work very early in ipl sequence. But for whatever reason this option was not iplemented. 
    if the parmlib is dead jes, omvs etc will not start either....