In fact,  one of my colleagues came up with a neat suggestion.  

We're going to break-up our MPE copylibraries into one file per module
and we have written a script and small program to re-construct the
standard MPE KSAM copylibrary from those fragmented files.  

Got the best of both worlds 

A) Each module will now be subject to source control 
B) We're preparing for the world after we migrate off the HP3000.

-----Original Message-----
From: Keven Miller (rtt) [mailto:[log in to unmask]] 
Sent: 25 August 2007 16:57
To: Tony Summers
Cc: [log in to unmask]
Subject: Re: [HP3000-L] HP3000 COBOL copy libraries

Tony Summers wrote:
> 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" 

When we took over the HPMMII product at eXegeSys, Inc, it came with a
development package made by HP called PDE (Parallel development
environment).
All it really is, is a set of command scripts, a defined mpe GROUP and
ACCOUNT structure, and use of HPSRC (source control).

What you describe as desiring to do is just what it did.
We would have group names for each release version:
	PMA0307
	PMA0307N
	PMA0307O
	PMA0307P
	PMA0308
The complete sources at a major release would be kept in that release's
group: PMA0307.
When you worked on a version, you would check out the sources in your
logon group: PMA0307N.
This groups would only contain the sources for what was changed from the
major release.

The compile scripts, would have a PATH variable set to include all the
groups, in reverse order.
Then for each file the was needed to compile (sources were scanned for
$INCLUDEs), its existence was checked following down this PATH variable,
and a file equation was created.
When that was done, the compile would follow.

Keven Miller


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 *