Click here for TSG sponsor message | |||||
Hidden Value details commands and
procedures in MPE that can improve
your productivity with HP 3000 systems. Get
a free NewsWire HP
3000 Always Online cap submit your
MPE tip directly to us here
at the NewsWire. Send your tips to
editor@3000newswire.com, or
fax them to 512.331.3807. The second issue is: how are you going
to log on to your 3000?
If your 3000 supports inbound telnet, you
can just telnet to him
and do whatever you want. If, however, you
want to use the 3000s
NS/VT capability to do logins (which is how
its been done prior
to being able to do telnet), then you will
need to either purchase
vt3k from HP, or pick up
freevt3k, which is a freeware mimic
of vt3k. (Sadly, HP dropped all support for
DSCOPY, which is the
NS equivalent of FTP but thats
another topic.) vt3k isnt on every HP 9000. It
used to be part of a add-on product
(some networking product.), and I
dont know if its been bundled
with HP-UX in recent versions or not.
Another option is freevt3k,
at the Telamon web site. It combines a vt3k and
hpterm emulator, and comes with
source code. A program that knows how to specify a
priv_level via HPFOPEN will
suffice... the PRINTSPF utility, in
PUB.SYS, should work. (You
may need to be SM to run this example): The command The structure of an UDC file is easy: UDC_command [parms] Remember, UDCs are always loaded into
the memory! Since MPE/iX
was released, it is better to set a path to
a common used area
of useful command files instead of having
UDCs. Such an entry
in a system-wide UDCs (probably the only
one) could look like:
As an example, T filename could invoke
TDP to edit the file filename.
S could show you all sessions, because
S.XECMD.SYS looks like
SHOWJOB JOB=@S and so on. Create the UDC file (use HPEDIT or editor) containing the commands you want. Use the Hint: The The append parameter in the command will add it to the list of existing UDCs. If now want to edit a UDC file
(myudc.pub.sys) which has already
been set, first delete this UDC (you cannot
edit myudc.pub.sys
as long as it is set) with the command
You can go through MPEs help on
setcatalog and showcatalog
to have better understanding of the various
parameters associated
with these commands. If this is going to be an ongoing production procedure, then a 3000 command file could be written that would input the fixed length file and output a comma delimited file. Note that the complexity of either the command file or other procedure increases with the number of fields. Using the fixed length field as input, you would have to assign a variable to the input line and use the STR function to break up the input line and build the output-line (another variable), appending a comma after each field except the last. With this method, however, the record length could not exceed MPEs limitation on the size of a string variable. Just about any program language could do the same thing as a command file and more efficiently. Rather than hard-code the field definition into the program, I would use a second parameter file to provide information about the input file, i.e., record length, number of fields and field positions. This way you would have a tool to transform any fixed field files to comma delimited files simply by modifying or creating a parameter file and pointing to the correct parameter file with a file equation. Finally, I advise you to call Robelle and get a Suprtool demo. The product is not very expensive should you decide to purchase it, and worth every dime. |
|||||
Copyright 1998, The 3000 NewsWire. All rights reserved. |