![]() Then on your desktop right click and select paste.Copy the file by clicking on it, then right click and select Copy.You can double click on the file to view it in the AFP workbench (if that module was installed on your PC) You should see the file that you created in the previous steps at the bottom of the list.Then click on the + sign next to Basic Operations and click on the words Printer Output.Click on the + sign next to the system that you were signed in to, to print the file.You should see a list of AS/400 servers.At this point in the procedure we change programs.You can use option 5, here to view the print file. Generally, you will find the file you just created at the bottom of the list. If it is not apparent which one of the files is the one you just created, use the F11 key a couple of times to see different views of the print files. You may need to use the PAGE DOWN key to scroll to the bottom of the list of printer files, or you can use F18 to go to the bottom. Optionally, at this point you can view the file using the command WRKSPLF which shows all of your printer files.After the command completes, a message will show below the command line telling you how many lines were output to a print file *ALL will output multiple file members if there are more than one. The From member is either the name of the BSFN, N5642003, or you can use *ALL if you want. Using the example above, the From File is FAILED, the From File’s Library is the package name We are going to output to a print file – in other words, we will create a file that could be printed on a printer instead of exported.On the command line type ‘CPYF’ and then press the F4 key to view of the parameters for the command.Sign onto a Client Access 5250 emulation session.This method is specifically for finding the compile log and producing it for the developer. The quick and easy way to transfer files to a PC is drag and drop Within this one file will be multiple members, each member having the name of the BSFN or NER that failed.įor example: If a package is named DVU200514A and the BSFN that failed is named N5642003, then the compile log will be output to a file named FAILED in library DVU200514A, with member name N5642003. On the AS/400 a table can have multiple members, so if a package fails, the different BSFN’s and NER’s that fail will have their output directed to one physical file, called FAILED, in a library named the same as the package name. The compile log is created in an AS/400 physical file (or table in SQL terms). Sometimes PC security is setup to thwart you from sharing data between computers, so it is helpful to know various methods. I am outlining two possible ways to accomplish this. When a package fails, the CNC is often asked to produce the compile log for the developer. Engineering, Construction and Operations. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |