Idea Details

Resolve "TSS LIST until" defect more logical

Last activity 06-03-2019 08:26 PM
aw-bmw's profile image
08-24-2016 03:33 AM

We discovered that TSS LIST is not work properly in some cases. So we raised a ticket to CA. Unfortunately the fix we got solves the problem a way that is not really beautiful. We're convinced the following solution would be more useful for all.

 

First let's understand the issue: Usually a list of resources having expiration date look like

 

XA DATASET = RZZ.TSO.MESSAGES              UNTIL(22.09.16) OWNER(C#RZ    )

   ACCESS  = READ

 

When the resource gets longer the "until" jumps to the next line.

 

XA DATASET = RZZ.TSO.MESSAGES.BAC.TEST1.TEST2.TEST3        OWNER(C#RZ    )

   ACCESS  = READ                          UNTIL(22.09.16)

 

This works until access and privpgm getting too long; then until disappears completely. CA now fixed this issue in the following way:

 

XA DATASET = RZZ.TSO.MESSAGES.BAC.TEST1.TEST2.TEST3        OWNER(C#RZ    )

           = N/A                           UNTIL(22.09.16)

   ACCESS  = FETCH,UPDATE,CREATE,CONTROL,INQUIRE

   PRIVPGM = PROGRM      GUCKGUCK    HIHI        MUHKUH      BLUBB

 

So a new line with _no_ qualifier and confusing "N/A" (which according to CA exists for many version) has been introduced. Our suggestion is now to introduce a new qualifier "until" ...

 

XA DATASET = RZZ.TSO.MESSAGES.BAC.TEST1.TEST2.TEST3        OWNER(C#RZ    )
   UNTIL   =                               UNTIL(22.09.16)
   ACCESS  = FETCH,UPDATE,CREATE,CONTROL,INQUIRE
   PRIVPGM = PROGRM      GUCKGUCK    HIHI        MUHKUH      BLUBB

 

... which makes it clear and parseable by qualifier; and it should be independantly of the resource length:

 

XA DATASET = RZZ.TSO.MESSAGES                              OWNER(C#RZ    )
   UNTIL   =                               UNTIL(22.09.16)
   ACCESS  = READ

 

By keeping until(...)  at position 44 it will be compatible for all existing processes parsing that position.


Comments

08-29-2016 10:07 AM