Re: Linkage Editing VSE Phase in z/OS
In CAKvHmLtCsh_B8uJmzXVomWVVhOi06p=pwc-o0gvbppc2an2...@mail.gmail.com, on 08/09/2013 at 04:13 PM, Roberto Halais roberto.hal...@gmail.com said: We are doing a VSE to z/OS conversion and had to do the following since we have no source. Ouch! We put the phase in a z/os pds member (lrecl 80) How? If you used FTP, was it in binary mode? IEW2359E 240B SECTION FA010 CONTAINS AN RLD WITH AN INVALID ADCON LOCATION. CLASS = B_TEXT, ELEMENT OFFSET = FFAFFF88 Does VSE support negative offsets? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Linkage Editing VSE Phase in z/OS
Listers: We are doing a VSE to z/OS conversion and had to do the following since we have no source. We punched out a CIL phase from a VSE system. We put the phase in a z/os pds member (lrecl 80) and it looked like this: Phase modname ESD TXT RLD END /* We edited the phase so that it looked like this: ESD TXT RLD END We then tried to linkedit the phase with IEWL and got the following messages: z/OS V1 R13 BINDER 15:51:52 FRIDAY AUGUST 9, 2013 BATCH EMULATOR JOB(LINKEDT2) STEP(LKED) PGM= IEWL IEW2278I B352 INVOCATION PARAMETERS - XREF,LIST IEW2359E 240B SECTION FA010 CONTAINS AN RLD WITH AN INVALID ADCON LOCATION. CLASS = B_TEXT, ELEMENT OFFSET = FFAFFF88 IEW2307E 1113 CURRENT INPUT MODULE NOT INCLUDED BECAUSE OF INVALID DATA. IEW2322I 1220 3NAME HA010(R) IEW2230S 0414 MODULE HAS NO TEXT. IEW2648E 5111 ENTRY RR$$AA IS NOT A CSECT OR AN EXTERNAL NAME IN THE MODULE. IEW2677S 5130 A VALID ENTRY POINT COULD NOT BE DETERMINED. IEW2008I 0F03 PROCESSING COMPLETED. RETURN CODE = 12. Any ideas? Thank you, Roberto -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Linkage Editing VSE Phase in z/OS
I would think what you described might well work. I don't see any inherent flaws in the process. RLD cards are documented and not at all impossible to decode. You could post the offending RLD here (in hex) and I'm sure folks would love to demonstrate their skills. You could also try a disassembler. (CBT tape has one, right?) Disassembled object code is a real piece of cowstuff but you could re-assemble it and try that approach. What's the possibility that you garbled things in the editor, or somewhere else along the way? Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Roberto Halais Sent: Friday, August 09, 2013 4:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Linkage Editing VSE Phase in z/OS Listers: We are doing a VSE to z/OS conversion and had to do the following since we have no source. We punched out a CIL phase from a VSE system. We put the phase in a z/os pds member (lrecl 80) and it looked like this: Phase modname ESD TXT RLD END /* We edited the phase so that it looked like this: ESD TXT RLD END We then tried to linkedit the phase with IEWL and got the following messages: z/OS V1 R13 BINDER 15:51:52 FRIDAY AUGUST 9, 2013 BATCH EMULATOR JOB(LINKEDT2) STEP(LKED) PGM= IEWL IEW2278I B352 INVOCATION PARAMETERS - XREF,LIST IEW2359E 240B SECTION FA010 CONTAINS AN RLD WITH AN INVALID ADCON LOCATION. CLASS = B_TEXT, ELEMENT OFFSET = FFAFFF88 IEW2307E 1113 CURRENT INPUT MODULE NOT INCLUDED BECAUSE OF INVALID DATA. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Linkage Editing VSE Phase in z/OS
Charles: Thank you for your comments. I cannot identify the offending RLD. I'll revise the loading procedure to see if I garbled the RLD. On Fri, Aug 9, 2013 at 4:21 PM, Charles Mills charl...@mcn.org wrote: I would think what you described might well work. I don't see any inherent flaws in the process. RLD cards are documented and not at all impossible to decode. You could post the offending RLD here (in hex) and I'm sure folks would love to demonstrate their skills. You could also try a disassembler. (CBT tape has one, right?) Disassembled object code is a real piece of cowstuff but you could re-assemble it and try that approach. What's the possibility that you garbled things in the editor, or somewhere else along the way? Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Roberto Halais Sent: Friday, August 09, 2013 4:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Linkage Editing VSE Phase in z/OS Listers: We are doing a VSE to z/OS conversion and had to do the following since we have no source. We punched out a CIL phase from a VSE system. We put the phase in a z/os pds member (lrecl 80) and it looked like this: Phase modname ESD TXT RLD END /* We edited the phase so that it looked like this: ESD TXT RLD END We then tried to linkedit the phase with IEWL and got the following messages: z/OS V1 R13 BINDER 15:51:52 FRIDAY AUGUST 9, 2013 BATCH EMULATOR JOB(LINKEDT2) STEP(LKED) PGM= IEWL IEW2278I B352 INVOCATION PARAMETERS - XREF,LIST IEW2359E 240B SECTION FA010 CONTAINS AN RLD WITH AN INVALID ADCON LOCATION. CLASS = B_TEXT, ELEMENT OFFSET = FFAFFF88 IEW2307E 1113 CURRENT INPUT MODULE NOT INCLUDED BECAUSE OF INVALID DATA. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Men will never be free until the last king is strangled with the entrails of the last priest. Denis Diderot -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Linkage Editing VSE Phase in z/OS
Couple things to check. BLKSIZE less than 3200. Nulls off. FF is like EOL for editor with Nulls on. HLASM also has disassembler but have never used on conversion attempts. In a message dated 8/9/2013 3:36:08 PM Central Daylight Time, roberto.hal...@gmail.com writes: I'll revise the loading procedure to see if I garbled the RLD -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Linkage Editing VSE Phase in z/OS
I don't know if what you are attempting to do will work. There are most likely VCONs to VSE transients that aren't going to be resolved in z/OS. Also, I believe there are structures like COMREG that won't translate to OS because they aren't there, at least not by name and not by location though they may be present in concept. Also, doesn't VSE have some RLD entries that are partition offset based? I think the best suggestion is to grab the source to a disassembler from the CBT, assemble and link it in the VSE world and execute it there. Then, take the generated source and move it to z/OS and try assembling it there. If the program has disk file definitions, ie the VSE counterpart to a DCB, the disassembler may not know what to do with them. Good luck. Chuck Charles (Chuck) Hardee Senior Systems Engineer/Database Administration CCG Information Technology Thermo Fisher Scientific 300 Industry Drive Pittsburgh, PA 15275 Direct: 724-517-2633 FAX: 412-490-9230 chuck.har...@thermofisher.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of efinnell15 Sent: Friday, August 09, 2013 4:42 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Linkage Editing VSE Phase in z/OS Couple things to check. BLKSIZE less than 3200. Nulls off. FF is like EOL for editor with Nulls on. HLASM also has disassembler but have never used on conversion attempts. In a message dated 8/9/2013 3:36:08 PM Central Daylight Time, roberto.hal...@gmail.com writes: I'll revise the loading procedure to see if I garbled the RLD -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Linkage Editing VSE Phase in z/OS
I cannot identify the offending RLD. Ah. I had thought the link editor printed offending cards. I know what I am thinking of -- if it can't identify the card at all it prints the first three bytes in hex. How many RLD cards are there? You could delete from the bottom until you found the offending one, although this is starting to seem like a kludge supporting a kludge. The 240B might be a further clue if one knew how to decode it. What happens if you do not edit? PHASE is certainly an error in z/OS but does the link editor keep going or abandon the file? Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Roberto Halais Sent: Friday, August 09, 2013 4:36 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Linkage Editing VSE Phase in z/OS Charles: Thank you for your comments. I cannot identify the offending RLD. I'll revise the loading procedure to see if I garbled the RLD. On Fri, Aug 9, 2013 at 4:21 PM, Charles Mills charl...@mcn.org wrote: I would think what you described might well work. I don't see any inherent flaws in the process. RLD cards are documented and not at all impossible to decode. You could post the offending RLD here (in hex) and I'm sure folks would love to demonstrate their skills. You could also try a disassembler. (CBT tape has one, right?) Disassembled object code is a real piece of cowstuff but you could re-assemble it and try that approach. What's the possibility that you garbled things in the editor, or somewhere else along the way? Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Roberto Halais Sent: Friday, August 09, 2013 4:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Linkage Editing VSE Phase in z/OS Listers: We are doing a VSE to z/OS conversion and had to do the following since we have no source. We punched out a CIL phase from a VSE system. We put the phase in a z/os pds member (lrecl 80) and it looked like this: Phase modname ESD TXT RLD END /* We edited the phase so that it looked like this: ESD TXT RLD END We then tried to linkedit the phase with IEWL and got the following messages: z/OS V1 R13 BINDER 15:51:52 FRIDAY AUGUST 9, 2013 BATCH EMULATOR JOB(LINKEDT2) STEP(LKED) PGM= IEWL IEW2278I B352 INVOCATION PARAMETERS - XREF,LIST IEW2359E 240B SECTION FA010 CONTAINS AN RLD WITH AN INVALID ADCON LOCATION. CLASS = B_TEXT, ELEMENT OFFSET = FFAFFF88 IEW2307E 1113 CURRENT INPUT MODULE NOT INCLUDED BECAUSE OF INVALID DATA. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Men will never be free until the last king is strangled with the entrails of the last priest. Denis Diderot -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Linkage Editing VSE Phase in z/OS
Well sure, absolutely, lots of VSE things won't work in z/OS: COMREG and any other control block chasing DTFs Most or all SVCs including the one that ends a jobstep program I was assuming the OP knew that and that this was somehow pure non-OS code. But you're right, if it's an executable phase then it almost certainly has some sort of external interface other than entry and return. It could be a loadable, callable pure subroutine, but that's unlikely. Relocatable core image came along after I moved on from DOS/360 to the greener pastures of OS/360, so I am not familiar with RLDs in core images, or VCONs to VSE transients. If the program has disk file definitions, ie the VSE counterpart to a DCB, the disassembler may not know what to do with them. Well (a.) the HLASM is also a VSE product, so the disassembler should be VSE-aware, right? And (b.) my guess is that it will do what most disassemblers do with most macro-generated code: disassemble it as open code blissfully innocent of macros. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hardee, Chuck Sent: Friday, August 09, 2013 4:48 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Linkage Editing VSE Phase in z/OS I don't know if what you are attempting to do will work. There are most likely VCONs to VSE transients that aren't going to be resolved in z/OS. Also, I believe there are structures like COMREG that won't translate to OS because they aren't there, at least not by name and not by location though they may be present in concept. Also, doesn't VSE have some RLD entries that are partition offset based? I think the best suggestion is to grab the source to a disassembler from the CBT, assemble and link it in the VSE world and execute it there. Then, take the generated source and move it to z/OS and try assembling it there. If the program has disk file definitions, ie the VSE counterpart to a DCB, the disassembler may not know what to do with them. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Linkage Editing VSE Phase in z/OS
I guess you all are correct. We will try the disassembler route. Thank you all for your pointers. (By the way I tried all the stuff some of you suggested but got same message.) It was a good try. Thank you again. On Fri, Aug 9, 2013 at 5:04 PM, Charles Mills charl...@mcn.org wrote: Well sure, absolutely, lots of VSE things won't work in z/OS: COMREG and any other control block chasing DTFs Most or all SVCs including the one that ends a jobstep program I was assuming the OP knew that and that this was somehow pure non-OS code. But you're right, if it's an executable phase then it almost certainly has some sort of external interface other than entry and return. It could be a loadable, callable pure subroutine, but that's unlikely. Relocatable core image came along after I moved on from DOS/360 to the greener pastures of OS/360, so I am not familiar with RLDs in core images, or VCONs to VSE transients. If the program has disk file definitions, ie the VSE counterpart to a DCB, the disassembler may not know what to do with them. Well (a.) the HLASM is also a VSE product, so the disassembler should be VSE-aware, right? And (b.) my guess is that it will do what most disassemblers do with most macro-generated code: disassemble it as open code blissfully innocent of macros. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hardee, Chuck Sent: Friday, August 09, 2013 4:48 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Linkage Editing VSE Phase in z/OS I don't know if what you are attempting to do will work. There are most likely VCONs to VSE transients that aren't going to be resolved in z/OS. Also, I believe there are structures like COMREG that won't translate to OS because they aren't there, at least not by name and not by location though they may be present in concept. Also, doesn't VSE have some RLD entries that are partition offset based? I think the best suggestion is to grab the source to a disassembler from the CBT, assemble and link it in the VSE world and execute it there. Then, take the generated source and move it to z/OS and try assembling it there. If the program has disk file definitions, ie the VSE counterpart to a DCB, the disassembler may not know what to do with them. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Men will never be free until the last king is strangled with the entrails of the last priest. Denis Diderot -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Linkage Editing VSE Phase in z/OS
Chuck, *WAY BACK* in the 70's I used to punch out the macro definitions and put them into a PDS (had to write a quick and dirty pgm to create ./ add name= and insert them before each MACRO definitions. Then I assembled DOS pgms on OS/360 (MFT if it matters) and took the object decks and linked them on DOS it worked like a charm. The MFT assembler output worked fine on DOS system. Mind you there were no complicated programs with overlays etc but it did work. Ed On Aug 9, 2013, at 3:48 PM, Hardee, Chuck wrote: I don't know if what you are attempting to do will work. There are most likely VCONs to VSE transients that aren't going to be resolved in z/OS. Also, I believe there are structures like COMREG that won't translate to OS because they aren't there, at least not by name and not by location though they may be present in concept. Also, doesn't VSE have some RLD entries that are partition offset based? I think the best suggestion is to grab the source to a disassembler from the CBT, assemble and link it in the VSE world and execute it there. Then, take the generated source and move it to z/OS and try assembling it there. If the program has disk file definitions, ie the VSE counterpart to a DCB, the disassembler may not know what to do with them. Good luck. Chuck Charles (Chuck) Hardee Senior Systems Engineer/Database Administration CCG Information Technology Thermo Fisher Scientific 300 Industry Drive Pittsburgh, PA 15275 Direct: 724-517-2633 FAX: 412-490-9230 chuck.har...@thermofisher.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM- m...@listserv.ua.edu] On Behalf Of efinnell15 Sent: Friday, August 09, 2013 4:42 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Linkage Editing VSE Phase in z/OS Couple things to check. BLKSIZE less than 3200. Nulls off. FF is like EOL for editor with Nulls on. HLASM also has disassembler but have never used on conversion attempts. In a message dated 8/9/2013 3:36:08 PM Central Daylight Time, roberto.hal...@gmail.com writes: I'll revise the loading procedure to see if I garbled the RLD -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Linkage Editing VSE Phase in z/OS
Yep, been there, done that too. Now that you mention it, maybe the OP should think about doing that as well after the disassembled source is available. I used to work for a software vendor and we distributed a VSE version of our product and we had macros like that as well as some in-house routines that answered to the call of some VSE EXTRNs. Charles (Chuck) Hardee Senior Systems Engineer/Database Administration CCG Information Technology Thermo Fisher Scientific 300 Industry Drive Pittsburgh, PA 15275 Direct: 724-517-2633 FAX: 412-490-9230 chuck.har...@thermofisher.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Gould Sent: Friday, August 09, 2013 5:19 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Linkage Editing VSE Phase in z/OS Chuck, *WAY BACK* in the 70's I used to punch out the macro definitions and put them into a PDS (had to write a quick and dirty pgm to create ./ add name= and insert them before each MACRO definitions. Then I assembled DOS pgms on OS/360 (MFT if it matters) and took the object decks and linked them on DOS it worked like a charm. The MFT assembler output worked fine on DOS system. Mind you there were no complicated programs with overlays etc but it did work. Ed On Aug 9, 2013, at 3:48 PM, Hardee, Chuck wrote: I don't know if what you are attempting to do will work. There are most likely VCONs to VSE transients that aren't going to be resolved in z/OS. Also, I believe there are structures like COMREG that won't translate to OS because they aren't there, at least not by name and not by location though they may be present in concept. Also, doesn't VSE have some RLD entries that are partition offset based? I think the best suggestion is to grab the source to a disassembler from the CBT, assemble and link it in the VSE world and execute it there. Then, take the generated source and move it to z/OS and try assembling it there. If the program has disk file definitions, ie the VSE counterpart to a DCB, the disassembler may not know what to do with them. Good luck. Chuck Charles (Chuck) Hardee Senior Systems Engineer/Database Administration CCG Information Technology Thermo Fisher Scientific 300 Industry Drive Pittsburgh, PA 15275 Direct: 724-517-2633 FAX: 412-490-9230 chuck.har...@thermofisher.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM- m...@listserv.ua.edu] On Behalf Of efinnell15 Sent: Friday, August 09, 2013 4:42 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Linkage Editing VSE Phase in z/OS Couple things to check. BLKSIZE less than 3200. Nulls off. FF is like EOL for editor with Nulls on. HLASM also has disassembler but have never used on conversion attempts. In a message dated 8/9/2013 3:36:08 PM Central Daylight Time, roberto.hal...@gmail.com writes: I'll revise the loading procedure to see if I garbled the RLD -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Linkage Editing VSE Phase in z/OS
On 8/9/2013 1:13 PM, Roberto Halais wrote: We punched out a CIL phase from a VSE system. [snip] We then tried to linkedit the phase with IEWL and got the following messages: Even if you could get this program through the binder, what are the chances it will work? How many programs don't access files, acquire storage, or even print the date/time? The SVCs, parameter lists, and control blocks that interface to these system services on z/VSE are *completely* different from their z/OS counterparts. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Linkage Editing VSE Phase in z/OS
The exact same thread is going on over on the VSE list. Pretty much the same answers too! Chuck Arney Arney Computer Systems On Aug 9, 2013, at 3:13 PM, Roberto Halais roberto.hal...@gmail.com wrote: Listers: We are doing a VSE to z/OS conversion and had to do the following since we have no source. We punched out a CIL phase from a VSE system. We put the phase in a z/os pds member (lrecl 80) and it looked like this: Phase modname ESD TXT RLD END /* We edited the phase so that it looked like this: ESD TXT RLD END We then tried to linkedit the phase with IEWL and got the following messages: z/OS V1 R13 BINDER 15:51:52 FRIDAY AUGUST 9, 2013 BATCH EMULATOR JOB(LINKEDT2) STEP(LKED) PGM= IEWL IEW2278I B352 INVOCATION PARAMETERS - XREF,LIST IEW2359E 240B SECTION FA010 CONTAINS AN RLD WITH AN INVALID ADCON LOCATION. CLASS = B_TEXT, ELEMENT OFFSET = FFAFFF88 IEW2307E 1113 CURRENT INPUT MODULE NOT INCLUDED BECAUSE OF INVALID DATA. IEW2322I 1220 3NAME HA010(R) IEW2230S 0414 MODULE HAS NO TEXT. IEW2648E 5111 ENTRY RR$$AA IS NOT A CSECT OR AN EXTERNAL NAME IN THE MODULE. IEW2677S 5130 A VALID ENTRY POINT COULD NOT BE DETERMINED. IEW2008I 0F03 PROCESSING COMPLETED. RETURN CODE = 12. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
