|
Dave Mahadevan wrote: >Cant wait for it :-)) Really I am eager to see it...please can you just >e-mail me that document (I have Word and MS Pub). Thanks very >mucho. As the original poster to Midrange-l mentioned, they had the overlay function working correctly prior to CA for Win 95. We had created a document which showed step by step how to make this procedure work in Win 3.1. The reason I will be posting the CA95 document next week is because I am currently editing our old document to include new pictures and steps required by CA95. To accomodate the need for immediate information, I have included the steps to follow as plain text which is appended below: Steps to be Performed on the Windows 95 PC ------------------------------------------ Chapter 1 - Working on the Win 95 PC ------------------------------------ Our successful test was performed using Client Access for Windows 95 V3R1M2. The service pak that provides the VxD to drive an IBM 2 session twinax card has also been applied to our test machine. 1. Verify that when Client Access for Windows 95 was installed on your PC, the SCS and AFP print drivers (an optional component) were installed as well. If not, follow instructions to add these components to your Windows 95 PC. *NOTE* - Be aware that if you had previously installed the print drivers and then upgraded the Client Access for Windows 95 software with a service pak, the service pak writes its controlling information into the Win 95 registry. This may cause the link between the Win 95 registry and the source files for all of the IBM AFP print drivers to be broken. If this happens you need to selectively uninstall the AFP Print Driver component and then reinstall it. 2. If you already have an AFP print driver installed in Windows 95, choose the Windows 95 START button, choose settings, choose printers, and then highlight your AFP print driver. Click the Right mouse button and then choose properties. Click on the details tab. Under the field "Print to the following port:" you will probably see a path that looks something like \\S10055DA\prt010306. Click the arrow next to this field to see the other choices. Highlight the value FILE: and press enter. Next click on the Setup.. button. From this new menu click the Options button. Under the field output type there will be four choices listed: Document, Medium Overlay, Overlay, and Page Segment. Choose the type of object you would like to create. In our test, we chose Overlay. Click on OK to return to the setup menu. Choose OK to return to the Details menu. Choose Apply and then OK to close the Properties Menu. *NOTE* If you have not installed an AFP print driver, the IBM documentation tells you to select Network Printer when using the Win 95 Add Printer function. If you only want to create Page Segments and Overlays with the driver and never connect to your AS/400, you should choose local when prompted. *NOTE* IBM offers a number of Win 95 AFP print drivers. The drivers can work at three different resolutions (DPI means dots per inch). In the past there was a default AFP driver that created output at 144 DPI. This driver is for IPDS impact printers like 4224, 4230, 4234, 4247, and 64xx. I didn't look to see if this driver is still available in Client Access for Windows 95 or not. The next set of AFP print drivers create output at 240 DPI. The individual drivers will be for IBM 3812, 3816, 3820, 3825, 3827, 3828, 3835, 3800, 3900, and 3930 printers. The last set of AFP print drivers create output at 300 DPI. The individual drivers will be for IBM 4028, 3912, 3916, 3112, 3116, 3130, 3160, and 43xx (Network Printer Family) printers. For our test, we used the AFP IBM 4028 print driver. If you have properly configured the driver, you will see a small arrow and diskette icon in front of the picture of the printer in the Windows 95 Printers dialog box. This means that all output will be written to disk as individual files. You can now open your PC application and print the document that you want to become an overlay or page segment. Choose the IBM AFP print driver that you have previously configured as the target. A small dialog box will appear asking you to choose a name for the file you are going to print. Enter the name and choose the destination path as well when necessary. The file will now be copied to your PC's hard drive. You have now successfully created an Overlay or Page Segment source file on your PC. This is the end of chapter 1 in creating overlays and page segments from PC documents. Chapter 2 - Transferring the File to the AS/400 ----------------------------------------------- The file must be maintained in its PC format (ASCII) during the transfer to the AS/400. For our test, we used Windows 95 explorer. We mapped a network drive to the AS/400 and then transferred the test file from the Windows 95 PC hard drive to an AS/400 folder by dragging and dropping. Any file transfer method that maintains the file format that existed on the PC should work for this step. Make sure that you copy the files to a folder on the AS/400 that your User ID has access to when you are running a display session on the AS/400. This is the end of Chapter 2. --------------------------------------------------------- Chapter 3 - Converting the PC Document into an Overlay or Page Segment on the AS/400 --------------------------------------------------------- The steps that must be performed on the AS/400 are to copy the PC document into a source physical file and then to run an OS-400 conversion routine against the source physical file to create the overlay or page segment. The steps are as follows: 1. Create a source physical file. The CL command is CRTSRCPF. If you press F4 to get a prompt you will be asked for a file name, library, Record length, Member 'if desired', and Text description. If you are going to be creating a number of overlays or page segments, you can create a source physical file for each one or you can make each overlay or page segment a member that is part of a global file like "W95PCOVR". Both methods worked for us. In our test, we used the system supplied (V3R2) default record length which was 92. When you have entered all of your information, press enter to create the file. 2.Now you have to execute the Copy From PC Document Command. The CL command is CPYFRMPCD. You can press F4 to get a prompt. a) Enter the folder name where your PC document resides in the "From folder" field. b) Enter Source Physical File Name in the "To file" field. The source physical file is the target where the PC document is to be copied. c) Enter PC Document Name in the "From document" field. This is the file that you transferred from your Win 95 PC to the AS/400 in Chapter 2. d) The settings for fields "To Member" and "Replace or add records" depend on whether you are using members and whether you have used the target source file previously.The defaults *FIRST and *REPLACE work fine when you are putting only one PC document into the source physical file. e) The field "Translate Table" must be changed from *DFT to *NONE. This is a very *important* change. f) The field "Format of PC Data" must be changed from *TEXT to *NOTEXT. This change is also very *important*. You can now press enter to perform the copy of your PC document into the source physical file you built in step one. 3. If your PC document included overlay data, you will need to execute the CL command CRTOVL to turn the data stored in the source physical file into an Overlay. If your PC document included page segment data, you will need to execute the CL command CRTPAGSEG to turn the data stored in the source physical file into a Page Segment. When you execute either command and press F4 to get a prompt; you will find that the command wants the name of the overlay or page segment to be created, the library the overlay or page segment should be placed in, as well as the name, library name, and member name (if applicable), for the source physical file that you created. After you have entered this information, you can press enter. An informational message should appear at the bottom of your screen telling you that the overlay or page segment has been created. Please contact me if you have questions about any of this information. /Paul -- Paul Tykodi, Technical Director E-mail: pault@praim.com Praim Inc. Tel: 603-431-0606 140 Congress St., #2 Fax: 603-436-6432 Portsmouth, NH 03801-4019 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the Midrange System Mailing List! To submit a new message, * * send your mail to "MIDRANGE-L@midrange.com". To unsubscribe from * * this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe MIDRANGE-L' in the body of your message. 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-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.
midrange.com
