Re: Job hangs after processing 220 records.

Hi Marie,

The read is most likely not the problem.

The problem will be on one of ..

SQL_Deletes_ from a table
SQL_Deletes_ from a second table
SQL_Inserts_ to a file
SQL_Inserts_ into a second file

The problem could be a record lock, or something to do with a logical or a trigger or a constraint.
I would copy the 220th and the 221st record to a temporary input file and run in debug mode.
Knowing the particular record means you can investigate related records in the related files.
Of course, depending on how it is coded, the program might be going into a loop on that particular record ...

Regards,
John McKay mba


On 01/07/2014 17:45, Marie O'Rourke 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