|
Here's the text instructions w/o screenshots: 1. Use the iSeries Navigator to create a secure folder called in the iSeries Integrated File System (IFS). This folder will hold the CSV file. a. Find the Root directory in the Integrated File System. b. Right-click on the Root directory and select New Folder. c. Enter myfolder (or whatever) as the name and click the OK button. d. After the myfolder folder appears, right-click on it and select Permissions. e. Set the permissions. Permissions can be set by user or by group. A userwho does not have permission to the folder (as an individual or as part of a group) will not be able to map it to her or his PC. The attempt to map will return a message saying the user name or password is not recognized. Click the OK button. 2. Use iSeries NetServer to share the accounting file. a. Right-click on the myfolder folder and select Sharing. b. Select New Share. c. Under the Share name enter myfolder$. The $ at the end of the share name hides the folder from the network. Someone trying to map a drive will not see thefolder when browsing. You will need to enter the folder path directly (as explained below) when mapping. You can omit the $ if you don't mind the folder being visible to the network. Do not put the $ on the name of the actual folder in the IFS. d. Enter a description of the folder. e. Set the access level appropriately. f. Click the OK button. 3. Map the myfolder folder to the user PC. a. Right-click on My Computer and select Map Network Drive. b. Enter \\Qsystem\myfolder$ as the folder to share, where Qsystem is the network name of your iSeries. Remember, if you put $ on the share name, you will not be able to browse and find the folder. You need to enter the path manually. c. Log on with a valid iSeries user name and password when the log on window appears. A valid user in this case means one with permissions to the folder. By the way, if you don't want to write a CSV file to the IFS using COBOL, you might try using COBOL to create a temporary DB2 database file, then use the CL command CPYTOSTMF to write the temporary DB2 database file to an IFS stream file. If you set the ENDLINFMT parameter to *FIXED you should get a fixed width text file in the IFS. Microsoft Excel can open fixed width text files. Thanks, Kelly -----Original Message----- From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx]On Behalf Of welchj@xxxxxxxx Sent: Monday, March 08, 2004 4:32 PM To: COBOL Programming on the iSeries/AS400 Subject: RE: [COBOL400-L] Downloading from COBOL to a .csv Kelly, The Word attachment did not come through. Did anyone else get it? I don't know if attachments will go through the list. _______________________________________________ > Okay, I'm still learning this stuff myself, so I've not done this...but > it's > supposed to work from what I've read. > > You can create and share an IFS folder with any PC. You simply map the IFS > folder to a network drive on the PC. This much I know works because I've > done it. Attached is a Word document from a project design that explains > how > to share an IFS folder and map it to a network drive on a PC. > > If you use some examples from others on this list to create a COBOL > program > that reads DB2 files and writes CSV records to a stream file, then you can > have the program write the stream file to the shared/mapped IFS folder. > Users can access the CSV file from their PC just like they access any > other > file in a mapped drive. > > The iSeries job scheduler could run the COBOL program that writes the > stream > file. > > Just some ideas... > Thanks, > Kelly > > > > -----Original Message----- > From: cobol400-l-bounces+kcookson=dotfoods.com@xxxxxxxxxxxx > [mailto:cobol400-l-bounces+kcookson=dotfoods.com@xxxxxxxxxxxx]On Behalf > Of Phil Campbell > Sent: Monday, March 08, 2004 1:01 PM > To: cobol400-l@xxxxxxxxxxxx > Subject: [COBOL400-L] Downloading from COBOL to a .csv > > > > I've download files to .csv's before. I would like to > > 1) have the operator run a nightly job that executes the COBOL program > that > creates a .csv. > 2) Somehow EVOKE (might not be the write term) a job to have the data > transferred from the .csv to the common area on our host PC. > > Every Morning I come into work and use the AS400 data transfer > facility to transmit data to a user. I sure would like to get away from > having to do this. > > Thanks .. Phil :) > > Phil Campbell > Wisco Envelope > > pcampbell@xxxxxxxxxxxx > > > > _______________________________________________ > This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing > list > To post a message email: COBOL400-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/cobol400-l > or email: COBOL400-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/cobol400-l. > > _______________________________________________ > This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing > list > To post a message email: COBOL400-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/cobol400-l > or email: COBOL400-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/cobol400-l. > > _______________________________________________ This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/cobol400-l or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l.
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.