MIDRANGE dot COM Mailing List Archive



Home » JAVA400-L » October 2005

MCH3601 from CRTJVAPGM command?



fixed

I ran the following command and ended up with 2150 pages of MCH3601
errors.  Any ideas?  (It is a third party .JAR, completely self
contained.)

COMMAND:

CRTJVAPGM CLSF('/XXXXXX/YYYYYY.jar') JDKVER('1.4.2') OPTIMIZE(40)


PARTIAL LOG:

MCH3601    Escape                  40    10/20/05   10:52:01
QJVASYSSRV     QSYS        *STMT    QJVASYSSRV   QSYS         *STMT 
       From module . . . . . . . . :   QJVASYSSRV

       From procedure  . . . . . . :   CRTJVPG_getVnodePtr

       Statement . . . . . . . . . :   2687

       To module . . . . . . . . . :   QJVASYSSRV

       To procedure  . . . . . . . :   CRTJVPG_getVnodePtr

       Statement . . . . . . . . . :   2687

       Message . . . . :   Pointer not set for location referenced.

       Cause . . . . . :   A pointer was used, either directly or as a
basing                        
                           pointer, that has not been set to an address.


< MUCH CUT - 2100+ pages of MCH3601 errors, all the same as above >

MCH3203    Escape                  60    10/20/05   16:25:54   <
izeNoToken               000CA8   QJVASYS      QSYS         *STMT 
       From Program  . . . . . . . :   RmslReleaseSeizeNoToken

       To module . . . . . . . . . :   QJVASYS

       To procedure  . . . . . . . :   MI_CRTJVPG

       Statement . . . . . . . . . :   1805

       Message . . . . :   Function error X'1720' in machine
instruction. Internal                   
                           dump identifier (ID) 01001174.

       Cause . . . . . :   The machine instruction that was running
failed. Time                     
                           stamp is 10/20/05 16:25:50, error code is
X'1720', error class is 
                           0, device number is X'0000'. The error class
indicates how the 
                           damage was detected: 
                           0000-unspecified abnormal condition;
0002-logically invalid device 
                           sector; 0003-device failure. For error class
0003, the device 
                           number identifies the failing device, or
contains zero if main 
                           storage failed. Recovery  . . . :  Start
problem analysis (ANZPRB 
                           command).                  
JVAB56F    Diagnostic              40    10/20/05   16:25:54
QJVASYSSRV     QSYS        *STMT    QJVASYSSRV
       From module . . . . . . . . :   QJVASYSSRV

       From procedure  . . . . . . :   Send_Msg_Msgf__FPcT1iN21T3

       Statement . . . . . . . . . :   2310

       To module . . . . . . . . . :   QJVASYSSRV

       To procedure  . . . . . . . :   SendMsgCCSID

       Statement . . . . . . . . . :   2291

       Message . . . . :   Unable to complete processing.

       Cause . . . . . :   Unable to complete processing for the
following reason: 
                           "Unexpected exception" Recovery  . . . :   If
the error is a 
                           permission or authorization error, contact
your system security 
                           officer to obtain the authority needed.
Otherwise try the command 
                           again.                        
JVAB532    Escape                  40    10/20/05   16:25:54
QJVASYSSRV     QSYS        *STMT    QCMD 
       From module . . . . . . . . :   QJVASYSSRV

       From procedure  . . . . . . :   Send_Msg_Msgf__FPcT1iN21T3

       Statement . . . . . . . . . :   2310

       Message . . . . :   Unable to create Java program for
"/XXXXXX/YYYYYY.jar". 
       Cause . . . . . :   Unable to create Java program for class file

                           "/XXXXXX/YYYYYY.jar". Recovery  . . . :   See
messages listed on 
                           This display or in the job log by using the
Display Job Log 
                           (DSPJOBLOG) command.
                           Correct any errors and try the command again.

CPC2402    Completion              50    10/20/05   16:25:54   QCMD
QSYS        05D4     *EXT           
       Message . . . . :   Job ended. Cancel message received at command
processor. 
       Cause . . . . . :   A message with a severity equal to or
exceeding the end  
                           severity was received at the command
processor. Recovery  . . . :
                           See the messages previously listed to
determine the message that 
                           caused the job to be ended. Correct the
errors, and then try the
                           request again.






 <<Chris Wolcott.vcf>> 





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact