RE: V6R1 Issue

["M. Lazarus" <mlazarus@xxxxxxxx>]

Eric,

 IIRC, ILE C was available for V2R3.  ILE RPG was released for V3R1.

 -mark

At 4/23/09 12:53 PM, you wrote:
> 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