RE: Job hangs after processing 220 records.

["Monnier, Gary" <Gary.Monnier@xxxxxxxxx>]

It works when you submit with JOBD set to, I assume, *USRPRF but not when you specify QGPL/CQAJOBD?  Sounds like a library list issue to me.  How does your interactive job's setup vary from what you submit using QGPL/CQAJOBD?  Do the library lists in each match?

Gary

On Tue, Jul 1, 2014 at 12:45 PM, Marie O'Rourke < Marie.O'Rourke@xxxxxxxxxxxxxxxxxxx> wrote:

> Hi
>
> I'm wondering if anyone could help.
>
> If I submit the following job using the Job Description the job hangs 
> after processing 220 records.
> SBMJOB CMD(CALL PGM(HQDOBJ/UMR_UPDATE)) JOB(PCODUMRUPQ) 
> JOBD(QGPL/CQAJOBD)
> INLLIBL(*JOBD)
>
> However if I manually set the library list and submit the job then the 
> job completes without hanging.
> SBMJOB CMD(CALL PGM(HQDOBJ/UMR_UPDATE)) JOB(PCODUMRUPQ)
>
> This looks like a problem with the Job Description , but I don't have 
> the slightest idea what to look for. The library list on the Job 
> description is correct, but I don't understand all the other details.
>
> This SQLRPGLE program does the following SQL Deletes from a table SQL 
> Deletes from a second table Reads a file and for every entry on that 
> file
>                 SQL Inserts to a file
>                 SQL Selects details to work variables
>                 SQL Inserts into a second file using details from file 
> Read and work variables.
>
>
> Some of the errors visible on the Job log (This happens regardless of 
> the way the job is submitted)
> MCH3603    Escape                  40   30/06/14  12:31:55.669663
>  #cfochkr                 000C2C   QSQSBAS     QSYS        *STMT
>                                      To module . . . . . . . . . :
> QSQHDCLS
>                                      To procedure  . . . . . . . :
> SQHRDCLS
>                                      Statement . . . . . . . . . :   4007
>                                      Message . . . . :   Pointer addresses
> object type not valid for this
>                                        operation.
>                                      Cause . . . . . :   Pointer is
> X'000000000000000004817F77B1000200'.
> MCH3603    Escape                  40   30/06/14  12:31:55.676036  QSQSBAS
>      QSYS        *STMT    QSQRUN3     QSYS        *STMT
>                                      From module . . . . . . . . :
> QSQHDCLS
>                                      From procedure  . . . . . . :
> SQHRDCLS
>                                      Statement . . . . . . . . . :   4546
>                                      To module . . . . . . . . . :
> QSQOPEN
>                                      To procedure  . . . . . . . :
> CKLNGNAM
>                                      Statement . . . . . . . . . :   35571
>                                      Message . . . . :   Pointer addresses
> object type not valid for this
>                                        operation.
>                                      Cause . . . . . :   Pointer is
> X'000000000000000004817F77B1000200'.
> SQL0901    Diagnostic              50   30/06/14  12:32:09.839561  QSQRUN3
>      QSYS        *STMT    QSQRUN3     QSYS        *STMT
>                                      From module . . . . . . . . :   QSQINS
>                                      From procedure  . . . . . . :
> CLEANUP
>                                      Statement . . . . . . . . . :   31437
>                                      To module . . . . . . . . . :   QSQINS
>                                      To procedure  . . . . . . . :
> CLEANUP
>                                      Statement . . . . . . . . . :   31437
>                                      Message . . . . :   SQL system error.
>                                      Cause . . . . . :   An SQL system
> error has occurred.  The current SQL
>                                        statement cannot be completed 
> successfully.  The error will not prevent
>                                        other SQL statements from being 
> processed. Previous messages may indicate
>                                        that there is a problem with 
> the SQL statement and SQL did not correctly
>                                        diagnose the error. The 
> previous message identifier was MCH3603. Internal
>                                        error type 3109 has occurred. 
> If precompiling, processing will not continue
>                                        beyond this statement. Recovery  .
> . . :   See the previous messages to
>                                         determine if there is a 
> problem with the SQL statement. To view the
>                                         messages, use the DSPJOBLOG 
> command if running interactively, or the WRKJOB
>                                         command to view the output of 
> a precompile.  An application program
>                                         receiving this return code may 
> attempt further SQL statements.  Correct any
>                                         errors and try the request again.
>
>
>
> Thanks
>
> Marie O'Rourke
> Applications Developer
> IT Dept
> Liberty Insurance
> mailto:marie.orourke@xxxxxxxxxxxxxxxxxxx
>
> --
> This is the RPG programming on the IBM i (AS/400 and iSeries) 
> (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a 
> moment to review the archives at http://archive.midrange.com/rpg400-l.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.