Nlynx ETU400 - Manual (Page 260)

ETU400 User Guide 011603 E-22
PROBLEM:
I am using ES32 macro commands to do transfers and I get this error message: “USR9988 "ETU
encountered information not identified as part of the ETU process".
CAUSE:
If a transfer has started, and more data comes in, this message will occur.
SOLUTION:
Put a delay between file calls, to make sure ETU finishes it's processes before another file is called.
PROBLEM:
How can I change the ETU utility to copy items to my C: drive instead of my A: drive?
CAUSE:
You must doing your ETU file transfers using a CL script. Otherwise when the menu selection for
"Qualified file name": comes up, you would see that this is where to change from A:\ to C:\.
SOLUTION:
You will need to find the CL script and modify it. The line that needs to change will look similar to
this: FROM3XB FRMFILE(GEORGE) QFNAME1('a:\george.txt') and you must change it to
('C:\george.txt')
PROBLEM:
When I try to do a transfer, I get a message after the EMULATOR CHECK that says, "USR3255
return from native code processor".
CAUSE:
This is often the same error as USR9987, but occurs when command is called from a CL script.
Technically it means "Select/Omit statement has too many parameters".
SOLUTION:
If you have our ES32 emulation, make certain that ETU is enabled.
• Select the Session menu, then Properties.
• Select the API tab.
• Make certain there is a check in Enable ETU.
• Also make certain that the CL script is called by the PC that is running our emulation.