IBM Mainframe Discussion List <[email protected]> wrote on 02/13/2006 09:44:22 AM:
> On Mon, 13 Feb 2006 12:53:10 +0200, Arie Kremer <[EMAIL PROTECTED]> wrote: > > >Hi all, > > > >we use MVS System logger in our products. We compile on OS390 2.10. > >One of our customers tried to run it on his OS390 2.8 (we hope it is > correct > >info). They received return code 8, reason code '840'x after IXGBRWSE from > >an empty log. > > > >This reason code is not documented. > >http://www.redbooks.ibm.com/redbooks/pdfs/sg246377.pdf contains the > follows: > > > >*Migration and coexistence* > > > >Logger macros with the BUFFER64 keyword can be compiled or assembled on a > > > >z-Architecture mode machine. If you try to execute it on a pre-z/OS V1R6 > >system, it will fail > > > >with return code 8, reason code '840'x (Bad version). > > > >We do not use BUFFERS64, nor compile on z/OS. > > > >HELP !!! > > > > > Tell the client to get on a supported level of the OS! :-) > > (just kidding, I realize mnay vendors have to support old OS releases) > > The doc on the error is right on your own OS/390 2.10 system: > > BROWSE SYS1.MACLIB(IXGBRWSE) Line 00001792 Col > Command ===> Scroll = > * * > * xxxx0840 08 IXGRSNCODEBADVERSION - * > * * > * * > * EXPLANATION: Environment error. The * > * parameter list passed to the service * > * routine had an invalid version indicator. * > * * > * * > * ACTION: Ensure the level of MVS * > * executing the request and the macro * > * library used to compile the invoking * > * routine are compatible. * > * * > * * > > OS/390 2.8 was able to coexist with OS/390 2.10. Perhaps your > client does not have that maintenance (2.10 coexistence) applied > on their system. If not, you may need a copy of their macro library. > > In looking at the macro (which I've never used), perhaps it also has > something to do with PLISTVER (see usage note #3). OS390 2.8 allowed PLISTVER 0 and 1. OS390 2.10 added PLISTVER 2, for keywords MAXNUMLOGBLOCKS, MULTIBLOCK, and RETBLOCKINFO, If you want code assembled with 2.10 to run on 2.8, you must avoid specifying these keywords (and also do not specify PLISTVER=MAX). The safest thing would be to explicitly specify PLISTVER=1, as I think that will fail the assembly if you also specify a keyword which requires a higher PLISTVER. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
