View previous topic :: View next topic
|
Author |
Message |
Prosenjit2011
New User
Joined: 15 Aug 2015 Posts: 3 Location: Singapore
|
|
|
|
Hi,
We have two sets of set of load modules one for ARCH(5) and one for ARCH(7).
In our current Mainframe , we can test ARCH(7) load only.
Is there a way we can determine a load is purely ARCH 5 ( not having any instruction, which is not valid for ARCH(5) ,like "LT 1,xxxx") or not, other than running and testing those in ARCH(5) machines. |
|
Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
|
|
|
|
Some indication of which language you are talking about would be helpful. |
|
Back to top |
|
|
Prosenjit2011
New User
Joined: 15 Aug 2015 Posts: 3 Location: Singapore
|
|
|
|
Hi ,
We are having C++ and COBOL modules. |
|
Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
|
|
|
|
ARCH(5) does not exist for COBOL, so no problem there.
You need to look at the C++ manuals. In COBOL the value of ARCH is stored in the Compiler Information Bytes (documented in the Programming Guide, you need V5 to have ARCH at all). See if the same thing is done with C++. |
|
Back to top |
|
|
Prosenjit2011
New User
Joined: 15 Aug 2015 Posts: 3 Location: Singapore
|
|
|
|
Hi,
Thanks for your suggession, I have tried to get "complier information byte" related detail by AMBLIST , but could not able to get such information.
We do only have C++ objects and loads, our test environment is in ARCH(7) , but one of production mainframe in ARCH(5).
We want to make sure , is there any traces of ARCH(7) into those modules, before move to ARCH(5) production environment.
Below AMBLIST code I have USED -
//STEP010 EXEC PGM=AMBLIST
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//LOADLB DD DSN=MY.LOADLIB.DIR,DISP=SHR
//SYSIN DD *
LISTIDR DDN=LOADLB,MEMBER=xxxxxx |
|
Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
|
|
|
|
The point of the ARCH compiler option is so that you can develop on one machine to target another. On your "Arch(7)" machine, if you compile with ARCH(5), you will not have a problem.
AMBLIST does not know about the Compiler information. |
|
Back to top |
|
|
|