×
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.
Hi Luis
First of all - no apology necessary. I understand that people have their own things to do. I'm just glad that whenever I post a question on this list, people are gracious enough to take the time to answer.
Your explanation now makes sense.
I saw that V6r1 did in fact have what I need.
Now here comes the twist.
Since yesterday I have discovered that these files (in what I consider to be the wrong library) may have been put there years ago (for whatever reason) and they should in fact NOT be in that library.
I am hoping that this is the case. The file format definitely looks to be from years ago. If so I am going to delete them, but only if they can be.
Will let you know the outcome
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: Thursday, November 08, 2012 9:12 AM
To: Midrange Systems Technical Discussion
Subject: Re: EXTNAME not picking up the correct file
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:
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.