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


  1.  Home
  2. MIDRANGE-L
  3. November 2012

RE: EXTNAME not picking up the correct file

LOL

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Thursday, November 08, 2012 8:17 AM
To: Midrange Systems Technical Discussion
Subject: Re: EXTNAME not picking up the correct file

You must be an IT professional (like me) because most parents would "pick
up" their daughter at school, not "retrieve" her.

:)

Sorry, I just couldn't resist.



On Thu, Nov 8, 2012 at 9:12 AM, Luis Rodriguez <luisro58@xxxxxxxxx> wrote:

Alan,

As I see it, your problem is that, being on V5R4, you can't use a
EXTNAME(mylib/myfile) keyword, so when I suggested the idea of including a
F-spec, I was thinking about doing the following steps:

1) Include a F-Spec (input only/user open) indicating
EXTFILE(mylib/myfile). That way you can have the file format you need.

2) Create two (2) data structures (before and after), using the LIKEREC
keyword in your DS. Something like:

DRecBefore DS Likerec(FileFormat)
DRecAfter DS Likerec(FileFormat)

My apologies for my prior post being so terse (short?), as I was leaving
my
office in a hurry in order to retrieve my daughter at the school.

Best Regards,


Luis Rodriguez
IBM Certified Systems Expert - eServer i5 iSeries
--




On Wed, Nov 7, 2012 at 5:11 PM, Alan Shore <ashore@xxxxxxxx> wrote:

Thanks for your e-mail Luis
The extname is on a data structure that will hold the before and/or
after
image of the record when a change is applied to the record.
There is no f-spec for this particular file

Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Luis Rodriguez
Sent: Wednesday, November 07, 2012 3:56 PM
To: Midrange Systems Technical Discussion
Subject: Re: EXTNAME not picking up the correct file

Alan,

The option you want (libname/filename) was made available only (AFAIK)
beginning with V6R1... :-(

Why don't you define your file with a f-spec, using USROPN?

Regards,

Luis Rodriguez
IBM Certified Systems Expert - eServer i5 iSeries
--




On Wed, Nov 7, 2012 at 4:08 PM, Alan Shore <ashore@xxxxxxxx> wrote:

Hi everyone
Before I forget, we are on V5r4.
I am writing a trigger program and placing the before/after data of
the file record like the following code:-

d data_Ordhdrp e ds extname(ORDHDRP)
d
based(dataPtr)
d qualified

The problem that I am having is that when the program is promoted to
QA, the compile is using the record layout of the file that resides in
a different library (which is a different layout (of course) than the
file I must use.
This is due to the library list (which I have been told I CANNOT
change)

My question is:-
Is there a way for the COMPILE to pick up the correct file I know that
this is available for files in the f-spec by using the following
f EXTFILE(*EXTDESC)
f EXTDESC('MYLIB/MYFILE5')

I realize that I will probably need to provide an OVRDBF for the
compile in the promotion, but that would mean adding comments to the
program and hoping that the next person reads those comments

As always, any and all suggestions ALWAYS welcome

Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill


Disclaimer: This message contains confidential information and is
intended only for the individual named. If you are not the named
addressee you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system. E-mail
transmission cannot be guaranteed to be secure or error-free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses.
The sender therefore does not accept liability for any errors or
omissions in the contents of this message, which arise as a result of
e-mail transmission. If verification is required please request a
hard-copy version. Any views or opinions presented are solely those of
the author and do not necessarily represent those of the company.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.


Disclaimer: This message contains confidential information and is
intended
only for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please notify
the
sender immediately by e-mail if you have received this e-mail by mistake
and delete this e-mail from your system. E-mail transmission cannot be
guaranteed to be secure or error-free as information could be
intercepted,
corrupted, lost, destroyed, arrive late or incomplete, or contain
viruses.
The sender therefore does not accept liability for any errors or
omissions
in the contents of this message, which arise as a result of e-mail
transmission. If verification is required please request a hard-copy
version. Any views or opinions presented are solely those of the author
and
do not necessarily represent those of the company.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
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.