OCL PROBLEMS
PROBLEM:
When I submit my OCL, I get this message: “PCT0002 Invalid or missing parameter.”
CAUSE:
There are two steps to a transfer: the translation and the transfer itself. In OCL the parameters must be entered for each step.
SOLUTION:
Use two steps: 1) translate, and 2) then transfer using *NONE.
PROBLEM:
The company has 8 output queues that will have new data every day for the same output queue names. They want to automate as much as possible the daily transfer process.
ANSWER:
No matter what happens, the spool queue must be copied from the spool to a physical file. The ETU part is the translation from EBCDIC to ASCII and to move the file to the PC. ETU can only work with a physical file. The process of copying the spool file to a physical file use an OS/400 command called CPYSPLF. The command interface only allows for a single spool file to be copied. In general, the OS/400 spool file interface is very restrictive.
Bottom line, it does not matter what ETU command you want to use, you still have to copy the spool file to a physical file first. That is the part that is restrictive. There are ways around it but none of them are very generalized and would require programming.
Because the spool transfer functions do not generate a single command line, this is a function that would probably require two steps.
You would first use Copy prt spool file - PC/XLT: (PRTXTOPC) to perform an EBCDIC to ASCII translation. On a command line, type PRTXTOPC and press F4. Use *TRANSLATE as the Action to perform. After successfully defining the parameters and submitting the command, use F9 to retrieve the command for the batch file transfer.
Next use PWRFROM3XB to perform the actual transfer.
ETU400 User Guide 011603 |
