Re: Modules prior to ILE Was: V6R1 Issue

["Steve Moland" <steve@xxxxxxxxxxx>]

> Well, modules don't exist without ILE...  A module contains the
> intermediate (w-code?) output of an ILE compiler.  I think C was the
> first compiler to support ILE.  Perhaps IBM laid in the plumbing for ILE
> in V2R3, but the compilers were not GA until later?  Maybe some ILE was
> PTF'd back to V2R3...

My partner wrote some of this stuff back in the very 1990s before there was 
ILE.

I know just enough C to help debug it but not enough to be comfortable to 
write much from scratch and I remember that all we had to work with back 
then was System C and I think C400. Neither handled I/O very well on the 400 
so we had to write our own higher level I/O routines so we could program the 
rest of the system in a less picky fashion. That worked and performance 
became acceptable. Once ILE C came out everything was changed to that.

Internally all the stuff is dual coded to run on intel platforms, hence the 
BIG_ENDIAN complier switch.

Everything went through CICS to RISC migrations fine and everything got 
compiled on RISC later at V4R3 but for earlier releases.

I'd just recompile the modules involved for a much later release, but many 
of these modules are at the heart of a ton of code, I'm afraid that 
something else might break.

Even though everything involved so far "appears" to have its creation code, 
I'm guess that there is some creation code that is not capable of moving 
forward. That's a totally uneducated guess and I would love to find one of 
those charts about version level compatibities which clearly stated the 
lines of demarcation.

The issue on this non-application stuff is like back in the Good? ole System 
34 days when you had to set up a Model 12 controller before you could bring 
it online. No such thing as auto-config. There were physical switches and 
software settings, some were base zero and some other references that were 
base 1. If you didn't do enough of it and didn't write it down completely, 
13 months later when you had to do it again, you were lost. Today, I have to 
toss in the senility factor to boot. [smile]

regards
Steve


