ACCOUNT= SYS GROUP= PUB4
FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
CCMSGCAT 128W FB 229 104800 1 240 1 8
CCOMXL NMPRG 128W FB 9426 9426 1 9440 1 8
CCSTDRL 72B FA 3 3 3 16 1 1
CCXL 80B FA 41 41 3 16 1 1
CCXLGO 80B FA 69 69 1 32 1 1
CCXLLK 80B FA 56 56 1 32 1 1
LIBC NMRL 128W FB 1543 1543 8 1552 7 8
LIBCANDT NMRL 128W FB 13 13 1 16 1 1
LIBCANSI NMRL 128W FB 11 11 1 16 1 1
LIBCINIT NMRL 128W FB 331 331 1 336 2 8
LIBCRAND NMRL 128W FB 13 13 1 16 1 1
LIBM NMRL 128W FB 297 297 1 304 2 1
LINKEDIT NMPRG 128W FB 2956 2956 1 2960 1 1
SOCKETRL NMRL 128W FB 7214 4096000 1 7216 7 32
XDBEND NMOBJ 128W FB 9 9 1 16 1 1
XL NMXL 128W FB 60247 4096000 1 60256 1 *
We've modified all the command files to reference CCOMXL.PUB4.SYS and the LIBC@.PUB4.SYS. This has worked very well for us so far....
We face this with each update. Our production systems stay on the old GS version while the devlopment system experiments with the new. This can take weeks, and the applications programmers need to gen patches.
I know this doesn't apply to a developer, but we keep each version of the compiler and libraries in alternate groups and during this phase, put the old compilers in PUB.SYS and the old libraries in H.SYS and LIB.SYS. This way the programmrs generate 4.0 code, which will run in production, and on the 5.0 development system as well.
If you took this logic a bit further, you could create command files that allowed the version number to be set/passed, and execute the appropriate compilers. How you would handle #includes is a tricker problem.
--RichTrapp?
| Topic Hp3000ProgrammingLanguages . { Edit | Attach | Backlinks: Web All webs | Printable | History: r3 < r2 < r1 More } |
|
Ideas, requests, problems regarding TWiki? Send feedback Note: Please contribute updates to this topic on TWiki.org at TWiki:TWiki.Hp3000ProgrammingLanguages |