× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thank you very much for the reply. Here is the joblog. Hope you don't mind
if I email it to you as well, in case the reformatting wrecks it.

Is it possible that I am hitting a limit on java classpath size rather than
environment? I do not believe we are anywhere close to 16MB or 4095
variables.

THANKS AGAIN,
-Marty

(I apologize to the list for posting whole joblog)


 5722SS1 V5R2M0 020719                           Job Log
ISDDEV04 08/15/03 16:07:02          Page    1
  Job name . . . . . . . . . . :   QP0ZSPWP        User  . . . . . . :
MURBANEK     Number . . . . . . . . . . . :   087940
  Job description  . . . . . . :   SIDEVJOBD       Library . . . . . :
QGPL
MSGID      TYPE                    SEV  DATE      TIME             FROM PGM
LIBRARY     INST     TO PGM      LIBRARY     INST
CPF1124    Information             00   08/15/03  16:07:01.117656  QWTPIIPP
QSYS        05D4     *EXT                    *N
                                     Message . . . . :   Job
087940/MURBANEK/QP0ZSPWP started on 08/15/03 at
                                       16:07:01 in subsystem QINTER in QSYS.
Job entered system on 08/15/03 at
                                       16:07:01.
MCH3601    Escape                  40   08/15/03  16:07:01.908904
QJVAQSHCMD   QSYS        *STMT    QJVAQSHCMD  QSYS        *STMT
                                     From module . . . . . . . . :
QJVAQSHCMD
                                     From procedure  . . . . . . :
optProperties__FPcT1
                                     Statement . . . . . . . . . :   2054
                                     To module . . . . . . . . . :
QJVAQSHCMD
                                     To procedure  . . . . . . . :
optProperties__FPcT1
                                     Statement . . . . . . . . . :   2054
                                     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.
JVAB544    Escape                  40   08/15/03  16:07:01.909768
QJVAQSHCMD   QSYS        *STMT    QJVATJAVA   QSYS        *STMT
                                     From module . . . . . . . . :
QJVAQSHCMD
                                     From procedure  . . . . . . :
SendMsg__FPcT1iT1T3N21
                                     Statement . . . . . . . . . :   2569
                                     To module . . . . . . . . . :
QJVATOOLS
                                     To procedure  . . . . . . . :   main
                                     Statement . . . . . . . . . :   108
                                     Message . . . . :   Unmonitored
exception received.
                                     Cause . . . . . :   Received an
unmonitored exception. Recovery  . . . :   See
                                       the messages listed on this display
or in the job log (use the DSPJOBLOG
                                       command to display the job log).
Correct any errors and try the command
                                       again.
CEE9901    Escape                  30   08/15/03  16:07:01.916792  QLEAWI
QSYS        *STMT    QP0ZEXEC    QSYS        *STMT
                                     From module . . . . . . . . :   QLEDEH
                                     From procedure  . . . . . . :   Q LE
leDefaultEh
                                     Statement . . . . . . . . . :   231
                                     To module . . . . . . . . . :
QP0ZEXECUT
                                     To procedure  . . . . . . . :
run__14Qp0zExecutableFv
                                     Statement . . . . . . . . . :   2166
                                     Message . . . . :   Application error.
JVAB544 unmonitored by QJVATJAVA at
                                       statement 0000000108, instruction
X'0000'.
                                     Cause . . . . . :   The application
ended abnormally because an exception
                                       occurred and was not handled.  The
name of the program to which the
                                       unhandled exception is sent is
QJVATJAVA QJVATOOLS main. The program was
                                       stopped at the high-level language
statement number(s) 0000000108 at the
                                       time the message was sent.  If more
than one statement number is shown, the
                                       program is an optimized ILE program.
Optimization does not allow a single
                                       statement number to be determined.
If *N is shown as a value, it means the
                                       real value was not available.
Recovery  . . . :   See the low level messages
                                       previously listed to locate the cause
of the exception.  Correct any errors,
                                       and then try the request again.
CEE9901    Escape                  30   08/15/03  16:07:01.917176  QLEAWI
QSYS        *STMT    QP0ZPCPN    QSYS        *STMT
                                     From module . . . . . . . . :   QLETOOL
                                     From procedure  . . . . . . :   Q LE
AWIRaise
                                     Statement . . . . . . . . . :   192
                                     To module . . . . . . . . . :
QP0ZPCPN
                                     To procedure  . . . . . . . :
InvokeTargetPgm__FP11qp0z_pcp_cb
                                     Statement . . . . . . . . . :   1998
                                                        
 5722SS1 V5R2M0 020719                           Job Log
ISDDEV04 08/15/03 16:07:02          Page    2
  Job name . . . . . . . . . . :   QP0ZSPWP        User  . . . . . . :
MURBANEK     Number . . . . . . . . . . . :   087940
  Job description  . . . . . . :   SIDEVJOBD       Library . . . . . :
QGPL
MSGID      TYPE                    SEV  DATE      TIME             FROM PGM
LIBRARY     INST     TO PGM      LIBRARY     INST
                                     Message . . . . :   Application error.
*N unmonitored by *N at statement *N,
                                       instruction X'4000'.
                                     Cause . . . . . :   The application
ended abnormally because an exception
                                       occurred and was not handled.  The
name of the program to which the
                                       unhandled exception is sent is *N *N
. The program was stopped at the
                                       high-level language statement
number(s) *N at the time the message was sent.
                                        If more than one statement number is
shown, the program is an optimized ILE
                                       program.  Optimization does not allow
a single statement number to be
                                       determined.  If *N is shown as a
value, it means the real value was not
                                       available. Recovery  . . . :   See
the low level messages previously listed
                                       to locate the cause of the exception.
