OS/390 was mid-1990s. I don’t remember the actual year. It sounds like the shop you were in had migrated from DOS/VS[E] and so continued with old phraseology. At least to me.
As at least one other referred to CIL (Core Image Library), non- DOS programmers would not know that DOS Linkedit pre-bound load modules to the Partition in which they would execute. Change the partition boundaries and life could get interesting. Think in terms of ACONs now pointing to the original addresses and not being relocated by the loader. And partition resizing was done when one needed more “core” to run certain programs where the system didn’t have enough memory (generally non-DAT machines but might be needed with 24bit DAT as well). Then, one needed subroutines that could self relocate so they were partition location independent. And the rest of my DOS memory appears to have been HSM migrated to the bit bucket. Sent from my iPhone — small keyboarf, fat fungrs, stupd spell manglr. Expct mistaks > On Oct 8, 2021, at 5:33 PM, Tony Thigpen <[email protected]> wrote: > > All I know is that the first MVS (or was it OS/390?) shop I worked with, > back in 1983, called them phases. After that shop, I was in VSE shops until > 10 years ago. Only upon returning to VSE did I first hear "load module" and > "objects". I just figured that when they moved to using "Binder", they > stopped using the old term. > > Tony Thigpen > > Seymour J Metz wrote on 10/8/21 5:15 PM: >> z/OS has program objects and load modules. Within legacy load modules there >> might be segments or overlays. But a/OS does not have phases. >> -- >> Shmuel (Seymour J.) Metz >> http://mason.gmu.edu/~smetz3 >> ________________________________________ >> From: IBM Mainframe Discussion List [[email protected]] on behalf of >> Tony Thigpen [[email protected]] >> Sent: Friday, October 8, 2021 11:30 AM >> To: [email protected] >> Subject: Re: Linkling an object from VSE to be used in z/OS >> A phase in z/VSE is the same as a phase in z/OS, But, the CSECT info is >> not as complete as in z/OS. While z/OS has the information for the >> original different CSECTs used to build the phase, z/VSE only saves the >> main CSECT identification information. Restated, all the subroutines >> that may have been hard-linked to the phase are in the phase, but there >> is not enough information to remove or replace one of the csects. >> So, when you punch the phase from z/VSE, you will see only one CSECT for >> the total program. >> In this discussion, the problem is that even if the COBOLII program was >> linked with LE 'parts' in z/VSE, those LE 'parts' may try to use z/VSE >> only pointers to branch into LE. >> So, I don't think it's going to work. >> Tony Thigpen >> Seymour J Metz wrote on 10/8/21 10:12 AM: >>> What do you consider to be the MVS equivalent of a phase, and what utility >>> are you using to convert a load module to an object module? >>> >>> Certainly you can relink (rebind) and delete extraneous csects but that's >>> somewhat of a manual process and still doesn't give you card images. >>> >>> >>> -- >>> Shmuel (Seymour J.) Metz >>> http://mason.gmu.edu/~smetz3 >>> >>> ________________________________________ >>> From: IBM Mainframe Discussion List [[email protected]] on behalf of >>> Tony Thigpen [[email protected]] >>> Sent: Thursday, October 7, 2021 8:39 PM >>> To: [email protected] >>> Subject: Re: Linkling an object from VSE to be used in z/OS >>> >>> Don't expect it to work. When VSE punches a phase, the link deck created >>> includes any called modules without any way to get them out. This is in >>> contrast to z/OS which produces all the individual modules. >>> >>> Tony Thigpen >>> >>> Gadi Ben-Avi wrote on 10/7/21 3:22 AM: >>>> Hi, >>>> I was asked to attempt to link a object deck from VSE in z/OS. >>>> The program is a COBOL2 program, but the source has been lost. >>>> >>>> The first few lines of the object deck are: >>>> W PHASE JKHIVX52,S+X'000000' >>>> W MODE AMODE(31),RMODE(ANY) >>>> W.ESD .. ..JKHIVX52.§.©..÷0 >>>> >>>> After that there are many (A little over 12,000) lines that start with >>>> W.TXT >>>> Next there are lines that start with W.RLD and a final like that starts >>>> with W.END. >>>> >>>> The JCL I used was >>>> //LKED EXEC PGM=IEWL, >>>> // PARM='LIST,XREF,NOLET,MAP', >>>> // REGION=2M >>>> //SYSLIN DD DSN=N623.PMKA.KPMAT.JKHIVX52,DISP=SHR >>>> //SYSLMOD DD DSNAME=V110GAD.LOAD(JKHIVX52),DISP=SHR >>>> //SYSUT1 DD UNIT=3390,SPACE=(CYL,(1,1)) >>>> //SYSPRINT DD SYSOUT=* >>>> //SYSIN DD * >>>> INCLUDE SYSLIN(JKHIVX52) >>>> NAME JKHIVX52(R) >>>> >>>> I am doing something wrong? >>>> Can this deck be linked into a usable z/OS load module? >>>> >>>> Thanks >>>> >>>> Gadi >>>> >>>> >>>> >>>> ---------------------------------------------------------------------- >>>> For IBM-MAIN subscribe / signoff / archive access instructions, >>>> send email to [email protected] with the message: INFO IBM-MAIN >>>> >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO IBM-MAIN >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO IBM-MAIN >>> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