> -Eric DeLong
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On 
> Behalf Of rob@xxxxxxxxx
> Sent: Thursday, April 23, 2009 1:18 PM
> To: Midrange Systems Technical Discussion
> Subject: Modules prior to ILE Was: V6R1 Issue
>
> Perhaps modules came out before ILE?  After all, that stuff was all C.
>
> Rob Berendt
> -- 
> Group Dekko Services, LLC
> Dept 01.073
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> From:
> "DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx>
> To:
> "Midrange Systems Technical Discussion" 
> <midrange-l@xxxxxxxxxxxx>
> Date:
> 04/23/2009 12:56 PM
> Subject:
> RE: V6R1 Issue
> Sent by:
> midrange-l-bounces@xxxxxxxxxxxx
>
>
>
> Interesting that the module had this attribute..
>
> Module created for . . . . . . . . . . . . . . :   V2R3M0
>
> I didn't think modules (ILE) became available until v3r0, but I'm a
> little hazy on the rollout of ILE.  I know some ILE support was added
> before ILE GA, but I didn't think it was v2r3...
>
> Probably has no bearing on your issue, but you never know...
>
> -Eric
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On 
> Behalf Of Steve Moland
> Sent: Thursday, April 23, 2009 11:22 AM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Re: V6R1 Issue
>
> Thanks for the reply Chuck,
>
>
> >   The F/pgm seemed odd to me, so searching only that token on the
> > web gives only two links [both related to Tivoli agent software but
> > the same issue] where VEXSIGEX was listed.  From that I was able to
> > see that the error MCH42B5 shares the msg\cause text, so presumably
> > msgMCH42B5 is what I wanted in the above <edit>.
>
> You are correct, MCH42B5 was the error code and all I could find was the
> same Tivoli reference.
>
> >  In the joblog, was the above  message preceded by any other?
>
> Nothing new or different than normal.
>
> >  Were there any VLIC logs for  around\before the date\time [04.22.09
> 10:59:18.2878] the error was  issued?
>
> Do know, haven't asked. They have about 25 boxes and just recently up'd
> 2 of them the V6R1
>
> Because it's a production box and at level 40 (at the request of the
> auditors) everything is screwed down so tight that having the tech
> person get anything including a command line takes hours.
>
> They let me use Netmeeting to try to be on the box in question but my
> borrowed sign-on didn't have authority to much and the "tell us what
> commands you need" bit doesn't work when I'm the prospecting mode.
>
> I just asked about the VLIC log.
>
> I'm not sure I know all the indications which leads one to believe that
> stuff is observable, however, I used WRKMOD and checked that each module
> had *YES for creation data.
>
> The program is C and other than the target release used, the rest of
> create command are the same.
>
> Here is the CRTMOD command used.
>
>
>   Command . . . . . . . . :   CRTCMOD MODULE(&L/&N) SRCFILE(&L/&F)
> SRCMBR(&N) O
> UTPUT(*PRINT) CHECKOUT(*NONE) OPTIMIZE(*NONE) DBGVIEW(*ALL)
> DEFINE(BIG_ENDIAN AS
> 400 EBCDIC ILE '_IS_QSYSINC' IS_IBMAS400) LANGLVL(*EXTENDED)
> TGTRLS(V3R2M0)
>
> Here is the CRTPGM command used.
>
>
>   Command . . . . . . . . :   CRTPGM PGM(&L/&N) MODULE(&N &L/*N)
> BNDDIR(TRSYS61
> 4T/TRGRCAT QSYS/QSNAPI TRSYS200T/APISECURE TRSYS614T/APIUTIL)
> DETAIL(*BASIC) TGT
> RLS(V4R2M0)
>
>
>
>
>
> >   What type of program is the IMPFRMCD object; what compiler?  Can
> > a DSPPGM output be obtained to review what the OS records about the
> > object?
>
> Here is the display PGM stuff
>
>
> Program creation information:
>
>   Program creation date/time . . . . . . . . . . :   12/02/04  10:30:50
>
>   Type of program  . . . . . . . . . . . . . . . :   ILE
>
>   Program entry procedure module . . . . . . . . :   IMPFRMCD
>
>     Library  . . . . . . . . . . . . . . . . . . :     TRSYS200T
>
>   Activation group attribute . . . . . . . . . . :   *NEW
>
>   Shared activation group  . . . . . . . . . . . :   *NO
>
>   User profile . . . . . . . . . . . . . . . . . :   *USER
>
>   Use adopted authority  . . . . . . . . . . . . :   *YES
>
>   Coded character set identifier . . . . . . . . :   65535
>
>   Number of modules  . . . . . . . . . . . . . . :   18
>
>
>  Number of service programs . . . . . . . . . . :   5
>  Number of unresolved references  . . . . . . . :   0
>  Number of copyrights . . . . . . . . . . . . . :   0
>  All creation data  . . . . . . . . . . . . . . :   *YES
>  Observable information compressed  . . . . . . :   *NO
>  Run time information compressed  . . . . . . . :   *NO
>  Allow update . . . . . . . . . . . . . . . . . :   *YES
>  Allow bound *SRVPGM library name update  . . . :   *NO
>  Profiling data . . . . . . . . . . . . . . . . :   *NOCOL
>  Teraspace storage enabled PEP  . . . . . . . . :   *NO
>  Teraspace storage enabled modules  . . . . . . :   *NONE
>
> Here is the module list
>
>                                          Creation  Optimization  Debug
> Opt  Module      Library     Attribute   Date         Level      Data
>      IMPFRMCD    TRSYS200T   CLE         01/25/02  *NONE         *YES
>      BIT         TRSYS200T   CLE         04/03/97  *NONE         *YES
>      GCATALOG    TRSYS200T   CLE         04/03/97  *NONE         *YES
>      GCDECOMP    TRSYS200T   CLE         04/03/97  *NONE         *YES
>      GCOMMON     TRSYS200T   CLE         04/03/97  *NONE         *YES
>      GSHARED     TRSYS200T   CLE         04/03/97  *NONE         *YES
>      LOADLONG    TRSYS200T   CLE         04/03/97  *NONE         *YES
>      XSECURE     TRSYS200T   CLE         04/03/97  *NONE         *YES
>
>      GCUSTOM     TRSYS200T   CLE         04/03/97  *NONE         *YES
>      APISYMBL    TRSYS200T   CLE         04/03/97  *NONE         *YES
>      STRUTIL     TRSYS200T   CLE         07/17/01  *NONE         *YES
>      XLATE       TRSYS200T   CLE         04/03/97  *NONE         *YES
>      DOSC400     TRSYS200T   CLE         04/03/97  *NONE         *YES
>      TRERROR     TRSYS200T   CLE         04/03/97  *NONE         *YES
>      ALLOC400    TRSYS200T   CLE         04/03/97  *NONE         *YES
>      APIUOBJ     TRSYS200T   CLE         07/17/01  *NONE         *YES
>      GETINI      TRSYS200T   CLE         08/30/01  *NONE         *YES
>      TRAUDIT     TRSYS200T   CLE         05/24/00  *NONE         *YES
>
>
> Here is a typical module.
>
>
> Module attributes:
>
>   Module . . . . . . . . . . . . . . . . . . . . :   BIT
>
>     Library  . . . . . . . . . . . . . . . . . . :     TRSYS200T
>
>   Source file  . . . . . . . . . . . . . . . . . :   GSRC
>
>     Library  . . . . . . . . . . . . . . . . . . :     TRSYS200T
>
>   Source member  . . . . . . . . . . . . . . . . :   BIT
>
>   Module attribute . . . . . . . . . . . . . . . :   CLE
>
>   Module creation date/time  . . . . . . . . . . :   04/03/97  13:39:01
>
>   Source file change date/time . . . . . . . . . :   08/29/96  09:41:20
>
>   Coded character set identifier . . . . . . . . :   37
>
>   Creation data  . . . . . . . . . . . . . . . . :   *YES
>
>   Sort sequence table  . . . . . . . . . . . . . :   *HEX
>
>   Language identifier  . . . . . . . . . . . . . :   *JOBRUN
>
>   Optimization level . . . . . . . . . . . . . . :   *NONE
>
>   Maximum optimization level . . . . . . . . . . :   *FULL
>
>  Debug data . . . . . . . . . . . . . . . . . . :   *YES
>  Profiling data . . . . . . . . . . . . . . . . :   *NOCOL
>  Number of procedures . . . . . . . . . . . . . :   8
>  Number of procedures block reordered . . . . . :   0
>  Number of procedures block order measured  . . :   0
>  Enable performance collection  . . . . . . . . :   *NONE
>  Teraspace storage enabled  . . . . . . . . . . :   *NO
>  Module created on  . . . . . . . . . . . . . . :   V4R3M0
>  Module created for . . . . . . . . . . . . . . :   V2R3M0
>  Object control level . . . . . . . . . . . . . :
>  User modified  . . . . . . . . . . . . . . . . :   *YES
>  Licensed program . . . . . . . . . . . . . . . :
>  PTF number . . . . . . . . . . . . . . . . . . :
>  APAR ID  . . . . . . . . . . . . . . . . . . . :
>  Licensed Internal Code options . . . . . . . . :   *NONE
>
>
>
> Steve Moland
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: 
> MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: 
> MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: 
> MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list
> To post a message email: 
> MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.