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



No, they are not loosing theirs which makes me think somehow there is
data in the file when I do the CRTDUPOBJ. But I am also always
clearing the file to make sure it it empty. I think this data area
will help drastically.


On Mon, 13 Sep 2004 11:35:53 -0500, rick.chevalier@xxxxxxxxxxxxxxx
<rick.chevalier@xxxxxxxxxxxxxxx> wrote:
> <snip>
> However,
> once in a blue moon, somehow a person gets other people's POs that
> they are printing.
> </snip>
> 
> If they get someone else's what happens to their PO?  Are you losing PO's 
> (having to request the print option again)?  If so, I think it may be a 
> timing issue with assigning the members in your work file.  Before the first 
> job locks the member to your system a second job comes along and acquires the 
> same member name.  The last PO number written is the one that prints.
> 
> Rick
> 
> 
> 
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Mike Wills
> Sent: Monday, September 13, 2004 10:20 AM
> To: Midrange_RPG400_L
> Subject: Seeking adivce
> 
> I am looking for adivce on a better way to do a program. What I have
> is a vendor application that prints a PO. We didn't like that PO and
> because of how complicated it was, I just wrote a new program to print
> the PO how we wanted it. This vendor program had a work file that put
> the PO number and some information like that into it. I made a copy of
> that file and renamed it and put the exact same information into my
> file (the vendor code puts the information into a new member in the
> file then deletes the memeber when it is done processing) so it
> doesn't get deleted. I did some fancy footwork to put my file in QTEMP
> so that more than one person can use this program at once. However,
> once in a blue moon, somehow a person gets other people's POs that
> they are printing. We have never been able to duplicate that.
> 
> My question is this, is this the best way? Is there a better way? All
> I truely care about getting is the PO number(s) that they are printing
> so I can pass this information to my program (there could be 1 or
> there could be 1000 or more, in theory). I am basically looking for
> some ideas on how to make this better so we don't have this problem I
> described above.
> 
> --
> Mike Wills
> iSeries Programmer/Lawson Administrator
> koldark@xxxxxxxxx
> http://www.koldark.net
> Want Gmail? Email koldark+gmail@xxxxxxxxx to get on my waiting list.
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
> 
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
> 
> 



-- 
Mike Wills
iSeries Programmer/Lawson Administrator
koldark@xxxxxxxxx
http://www.koldark.net
Want Gmail? Email koldark+gmail@xxxxxxxxx to get on my waiting list.

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.