RE: What is the best, most graceful way to import PC data and then runa CLP program?

We use a net.data macro.  It prompts for the file name and any
processing options, then uploads the file to the IFS, copies it to a
physical, and submits a job to process it.

It's not 'automated' in that the user must do the upload but if this is
a weekly thing that's probably OK.


John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin
Sent: Wednesday, August 23, 2006 11:49 AM
To: Midrange Systems Technical Discussion
Subject: What is the best, most graceful way to import PC data and then
runa CLP program?

What is the best, most graceful way to import PC data and then run a CLP
program?

It occurs to me that there are several ways to do this, and a discussion
might prove educational and fun.

The person runs a PC program, creating a PC file.  This file must go to
the iSeries once a week, and then be processed by a CLP program/

Ideas? Suggestions?  Fantastic solutions?




--
-----------------------------
Booth Martin
www.martinvt.com
-----------------------------
--
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 email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in future then please respond to the sender to this effect.