× 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.



On V5R2, his job description for compiles was probably different and had
the file in question in a "regular" library. I never, ever create a file
in QTEMP to compile a program. It should exist in a library. If the file
needs to be in QTEMP when the program is run, I do a CRTDUPOBJ of that
file to QTEMP. 

Francis Lapeyre
IS Dept. Programmer/Analyst
Stewart Enterprises, Inc.
E-mail: flapeyre@xxxxxxxx 

-----Original Message-----
From: midrange-l-bounces+flapeyre=stei.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+flapeyre=stei.com@xxxxxxxxxxxx] On Behalf Of
Ketzes, Larry
Sent: Thursday, September 14, 2006 9:41 AM
To: Midrange Systems Technical Discussion
Subject: V5R3 Quirk!

Hi folks!  I recently upgraded a partition from V5R2 to V5R3 and a
developer
noticed the following problem.  I was wondering if anyone else might
know
anything about this.

1) He displays a file to qtemp.
2) Qtemp is in his library list.
3) He tries to compile a cl program that references the file in qtemp.

When he does the compile interactively, he is fine.
When he compiles to batch, the compile fails because the file is not
found!

He tells me this never happened in the previous release!

Larry

======================

Larry Ketzes
iSeries Senior System Administrator
American Life Insurance Company

One ALICO Plaza
600 King Street
Wilmington, DE 19801
Phone: 302-594-2146
Mobile: 302-559-1631

Fax: 302-830-4524


Email: larry.ketzes@xxxxxxx

 


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.