Properties of a LOADLIB member - TTR, AC, AM, RM, Attribute

shanbalasay · Posted: Tue May 12, 2009 3:20 pm

Using the 3.4 Utility, when we view the members of a LOADLIB PDS, below are the properties that are displayed for each member. They have the values as shown below them.

Robert Sample · Posted: Tue May 12, 2009 4:53 pm

TTR - relative track address
AC - authorization code
AM - addressing mode
RM - residence mode
RN RU - rent reus (but don't quote me on that)
SSI - system status index

dick scherrer · Posted: Tue May 12, 2009 8:59 pm

Hello,

When you see a loadlib member list, press F1 (maybe a couple of times) and the following (and more) will be displayed on the terminal:

shanbalasay · Posted: Tue May 12, 2009 9:25 pm

Thanks very much to Robert and Dick.

The reason why I had asked this question is that one of the users had complained that the values for AC & Atrributes had changed from 00 to 01 and None to RU respectively for the Assembler LOADLIB members.

I later found that it has got to do with the default settings in the Assembler Compiler/Link Editor. We had been passing AC=1, REUS as default options to the Assembler Link Editor.

It worked fine after I removed these default options

Thanks to you guys. You were always helpful.

Robert Sample · Posted: Tue May 12, 2009 9:28 pm

The AC=1 to AC=0 probably had a lot to do with the successful change. AC=1 is used only for authorized programs, which generally require special authorization to create, and must be written following certain standards or problems can ensue. Why would a default be set to AC=1 anyway?

jothibso · New User Joined: 03 Sep 2009 Posts: 18 Location: chennai

I have a loadlib B which is Alias-of loadlib A.

Does this mean loadlib B has the same load as loadlib A. Both the loadsizes match.

Can anyone explain the benefit of Alias-of

Robert Sample · Posted: Thu Oct 07, 2010 8:29 pm

Aliases are described in the MVS Program Management manual in the MVS bookshelf. An alias establishes a different name for a load module. This can be useful when the program may be called by different names. One example would be a common routine for handling dates that was called by the name DATEPROC in one system and DATEPR in another system. Rather than changing the code in one system to match the other name, you could establish an alias so both names can be used. Some vendor programs can be called by different names and use aliases to reference the common code.

Akatsukami · Posted: Thu Oct 07, 2010 10:28 pm

A seriously non-standard use of alias: my shop considers bytes 6-8 of the load module's name to be the version number. To avoid having to find and change all of the JCL using a particular load module whenever a new version is promoted to production, a five-character alias is created for the current version; thus, whether current production is PQRSTA00 or PQRSTZ99, the JCL can continue to read PGM=PQRST.

(Do not try this at home, or anywhere else for that matter.)

Robert Sample · Posted: Thu Oct 07, 2010 10:41 pm

Akatsukami, my brain hurts now. Thanks.

Akatsukami · Posted: Thu Oct 07, 2010 11:00 pm

Well, I had a dentist's appointment this morning, so I want everyone to be in at least as much pain as I am

jothibso · New User Joined: 03 Sep 2009 Posts: 18 Location: chennai

Thanks for the explanation ......