|
Instead of a put to LIBRARY/FILE, have your Unix folks do this: quote site na 1 (puts it into namefmt 1 mode) put unixfile /somedir/somefile (now it's a stream file in the IFS!) > -------- Original Message -------- > Subject: RE: Maximum Record Length of PF!! > From: "Chaudhary, Sachin (GE Equipment Services, Consultant)" > <sachin.chaudhary@xxxxxx> > Date: Tue, March 15, 2005 2:24 pm > To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> > > Thanks Michael, but how do we do that? > I know its a dumb question but never worked on Stream File! > Our UNIX team get the data from AAR server, and then FTP to AS400 server, the > datafile which gets created on AS400 defaults to a PF! I verified on UNIX the > record length is indeed > 32766. > > Rgds, > Sachin > > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of > michael@xxxxxxxxxxxxxxxxxx > Sent: Tuesday, March 15, 2005 12:19 PM > To: Midrange Systems Technical Discussion > Subject: RE: Maximum Record Length of PF!! > > > Sounds like a good candidate for a stream file. FTP it to a stream file, > then copy the stream data to a physical file. This AAR place must have > longer than 32766 record length on their files? > > > -------- Original Message -------- > > Subject: Maximum Record Length of PF!! > > From: "Chaudhary, Sachin (GE Equipment Services, Consultant)" > > <sachin.chaudhary@xxxxxx> > > Date: Tue, March 15, 2005 1:06 pm > > To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> > > > > Hi > > > > We receive critical data from AAR every 30 minutes and the problem started > > occurring recently, when the files FTPed to AS400 started exceeding max > > record length of 32766 characters. I am loosing data though it is not very > > often, however a cause of major concern due to criticality and large volume > > of data involved, making it very difficult to recover. > > Should we go for stream file...Can somebody help? > > > > Rgds, > > Sachin > > > > -- > > 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. > > > -- > 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 mailing list archive is Copyright 1997-2025 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.