Correct any errors, and then try the
                                       request again.
C2M1212    Diagnostic              30   08/15/03  16:07:01.936928  QC2UTIL1
QSYS        *STMT    QP0ZEXEC    QSYS        *STMT
                                     From module . . . . . . . . :
QC2ALLOC
                                     From procedure  . . . . . . :   free
                                     Statement . . . . . . . . . :   1036
                                     To module . . . . . . . . . :
QP0ZEXEC
                                     To procedure  . . . . . . . :
__dt__14Qp0zExecutableFv
                                     Statement . . . . . . . . . :   980
                                     Message . . . . :   The pointer
parameter passed to free or realloc is not
                                       valid.
                                     Cause . . . . . :   The pointer
parameter passed to free or realloc was not
                                       valid. This caused your function call
to fail. Recovery  . . . :   Correct
                                       the invalid pointer parameter being
passed to free or realloc. Technical
                                       description . . . . . . . . :   The
value of the pointer passed to free or
                                       realloc is
X'8000000000000000CE20881E4F018480'.
CPF24A3    Escape                  40   08/15/03  16:07:01.957680  QMHSNDPM
QSYS        0AAD     QLEAWI      QSYS        *STMT
                                     To module . . . . . . . . . :   QLEDEH
                                     To procedure  . . . . . . . :   Q LE
leDefaultEh
                                     Statement . . . . . . . . . :   231
                                     Message . . . . :   Value for call
stack counter parameter not valid.
                                     Cause . . . . . :   The value 6,
specified for call stack counter parameter,
                                       is not valid. The value was specified
in parameter number 7 on the API.
                                       Recovery  . . . :   Correct the value
for call stack counter parameter and
                                       try the request again. This value
must be greater than or equal to 0 but
                                       cannot be larger than the number of
entries on the call stack.
CEE9901    Diagnostic              30   08/15/03  16:07:01.957912  QLEAWI
QSYS        *STMT    QP0ZSPWP    QSYS        *STMT
                                     From module . . . . . . . . :   QLETOOL
                                     From procedure  . . . . . . :   Q LE
CPF24A3_handler
                                     Statement . . . . . . . . . :   706
                                     To module . . . . . . . . . :
QP0ZSPWP
                                     To procedure  . . . . . . . :
_CXX_PEP
                                     Statement . . . . . . . . . :   1465
                                     Message . . . . :   Application error.
CEE9901 unmonitored by QP0ZPCPN at
                                       statement 0000001998, instruction
X'0000'.
                                     Cause . . . . . :   The application
ended abnormally because an exception
                                       occurred and was not handled.  The
name of the program to which the
                                       unhandled exception is sent is
QP0ZPCPN QP0ZPCPN
                                       InvokeTargetPgm__FP11qp0z_pcp_cb. The
program was stopped at the high-level
                                       language statement number(s)
0000001998 at the time the message was sent.
                                       If more than one statement number is
shown, the program is an optimized ILE
                                       program.  Optimization does not allow
a single statement number to be
                                                        
 5722SS1 V5R2M0 020719                           Job Log
ISDDEV04 08/15/03 16:07:02          Page    3
  Job name . . . . . . . . . . :   QP0ZSPWP        User  . . . . . . :
MURBANEK     Number . . . . . . . . . . . :   087940
  Job description  . . . . . . :   SIDEVJOBD       Library . . . . . :
QGPL
MSGID      TYPE                    SEV  DATE      TIME             FROM PGM
LIBRARY     INST     TO PGM      LIBRARY     INST
                                       determined.  If *N is shown as a
value, it means the real value was not
                                       available. Recovery  . . . :   See
the low level messages previously listed
                                       to locate the cause of the exception.
Correct any errors, and then try the
                                       request again.
CPC1219    Completion              50   08/15/03  16:07:01.958848  QWTPITPP
QSYS        0754     *EXT                    *N
                                     Message . . . . :   This job ended
abnormally.
                                     Cause . . . . . :   An error occurred
that caused this job to end abnormally.
                                       Recovery  . . . :   See the
previously listed messages in the job log for
                                       this job.  Correct the errors and try
the request again.
CPF1164    Completion              00   08/15/03  16:07:01.967584  QWTMCEOJ
QSYS        00BD     *EXT                    *N
                                     Message . . . . :   Job
087940/MURBANEK/QP0ZSPWP ended on 08/15/03 at
                                       16:07:01; 1 seconds used; end code 30
.

------------------------------

date: Fri, 15 Aug 2003 09:44:00 -0500
from: Fred Kulack <kulack@xxxxxxxxxx>
subject: Re: environment limitations


On 08/13/2003 at 01:26:51 PM, java400-l-bounces@xxxxxxxxxxxx wrote:
Anybody know about these limits and if/how I can control them?
--- end of excerpt ---

iSeries has an environment limitation of around 16MB the environment is
extended dynamically as required up to that limit. There is no limit that I
know of
on length of individual variables and their values, the max number of
variables is 4095.

In any case, that's probably not _directly_ the issue.

Signal 5 is SIGSEGV. Its likely something else is going on that is related
to the
long environment variables than this particular environment limit.

Note that you can't tell from the error you've shown exactly _what_ in the
script fails, just that it fails with SIGSEGV.
I.e. it may be one of the other tools/utilities you're using, not a java
related
thing or directly the environment variables limit.

Usually a SIGSEGV will be accompanied by a joblog from the utility
that you started that hit it (or from the script process if Qshell hit it
on its own).
That joblog will have an MCH message (typically MCH3601 or something
similar)
in it. That message will indicate which program/module took the exception
and may
give you a better hint.
Use WRKSPLF and keep looking till you find it. Let me know what it has in
it.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.