OPSLOG Archive Needs Secondary Space Amount

Idea created by mike.blocker on Aug 31, 2018
    Delivered
    Score7
    • patrick.reynaga
    • ColleenK
    • harless2
    • rhondal.lloyd
    • mike.blocker
    • teresa.mcclintic
    • MarcelvanEk

    When using the new and improved OPS/MVS OPSLOG archive process (>= v12.2), there is no longer a way to specify a secondary space amount for the archive dataset.  The primary allocation is calculated to what it needs and the secondary amount is set to 0.  This prevents the use of modern SMS "Space Constraint Relief" data class attributes.  We run our SMS storage groups very tight and need to use these features.  Expecting the entire primary allocation to always be available is unrealistic.