|
If you're able to get it to hold still long enough, try starting a service job for the job and starting debug on CVCM002. If the right compile options were used you might then be able to view the code as it executes (use <shift><F10>) and see what it's trying to delete, then do a wrkobjlck on the victim and see what has it locked and from that determine the conflict and see if there's a way to work around it by scheduling when things run. -----Original Message----- From: Simon Coulter [mailto:shc@flybynight.com.au] Sent: Friday, April 27, 2001 7:04 PM To: MIDRANGE-L@midrange.com Subject: Re: QCMDEXC Ð Hello Jeff, You wrote: > CVCM002 CVTILERPG 0000013500 > QLIDLOBJ QSYS 02A5 > QDBDLTFI QSYS 000C > QCMDEXC QSYS 0105 > QWCDLYJB QSYS 0030 CVCM002 CVTILERPG USER - ILE CL program QLIDLOBJ QSYS IBM - Librarian - Delete Object (CPP for the majority of DLTxxx commands) QDBDLTFI QSYS IBM - Database - Delete File QCMDEXC QSYS IBM - Command execution QWCDLYJB QSYS IBM - Work Management - CPP for DLYJOB An ILE CL program is issuing some form of delete command. The generic delete object program is invoking a specific object deletion handler which is then waiting for a resource to become available. It is probably using DLYJOB to avoid a LCKW timeout. If the CLLE program is one of yours then examine the code at line 13500 to see what file is being deleted. That may give you a clue as to why the resource is not available. Given that the library of the program invoking the delete function is called CVTILERPG I wonder if this is someone's poxy RPG IV conversion program doing stupid things? Regards, Simon Coulter. «»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«» «» FlyByNight Software AS/400 Technical Specialists «» «» Eclipse the competition - run your business on an IBM AS/400. «» «» «» «» Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ «» «» Fax: +61 3 9419 0175 mailto: shc@flybynight.com.au \ / «» «» X «» «» ASCII Ribbon campaign against HTML E-Mail / \ «» «»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«» +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.