|
Brad McDaniel wrote: >Does anyone know how to copy a SPLF type *AFPDS to a physical file without >losing any of the AFP attributes? I've seen many questions about this in >the archives, but can't seem to find an answer (an answer I like, anyway :)) >I have been using SNDTCPSPLF, but we are having problems at the remote site >directing where each SPLF should go. My thought was to copy the splf's to a >PF, and then FTP the file. That way we can put it wherever we like. (i.e. >/user/spool/annuity/etc...). This works with regular splf's, but not AFP >splf's. >Any suggestions?!?! I'm stuck. >Brad McDaniel >Information Services >Annuity Board, SBC >(214) 720-6546 Dear Brad, IBM ships a service tool that provides this type of capability. It allows you to capture an *AFPDS or *IPDS spool file to a library and physical file. The library can be placed into a savefile and then sent via binary FTP to a remote server for archival or to a different AS/400 for unpacking and printing. If the file is going to be restored on another AS/400, you may need to specify the target release value when making the savefile to insure compatibility between the OS/400 levels on the two machines if they are different. In my experience the tool is quite reliable but very syntax unfriendly. A missing space or single quote causes an error message to be displayed and the copying from or to a file is cancelled. The instructions to use the tool are listed below. The following information is from IBM Documentation and is copyright IBM. Item CGJLN Document ID Q631200 TITLE: 930527 WHAT IS THE PROCEDURE TO DUMP A SPOOLED FILE? A: If you have been asked by IBM Service to dump a spooled file, the following defines the temporary call interface to the QSPGETF and QSPPUTF system programs. Authority to these system programs is *PUBLIC *EXCLUDE. System program QSPGETF has the following five parameters. All character parameters must be entered in uppercase and be enclosed in quotation marks. The data base file and member will be created if they do not exist prior to the call. 10 character spooled file name 20 character qualified data base file name to dump the spooled file to. The first 10 characters contain the data base file name. The second 10 characters contain the data base file library name. 26 character qualified job name of the job that created the spooled file. The first 10 characters contain the job name. The second 10 characters contain the job user. The last 6 characters contain the job number. Numeric spooled file number, 1 through 9999. If using the call interface, specify the spooled file number as a hex value as follows: X’0001’ to X’270F ’ for spooled file numbers of 1 through 9999. 10 character data base file member name to dump the spooled file to. Below is an example that dumped spooled file, QPRINT, to database file, SPOOLDB, and member, MBR1. The spooled file number was 1. You can enter the information on the command line or prompt on the call command to enter the parameters. CALL PGM(QSYS/QSPGETF) PARM(‘QPRINT ‘’SPOOLDB USER1LIB ‘’DSP03 USER1 010160’ X’0001’ ‘MBR1 ‘) System program QSPPUTF has the following three parameters. All character parameters must be entered in uppercase and be enclosed in quotation marks. 20 character qualified data base file name to re-spool the spooled file from. The first 10 characters contain the data base file name. The second 10 characters contain the data base file library name. 20 character qualified output queue name to re-spool the spooled file to. The first 10 characters contain the output queue name. The second 10 characters contain the output queue library name. 10 character data base file member name to re-spool the spooled file from. Below is an example that re-spooled a previously dumped spooled file from database file, SPOOLDB, and member, MBR1, to output queue, USER1. You can enter the information on the command line or prompt on the call command to enter the parameters. CALL PGM(QSYS/QSPPUTF) PARM(‘SPOOLDB USER1LIB ‘ ‘USER1 QGPL ‘MBR1 ‘) HTH, /Paul Paul Tykodi Director of Technical Services LCI-Intermate US, Inc. p: 603.431.0606 x115 f: 603.436.6432 paul@intermate-us.com www.intermate.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.