|
The files we use normally don't have negatives but CPYTOIMPF does preserve the negative numbers in the output file. I assume that the product on the other end should be able to read these negative numbers fine, especially in the delimited output. The fixed output can be a little harder to interpret because the sign only show up on negatives and shifts the digits to the right. If you are writing the program to read the text file then you will have to look for the negatives. > -----Original Message----- > From: Roger Boucher [SMTP:RBoucher@stanpac.com] > Sent: Wednesday, October 20, 1999 2:36 PM > To: 'MIDRANGE-L@midrange.com' > Subject: RE: Solicitation for product recommendations > > Appreciate the reply (and also the others I got from a couple vendors who > I > will be contacting). I had a question for you on the CPYTOIMPF file > command. How do you deal with negative numbers? > > Thanks again! > > > -----Original Message----- > From: Scott Mildenberger [mailto:Smildenber@Washcorp.com] > Sent: Tuesday, October 19, 1999 11:31 AM > To: 'MIDRANGE-L@midrange.com' > Subject: RE: Solicitation for product recommendations > > > Some suggestions, you could use CPYTOIMPF to extract the data and put it > into a "flat" database file. This command has the ability to create a > fixed > record format or a delimited file(you can even specify the delimiters). > Then you could ftp this flat file to wherever you want it on the network. > As far as automating and being able to see if there were errors, we use a > scheduling product called Pilot from ASC that we really like. You can > schedule a job any way you can imagine. It can even do different things > depending on if a job ends normally or abnormally. For example, we have > and > EDI job that normally runs every 30 minutes but if it gets an abnormal end > then it runs again in 5 minutes. Every morning we just have to look in > Pilot to see how all the automated jobs ran, we even created an auto-purge > of the Pilot log so that the only jobs that show up are those that ended > abnormally. > > HTH > > Scott Mildenberger > > > -----Original Message----- > > From: Roger Boucher [SMTP:RBoucher@stanpac.com] > > Sent: Tuesday, October 19, 1999 10:42 AM > > To: 'MIDRANGE-L@midrange.com' > > Subject: Solicitation for product recommendations > > > > We are a very small shop, but with our foot to the pedal <g>. We now > have > > three different applications for which we extract data from the AS/400 > and > > send it to the NT network (and probably more to follow). We are looking > > for > > recommendations for a product that will allow us to automate and MANAGE > > the > > transfer of these extract files to the network. > > > > All three of these processes have the common thread that they need to > have > > their extracted data sent from physical files on the AS/400 to the > network > > when the extracts have completed running (submitted jobs running in > > batch). > > > > Requirements: > > 1) It MUST be able to handle zoned negative numbers (like Client > Access). > > > > (Hopeful) Requirements: > > 2) Data transfers can be initiated from a batch job running on the > AS/400. > > 3) We don't have to pay attention to it because it runs by itself > without > > errors. > > > > Wishful thinking > > 4) If errors do occur I only have to look one place to see what the > errors > > were. > > > > > > We are willing to spend a little on this one. > > Are there any such products out there? > > > > NOTE: We will also consider (with a bias) products that run on the > network > > and grab data from the AS/400 if they make sense for us. > > +--- > > | This is the Midrange System Mailing List! > > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > > | To unsubscribe from this list send email to > > MIDRANGE-L-UNSUB@midrange.com. > > | Questions should be directed to the list owner/operator: > > david@midrange.com > > +--- > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.