Re: Replacement for the NCZ93205 subroutine.

Oh No - Busted by the IT auditor.

I did not think any one would be interested in such detailed change
control/audit trail information.

Ed
--- In [email protected], "halfmeg" <opplr@...> wrote:
>
> > cedarlakebuzzards wrote:
>
> > The new version has two new functions added that allow sequential
> > reading of the PDS directory (to retrieve member name) from COBOL
> > programs.  In addition,  PL/1 (F) programs can call and access all
> > of the functions.  The module was renamed to PDSGET with entry
> > points/aliases of NCZ93205 and PDSGETP.  PL/I (F) restricts external
> > program names to 7 characters.
>
> > If you don't want to read the directory or call it from PL/I,  this
> > module offers nothing new over the "old" NCZ93205.
>
> ><snip>
>
> Ok, I've looked over both and the original.
>
> Original is on CBT Overflow tape file #12 as u87003as.
> Jay Moseley made modifications and posted on his site in 2004.
> You modified Jay's version ( dropped *JLM* from his changes in open
but left *JLM* in place for the +40 change IIRC ).
>
> Along the way you used GETDIR from CBT Tape file #183 and found;
> ".GEN   AIF   (D,GETDIR).MEND " 'D' not supported in IFOX00.
>
> Jay's install puts the module in SYS2.LINKLIB.  Since it isn't in the
TK3UPD system it seems to have never made it into TK3 at all.  Both
versions use different inline macros which is fine for standalone
installs, but what happens when what should be a common macro changes. 
You would have a need to update each source deck which uses the macro
inline to the new level.  I haven't checked whether GETDIR is in a
MACLIB on TK3.
>
> So, all that to pose a few of questions.
>
> What would you suggest is the best method to annotate the source as to
where it came from and who made changes ?
>
> The AMENDMENT HISTORY section only shows the original entry from 1982.
>
> Could the change to GETDIR, which comes from Gilbert Saint-flour's CBT
file # 183, be modified so that it works as originally written and only
uses the IFOX00 amendment if IFOX00 is being used?
>
> If so, it would eliminate the need for maintaining a separate version
for IFOX00.
>
> IIRC inline MACROs override the same named MACRO in a MACLIB.  Would a
temp MACLIB with the inline MACROs moved to it be beneficial for
assembly/compilation on various levels of systems ?
>
> Phil - bear with me folks - part of this exercise was to re-acquaint
myself with this stuff after letting it go for a while
>