A SERVICE OF

logo

146 Geac System21 commerce.connect: Implementation on the iSeries Server
Another common problem can be caused by inconsistent use of users. If you run jobs, such
as JMS as QSECOFR and then later as OMUSER, you may have an authority problem. It is
likely that the log files created when QSECOFR was used cannot be overwritten by the
normal user used later.
6.1.9 Editing an iSeries stream file using the OS/400 EDTF command
In most cases, the easiest way to edit a stream file is with a PC editor on a mapped drive. The
ETDF command is useful in a few circumstances:
The file may be in a directory that is not accessible through any share.
The file may be EBCDIC.
It may simply be convenient, for example, using the WRKLNK command.
There are several ways to start EDTF. For example, one way is to enter the EDTF command
followed by the stream file name. If the name is not qualified, then the current directory is
searched. It is not common to set the current directory. Therefore, you may need to full qualify
the file name. As for most stream file commands, if the name is qualified, then you need to
add single quotation marks around it as shown here:
edtf '/OrderManagement/log/stdout.txt'
Another way is to enter the EDTF command followed by a directory name such as /. Then you
can explore the IFS in a way that is similar to the WRKLNK command. When you find the file,
type option 5 (display) or option 2 (edit). You may perform some operations on files from the
EDTF file selector. There is even an option that WRKLNK lacks, which is
recursive delete.
This deletes a directory and its contents. The delete within WRKLNK deletes only an empty
directory. Of course, you must use recursive delete with caution.
You can also find the file using the WRKLNK command and type option 5 (display) or option 2
(edit) next to it the file.
EDTF is a simple dumb terminal editor that should be familiar to anyone who has used SEU
(the dumb terminal source editor on the iSeries). There are no sequence numbers but there
is an entry field at the left of each line into which SEU like commands may be typed.
If you do not make any changes, then press F3 or F12 to exit the editor. Unlike SEU, there is
no exit screen. If you make a change, when you press either key, you see a message
indicating that the file has changed. If you press F3 again, the file is saved and you exit. If you
press F12, then the file is not saved and you exit.
As for editing files with a PC editor, ensure that it is safe and appropriate to edit them. If you
start EDTF and the file is not readable or you do not understand its contents, then be careful
to exit without saving.
To use EDTF, you should be familiar with SEU and other OS/400 commands.
6.2 The Qshell
Java and other non-traditional iSeries software often requires programming techniques that
do not fit well into traditional iSeries facilities such as its structured commands and its
command entry screen. The UNIX or Windows NT equivalent of the command entry screen is
rather different.
The DOS command screen is probably familiar to most computer users. The output of simple
commands is sent back to the command screen and when the screen is full, it automatically