JOBLOG details - Problem in identifying the root cause

[pkbunu]

Hi All,

After a long gap posting some thoughts here.....

One of my job failed and I know system had ended the job. That job has been recovered and it processed well there after.

Now my problem is to identify the root cause of the problem. For this I had gone through all the programs thats related to my JOB.

CPF4028 DIAGNOSTIC 10 10/22/09 18:12:13.960736 QDBOPEN QSYS 14F6 IP023U IPWMPGM
TO MODULE . . . . . . . . . : IP023U
TO PROCEDURE . . . . . . . : IP023U
STATEMENT . . . . . . . . . : 2100000001
MESSAGE . . . . : OPEN OF MEMBER HISTORY WAS CHANGED TO SEQONLY(*NO).
CAUSE . . . . . : MEMBER HISTORY FILE IPWHJOB IN LIBRARY IPWMFIL WAS OPENED
WITH THE SEQONLY(*YES) PARAMETER SPECIFIED IN THE PROGRAM OR ON THE OVERRIDE
DATABASE FILE (OVRDBF) COMMAND. HOWEVER, THE PARAMETER HAS BEEN CHANGED TO
SEQONLY(*NO) BECAUSE OF CONDITION 1 SHOWN BELOW: 1 - THE PROGRAM OPENED
MEMBER HISTORY FOR OUTPUT OPERATIONS ONLY AND SEQONLY(*YES) WAS SPECIFIED
WITH THE DEFAULT NUMBER OF RECORDS. SEQONLY(*YES) WAS CHANGED TO
SEQONLY(*NO) TO ALLOW THE PROGRAM TO HANDLE DUPLICATE KEY, CONVERSION
MAPPING, KEY MAPPING, AND SELECT OR OMIT ERRORS, OR BOTH SELECT AND OMIT
ERRORS AT THE TIME OF THE OUTPUT OPERATION. 2 - THE PROGRAM OPENED THE


Please let me know .....how to identify the problem below

"HOWEVER, THE PARAMETER HAS BEEN CHANGED TO SEQONLY(*NO) BECAUSE OF CONDITION 1 SHOWN BELOW:".

I haven't found anything which caused a changes to SEQONLY to *NO. I require this because I am unable to retrieve the record which has caused error.

There is also the line " USER QTCP ISSUED AN IMMEDIATE END JOB REQUEST FOR JOB", which indicates that the system has ended the job.

My questions are

1) How SEQONLY changed to *NO (there are nothing mentioned in the code)
2) If QTCP ended the job, is there a way to identify the job details/logs
3) How QTCP comes to end the job
4) I have the job log which details about the error, I am sure that due to open file/file locking etc may have cause the error. If some how I can retrieve the record it would be great for analysis

Thanks all of you for your patience.........Have a nice day

[tomholden]

Re: JOBLOG details - Problem in identifying the root cause

1) - you can ignore this...it has absolutely nothing to do with your issue. if you look through job logs for other jobs you're likely to see this. (not 100% sure on this perhaps JonBoy or someone can verify or deny it's accuracy ) but when a file is opened for OUTPUT on a keyed file in the called program the SEQONLY setting will automagically be changed (same may hold true for files set to REUSEDLT records).

2) - to determine the job name, etc. it should be listed on your job log as to which QTCP job is being used to process the requests.

3) - QTCP is the default user for TCP jobs, when TCP jobs end QTCP (which actually controls all TCP services, apps, etc.) will be used to end these jobs)

4) - if a DSPJOB was executed as a part of the shut down/end job processing you can look in that spooled file for more info.

[pkbunu]

Re: JOBLOG details - Problem in identifying the root cause

Thanks a lot Tommy !!!!

This info will really help ..... Will update you if anyway I get the solution....