Lizette > But thanks for checking further.
How about your local specialist in TPX? > I have reviewed my JCL for TPX and it has an allocation for the SYS1.VTAMLST > in it. Which, of course is quite a good suggestion for Juan for the purposes of seeing which of the products he runs is interested in the VTAMLST partitioned data sets. >...> I can say that ... a few other things might need READ access. It is also a good suggestion for you for the purposes of fleshing out this comment and turning it from FUD to something useful. - Well, it was Sunday and so your TPX specialist may have been enjoying a day of rest. On the other hand I who obviously have nothing better to do decided to engage in some research regarding TPX. First I found the web site: http://www.ca.com/ and then a. I tried to access the TPX product documentation b. I tried to register in order to be able to access the documentation c. I discovered they remembered I had already registered some time in the past even if I had forgotten d. I found the little text file where I recorded my password - which would not be accepted today since it violates at least three of the rules now imposed! e. I logged on and downloaded all 12 pdf files f. I searched each for appearances of the token "VTAMLST" >...> I can say that ..., TPX, ... might need READ access. I can now modify your original assertion as follows: "I can say that ..., TPX, ... definitely requires READ access and at least one of the supplied utility programs requires UPDATE access." Essentially this is because, like the NetView component STATMON, TPX does indeed require to know the name of a VBUILD TYPE=APPL major node member in one of the VTAMLST partitioned data sets. There is a default name in the documentation, TPXAPPL, but this can be changed. Being a name in the VTAM name spaces defined by the names which can appear in VARY ACT and VARY INACT commands, it had jolly well better be changeable or customers would be entitled to hire a ton of bricks to drop on any developer who imposed a fixed value for such a name! In a rather hasty scan - after all I had spent enough time just getting access to the documentation! - of the places in the documentation where there was a reference to "VTAMLST", I discovered that, also just like STATMON, TPX likes to adorn the APPL statements with its own comments which provide TPX with information during execution. Which leads me to the TPX utility which requires UPDATE access. It seems TPX cannot abide VTAM APPL model statements. VTAM APPL model statements give TPX a *real* headache. There is a TPX utility which "corrects" VTAM APPL model statements so that they are no longer VTAM APPL model statements. If I had been predisposed to humour by the time I had waded through the documentation in order to work this out, I may have done myself an injury! Chris Mason On Sun, 11 Mar 2012 12:23:48 -0400, Lizette Koehler <[email protected]> wrote: >Chris, > >I have reviewed my JCL for TPX and it has an allocation for the SYS1.VTAMLST >in it. How or why it is in the STC JCL, I am unclear. > >But thanks for checking further. > >Lizette ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
