Tony,

The Cobol compiler won't be able to do it so your only solution is to
write a pre-processor. Wrote one myself back in 1982 (I think) to add a
copy-library capability to RPG II. It was written in SPL (and in-line
Assembler) and I might still have a printout of the source. If you have
somebody that understands SPL+Assembler they should be able to decipher
it and convert it (SPLash!, C, Pascal, even Cobol). Do you want me to
have a search for it?

regards,
 
Robert W.Mills
Business Systems Development Analyst
Group Information Systems & Technology
Pinnacle Arvato
DDI: +44 (0)20 8309 3604 


-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of Tony Summers
Sent: 30 July 2007 12:35
To: [log in to unmask]
Subject: [HP3000-L] HP3000 COBOL copy libraries

Dear Posters, 

Is anyone aware of an easy way of making the HP3000 cobol compiler
search a series of MPE groups in order to find a copylib module.

At present our programs use....

    COPY CFDB01. 
    COPY CFTONY OF COPYUTS.  

And our compile scripts issue some file equates before compiling the
program  ....

FILE COPYLIB=COPYNEW4.LIB
FILE COPYUTS=COPYUTS4.LIB
COB85XL SCPROG,,,etc 

The above is standard MPE resolution of copylibrary modules via COPYLIB
KSAM files (and has been discussed many times before on this list). 

However,  what we would like to be able to do is issue some more generic
"PATH" variable....

E.g. 

SETVAR COPYPATH="TONY.DEVELOP,LIB.DEVELOP,LIB.SYS" 

And then let the compiler find the relevant copylib modules from the
search path - with the requirement that if a module exists in multiple
locations then it will choose the first one that it finds !    E.g.  If
CFDB01 existed in both COPYLIB.TONY and COPYLIB.LIB then it would use
the .TONY version first. 

The reasoning behind my question is to prepare us for migration whilst
trying to support business as usual development.    What we're trying to
do is deploy the changes to our HP3000 development environment ahead of
formally migrating to Acucobol and Acubench.   

The fall-back position is to retain the status quo on the HP3000 and
split the KSAM copylibraries as they are migrated over to the new
environment (this procedure is proven).  However, I'm a bear with a
small brain and want to use the same procedure regardless of our
development environment. 

Regards to all. 




The contents of this email are confidential to the intended recipient
and may not be disclosed. Although it is believed that this email and
any attachments are virus free, it is the responsibility of the
recipient to confirm this.

Details of Smith & Williamson group companies and Nexia Smith &
Williamson Audit Limited and their regulators (where applicable), can be
found at this URL

http://www.smith.williamson.co.uk/disclosure

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *