S00101
-----------------------------------------------------------------------------
TAR S001
FAST TAR WRITER WITH DIRECTORY
-----------------------------------------------------------------------------
Contribution Name...........: TAR
Title....................: Fast TAR writer with directory
File Names...............:00. Rename Transfer File
:01. TAR.SBMT submit file
:02. TAR.FTN
:03. TAR.REL
:04. TAR.LOD link command file
:05. TAR.HLP copy to /help/tar
:06. VDL.FTN required support prog
:07. VDL.REL
:08. VDL.LOD link command file
:09. FTNSUBS.FTN support lib
:10. FTNSUBS.LIB
:11. MACSUBS.MAC support lib
:12. MACSUBS.LIB
:13. QSUBF.FTN support lib
:14. QSUBF.LIB
:15. QSUBM.MAC support lib
:16. QSUBM.LIB
Operating System.........: RTE-A
Uses hierarchical files?.: Yes
Language(s)..............: Fortran
Keywords.................: 1. Archive
: 2. Backup
: 3. Save/Restore
: 4. Unix
External Support Req'd...:
If Re-submission, Reason.: Minor bug fixes, enhancements
Contributor's Name..........: Alan R. Whitney
Company.......: MIT Haystack Observatory
City..........: Westford
State.........: MA
Country.......: USA
Zip Code......: 01886
Phone Number..: 508-692-4764 awhitney@bashful.haystack.edu
Program Abstract............:
TAR is a fast TAR tape writer with many features, including:
1. Extremely fast -- much faster than TF or FST in writing tar tapes.
2. Alphabetizes file order within directories.
3. Option to write an ASCII directory of saved files as the first tar
file saved.
4. Option to write an ASCII log file of the tar execution as the last tar
file saved.
5. Option to save ASCII files either in native HP disc-image format or
converted to standard Unix file format.
6. Supports tar appends after end of current data.
7. Tested with Exabyte and DAT on A900, as well as standard mag tape.
8. Tapes written by TAR have been successfully read on both HP and Sun Unix
workstations.
Additional Documentation....: see TAR.HLP
S00201
-----------------------------------------------------------------------------
PUSH S002
THE GAME OF PUSH
-----------------------------------------------------------------------------
Contribution Name...........: PUSH
Title....................: THE GAME OF PUSH
File Names...............:00. Rename Transfer File
:01. PUSH.SBMT
:02. PUSH.FTN
:03. PUSH.FTNI
:04. PUSH.LST
:05. PUSH.MAKE
:06. PUSH.RUN
:07. PUSHDATA000.DAT
:08. PUSH_FILES.FTNI
Operating System.........: RTE
Uses hierarchical files?.: NO
Language(s)..............: FTN7X
Keywords.................: 1. GAMES
External Support Req'd...: NONE
If Re-submission, Reason.:
Contributor's Name..........: Alan Tibbetts
Company.......: Alan Tibbetts, Consultant
Street........: 3498 Gibson Ave.
City..........: Santa Clara
State.........: CA
Country.......: USA
Zip Code......: 95051
Phone Number..: 408 247 7280 FAX 408 247 6667
Program Abstract.............:
This is a very simple to play strategy game, just push the '*'s to the '~'s.
S00301
-----------------------------------------------------------------------------
LIBA S003
RTE-A SUBROUTINE LIBRARY
-----------------------------------------------------------------------------
Contribution Name...........: LIBA
Title....................: Rte-A Subroutine Library
File Names...............:00. Rename Transfer File (Interex-supplied)
:01. LIBA.SBMT
:02. LIBA.DOC
:03. LIBA.MRG
:04. LIBA_CDS.CMD
:05. LIBA_STD.CMD
:06. COMPILE.CMD
:07. CDS.FTNI
:08. CDS_OFF.FTNI
:09. CDS_ON.FTNI
:10. ABORTIO.MAC
:11. ACCSYSCOM.FTN
:12. CLOSESPOOL.FTN
:13. DEVICESTAT.FTN
:14. GETCONFIG.FTN
:15. GETIDADR.MAC
:16. GETIDNUM.MAC
:17. GETLOGONSTRING.FTN
:18. GETMYIDNUM.MAC
:19. GETPROGRAMNAME.FTN
:20. OPENSPOOL.FTN
:21. TIMEDOUT.FTN
:22. TIMELIST.MAC
:23. $LIBA_CDS.LIB - merged & lindx'd Cds Lib.
:24. $LIBA_STD.LIB - merged & lindx'd Std Lib.
Operating System(s)......: Rte-A ONLY.
Language(s)..............: Ftn7x, Macro
Keywords.................: 1. I/O
: 2. ID_SEGMENTS
: 3. LIBRARY
: 4. SPOOLING
: 5. SYSTEM
External Support Req'd...: LibC (separate contribution)
: SpolA (Csl/1000 Rev-2730 L014)
If Re-submission, Reason.: see Abstract
Contributor's Name..........: Bill Donze
Company.......: Reliance Electric
Street........: 6065 Parkland Blvd.
City..........: Cleveland
State.........: Ohio
Country.......: USA
Zip Code......: 44124-8020
Phone Number..: (216) 266-7619
Telex.........:
Contribution Abstract.......:
This contribution is the same as the like-named contribution that
appeared in the 1990 Boston Swap Tape, the 1991 San Diego Swap
Tape, and the Csl/1000 Rev-3126 Tape. It is be submitted here
since it is used by other contributions.
This package contains a number of routines used by our application
programs on the Rte-A Operating System in conjunction with LIBC and
SPOLA, separate contributions. Another companion library, LIB6,
which supported Rte-6/Vm systems has been discontinued.
The supplied command files require that this contribution be stored
in a global directory called /LibA.Dir and that two sub-directories,
Cds.Dir and Std.Dir, exist. Also, the command files reference the
programs MERGE and LINDX located on the Fmgr Disc Lu-2 (somewhere
other than /Programs/) so that the library can be generated on the
current system for use on the next revision of the system.
No changes have occurred since the '90 Boston Swap tape and
Csl/1000 Rev-3126 tape.
Additional Documentation....:
S00401
-----------------------------------------------------------------------------
LIBC S004
COMMON SUBROUTINE LIBRARY
-----------------------------------------------------------------------------
Contribution Name...........: LIBC
Title....................: Common Subroutine Library
File Names...............:00. Rename Transfer File (Interex-supplied)
:01. LIBC.SBMT
:02. LIBC.DOC
:03. LIBC.MRG
:04. LIBC_CDS.CMD
:05. LIBC_STD.CMD
:06. COMPILE.CMD
:07. CDS.FTNI
:08. CDS_OFF.FTNI
:09. CDS_ON.FTNI
:10. ASCIITOREAL.MAC
:11. AUTODIAL.FTN
:12. CHECKDSERROR.FTN
:13. CHECKFMPERROR.FTN
:14. CHECKIMAGEERROR.FTN
:15. COMPAREBYTES.MAC
:16. COMPAREWORDS.MAC
:17. CRTCOM.FTNI
:18. DSCOM.FTNI
:19. DSPST.FTN
:20. EXITTEST.FTN
:21. FMPCOM.FTNI
:22. FORMATTIME.FTN
:23. FORMT.MAC
:24. FREESPACE.FTN
:25. HELPTEST.FTN
:26. IDOPSYSTEM.FTN
:27. IDPLOTTER.FTN
:28. IDTERMINAL.FTN
:29. IMAGECOM.FTNI
:30. INTTOASCII.MAC
:31. INTTOBINARY.MAC
:32. LISTCOM.FTNI
:33. LISTLIB.FTN
:34. LOADBYTE.MAC
:35. LOGCOM.FTNI
:36. MOVEBYTES.MAC
:37. MSGCOM.FTN
:38. MSGCOM.FTNI
:39. REALTOASCII.MAC
:40. SETDIRPATH.FTN
:41. SKIPLINES.FTN
:42. STOREBYTE.MAC
:43. TIMESTAMP.FTN
:44. TIMETOEXEC11.FTN
:45. WILDMATCH.FTN
:46. WRITECRT.FTN
:47. WRITECRTLOG.FTN
:48. WRITELOG.FTN
:49. $LIBC_CDS.LIB - merged & lindx'd Cds Lib.
:50. $LIBC_STD.LIB - merged & lindx'd Std Lib.
Operating System(s)......: Rte-A or Rte-6/Vm
Language(s)..............: Ftn7x, Macro
Keywords.................: 1. CONVERSION
: 2. COMPARE
: 3. LIBRARY
External Support Req'd...: LibA (separate contribution)
: Lib6 (Csl/1000 Rev-2730 L005)
If Re-submission, Reason.: see Abstract
Contributor's Name..........: Bill Donze
Company.......: Reliance Electric
Street........: 6065 Parkland Blvd.
City..........: Cleveland
State.........: Ohio
Country.......: USA
Zip Code......: 44124-8020
Phone Number..: (216) 266-7619
Telex.........:
Contribution Abstract.......:
This contribution is the same as the like-named contribution in the
1991 San Diego Swap Tape. It is be re-submitted here since it is
used by other contributions.
This package contains a number of routines used by our application
programs on the Rte-A Operating System in conjunction with LIBC, a
separate contribution. Another companion library, LIB6, which
supported Rte-6/Vm systems has been discontinued.
The supplied command files require that this contribution be stored
in a global directory called /LibC.Dir and that two sub-directories,
Cds.Dir and Std.Dir, exist. Also, the command files reference the
programs MERGE and LINDX located on the Fmgr Disc Lu-2 (somewhere
other than /Programs/) so that the library can be generated on the
current system for use on the next revision of the system.
The following changes have occurred since the '90 Boston Swap Tape
and Csl/1000 Rev-3126 tape:
Modified: OPENSPOOL.FTN - call argument added; Rte-6 users must
update the /Lib6 routine OpenSpool.
Additional Documentation....:
S00501
-----------------------------------------------------------------------------
IMULD S005
IMAGE/1000-II UNLOAD UTILITY
-----------------------------------------------------------------------------
Contribution Name...........: IMULD
Title....................: Image/1000-II Unload Utility
File Names...............:00. Rename Transfer File (Interex-supplied)
:01. IMULD.SBMT
:02. CDS.FTNI
:03. CDS_OFF.FTNI
:04. CDS_ON.FTNI
:05. DATABASECOM.FTNI
:06. DATABASELIB.FTN
:07. DATABASELIB.REL
:08. IMULD.FTN
:09. IMULD.LOD
:10. IMULD.REL
:11. INPUTCOM.FTNI
:12. INPUTLIB.FTN
:13. INPUTLIB.REL
:14. OUTPUTCOM.FTNI
:15. OUTPUTLIB.FTN
:16. OUTPUTLIB.REL
Operating System(s)......: Rte-A or Rte-6/Vm
Language(s)..............: Ftn7x
Keywords.................: 1. DATA_BASE
: 2. IMAGE
External Support Req'd...: LibC (separate contribution)
If Re-submission, Reason.:
Contributor's Name..........: Bill Donze
Company.......: Reliance Electric
Street........: 6065 Parkland Blvd.
City..........: Cleveland
State.........: Ohio
Country.......: USA
Zip Code......: 44124-8020
Phone Number..: (216) 266-7619
Telex.........:
Contribution Abstract.......:
This utility provides the means to unload selected datasets from
an Image/1000-II database to selected Ascii output files in a
format compatible with the DBBLD program.
The user can specify the maximum length of the output records in
bytes, the dataset name or number to be unloaded, and the name of
the output file. The IMAGE mode of operation will create output
files that are compatible with DBBLD; the FOREIGN mode of operation
creates output files that can be ported to another platform by
inserting a user-specified character between each field in the
output record.
Additional Documentation....:
S00601
-----------------------------------------------------------------------------
CALLB S006
MODEM CALL-BACK PROGRAM
-----------------------------------------------------------------------------
Contribution Name...........: CALLB
Title....................: Modem Call-Back Program
File Names...............:00. Rename Transfer File (Interex-supplied)
:01. CALLB.SBMT
:02. CALLB.FTN
:03. CALLB.LOD
:04. CALLB.REL
Operating System(s)......: RTE-A
Language(s)..............: F77
Keywords.................: 1. MODEM
: 2. SECURITY
External Support Req'd...: Modem with dial-out capability, HPMDM
If Re-submission, Reason.:
Contributor's Name..........: Brian Gray
Company.......: American Red Cross
Street........: 3747 Euclid Ave
City..........: Cleveland
State.........: Ohio
Country.......: USA
Zip Code......: 44115
Phone Number..: 216-431-3010
Telex.........:
Contribution Abstract.......:
This contribution contains enhancements to the CALLB program as
distributed by HP on RTE-A 5.2.
A call-back security system requires that modem users call from a
previously defined phone number. The caller identifies himself to
the system, and the system calls the pre-defined phone number. The
user then answers the incoming (modem) call, connects, and porcedes
with his session.
Enhancements include:
* Implemented the Immediate-Connect (!) option. When calling from a
location which does not have direct-inward dial capability (a hotel
room, for example), the user may enter a user-id and password which
immediately produces an RTE logon prompt. This defeats the primary
purpose of a call-back system, but does require a second user-id &
password combination.
* Implemented the "Call-back to a different number" option (?). When
calling from a phone number that is not defined, but has direct-inward
dial capability (a friend's home, for example), the user may enter
a user-id and password which causes CALLB to prompt the user for
a phone number to call. The line is disconnected, and the system
returns the call as if the number were pre-defined. (This can be
used to transfer most of the cost of a long-distance session from
the user to the company.)
* Implemented a dial-out request. A user already on the system
can instruct the system to call a remote modem directly, by tricking
CALLB into thinking that a user dialed in and gave a valid user-id &
password. (I use this option to eliminate a small long-distance
charge for initialting the call-back process. The user who calls
me to report a problem issues the appropriate command to call my
modem at home. The phone charges are on the company's bill.)
See comments in the source code for specific information.
* To use HPMDM and CALLB, do the following:
Initialize and configure the modem port. The primary program
should be set to HPMDM.
Start HPMDM, and add the modem port to HPMDMs configuration.
In the HPMDM configuration, the port's primary program is CALLB.
When CALLB verifies a user-id and password, the modem port's primary
program is changed to PROMT, the return call is made, and CALLB
terminates.
Additional Documentation....:
In the source code.
S00701
-----------------------------------------------------------------------------
MSDOS S007
DAMAGE CONTROL FOR MS-DOS COMMANDS UNDER RTE-A
-----------------------------------------------------------------------------
Contribution Name............: MSDOS
Title.....................: Damage control for MS-DOS commands under RTE-A
File Names................:00. Rename Transfer File [See Note 1.]
:01. MSDOS.SBMT - This file
:02. DIR.FTN -
:03. DIR.LOD -
:04. DIR.REL -
:05. COPY.FTN -
:06. COPY.LOD -
:07. COPY.REL -
:08. MAKEFILE.MAKE - MAKE command file.
:09. MAKEMSDOS.CMD - Invokes MAKE.
:10. LOADANDRUN.CMD - Command it and see.
:11. FOCOLI.CMD - FOrtran COmpile & LInk.
Operating System..........: RTE-A maybe 6.
Language(s)...............: FTN7X
External Support Req'd....: None
If Re-submission, Reason..:
Keywords..................:01. SYSTEM
:02. PC
Contributor's Name...........: Dan Khoushy
Company........: Marine Computing Ltd.
Street.........: 83, Marylebone High Street
City...........: London
State..........:
Country........: United Kingdom
Zip Code.......: W1
Phone Number...: (071) 486 9590
Fax............: (071) 224 3159
Program Abstract.............:
When the tired mind is slower than the nimble fingers, one tends to type
the wrong commands with more or less the right parameters. The MS-DOS
commands that cause me the most trouble are COPY, DIR and CD. Wild card
characters are also somewhat troublesome, mainly "*", but also "?" crops up
once in a while. To reduce the annoyance factor it is quite easy to write
command files that translate MS-DOS commands to RTE-A. For example the
command file to translate COPY into CO might read:
CO,$1,$2,$3
Such a strategy works, but it is slow, and there is an annoyance factor in
the screen output. Consequently this contribution contains two examples of
the way I cope with this situation. I do not dare to show the way how to
deal with CD since this involve real hacking (preventing CI from reacting
by substituting CQ for CD and writing a CD program that deciphers whether
you mean RTE-A CD or MS-DOS CD).
There is a previous CSL contribution, CSL2730-L085 by John Anderson. The
slant of that contribution is slightly different - emulation rather than
damage control. Except for DIR and CLS he uses command files.
There are several other MS-DOS command that may be of sufficient interest
to emulate following John's examples, or to contain using the current two
programs as templates.
Additional Documentation....: None.
S00801
-----------------------------------------------------------------------------
WORDGAME S008
A WORD SQUARE PUZZLE SOLVER
-----------------------------------------------------------------------------
Contribution Name............: WORDGAME
Title.....................: A word square puzzle solver
File Names................:00. Rename Transfer File [See Note 1.]
:01. WORDSQUAREPUZZLE.SBMT - This file
:02. WORDSQUAREPUZZLE.FTN -
:03. WORDSQUAREPUZZLE.LOD -
:04. WORDSQUAREPUZZLE.REL -
:05. MAKEFILE.MAKE - MAKE command file.
:06. MAKEWORDSQUAREPU.CMD - Invokes MAKE.
:07. LOADANDRUN.CMD - Command it and see.
:08. FOCOLI.CMD - FOrtran COmpile & LINK.
:09. TABLE.DAT - Test data file
:10. WORD.DAT - Test data file
Operating System..........: RTE-A maybe 6.
Language(s)...............: FTN7X
External Support Req'd....: None
If Re-submission, Reason..:
Keywords..................:01. GAMES
Contributor's Name...........: Dan Khoushy
Company........: Marine Computing Ltd.
Street.........: 83, Marylebone High Street
City...........: London
State..........:
Country........: United Kingdom
Zip Code.......: W1
Phone Number...: (071) 486 9590
Fax............: (071) 224 3159
Program Abstract.............:
This contribution is a solution for the word square puzzles. A word square
consists of letters arranged in a square, and one is supposed to match a
list of words into the square, by finding the right patterns in any
direction, including the diagonal directions. For the purpose of the
present program it is assumed that the patterns are not reflected at the
boundaries. The arbitrary limit on the puzzle size is 24x24 for the square
and 96 words for the list, but these are easily changed.
Usage: WORDSQUAREPUZZLE,LISTLU,WORDSQUARE,SQUARESIZE,WORDLIST,LISTSIZE
Where: WORDSQUARE is an ASCII file with the word square, up to 24x24
SQUARESIZE is the size of the square side.
WORDLIST is an ASCII file name one word/line.
LISTSIZE is the size of the list.
Try : WORDSQUAREPUZZLE,1,TABLE.DAT,12,WORD.DAT,24
Additional Documentation....: None.
S00901
-----------------------------------------------------------------------------
BREAK S009
BREAK CI AND SUBORDINATE PROGRAMS, FOR SURE
-----------------------------------------------------------------------------
Contribution Name......(16).: BREAK
Title...............(64).: Break CI and subordinate programs, for sure
File Names...............: 00. Rename Transfer File (INTEREX supplied)
: 01. BREAK.SBMT This file
: 02. BREAK.FTN BREAK source
: 03. BREAK.LOD
: 04. BREAK.REL
: 05. SETBREAK.MAC Subroutine source
: 06. SETBREAK.REL Subroutine relo
: 07. BREAK.MAKE Make file
Operating System(s)......: RTE-A
Uses hierarchical files?.: Yes
Language(s)..............: FTN7X, MACRO
Keywords.................: CI
: COMMAND_FILES
External Support Req'd...: None
If Re-submission, Reason.:
Contributor's Name..........: Donald A. Wright
Company.......: Interactive Computer Technology
Street........: 2069 Lake Elmo Avenue North
City..........: Lake Elmo
State.........: MN
Zip Code......: 55042
Country.......: USA
Phone Number..: 612/770-3728
Date..........: 93 Mar 20
Program Abstract............:
When CI is executing nested command files, its execution is not
stopped by a BReak command. The BReak flag only causes CI to drop
down one level to the next lower command file, where execution may
continue.
This little program allows you to STOP CI cleanly without OFFing it.
It first issues a BReak command to all programs subordinate to CI in
the parent/child chain, and then issues repetitive BReaks to CI
itself until it sees that CI has stopped or until a timeout com-
pletes.
Example: You have a command file which compiles and links several
modules. After starting this, you realize that there is a mistake in
an include file or LINK is using the wrong SNAP, or something else is
wrong. Simply run BREAK, and the compiler or linker will stop and so
will CI.
You may also tell BREAK to act at a different session than the one
from which it is scheduled.
S01001
-----------------------------------------------------------------------------
ENTRIES S010
REPORT RTE-A OPERATING SYSTEM PROPERTIES
-----------------------------------------------------------------------------
Contribution Name......(16).: ENTRIES
Title...............(64).: Report RTE-A Operating System Properties
File Names...............: 00. Rename Transfer File
: 01. ENTRIES.SBMT This file
: 02. ENTRIES.FTN Source
: 03. ENTRIES.LOD
: 04. ENTRIES.MAKE Compile/link commands
: 05. ENTRIES.REL
: 06. ENTRIES.SEND File list for KERMIT send
: 07. CPU.MAC Macro source
: 08. CPU.REL Macro relocatable
Operating System(s)......: RTE-A
Uses hierarchical files?.: No
Language(s)..............: FTN7X,MACRO
Keywords.................: COMMON
: ENTRY_POINTS
: SYSTEM
External Support Req'd...: None
If Re-submission, Reason.: Enhancements
Contributor's Name..........: Donald A. Wright
Company.......: Interactive Computer Technology
Street........: 2069 Lake Elmo Avenue North
City..........: Lake Elmo
State.........: MN
Country.......: USA
Zip Code......: 55042
Phone Number..: 612/770-3728
Fax Number....: 612/770-5986
Date..........: 93 Mar 20
Program Abstract............:
ENTRIES is a quick and dirty program that reports back the operating
system $OPSY code, the date code $DATC, firmware revision $FREV, size
of blank common $BC#, and CPU type (i.e. A400, A990).
It's especially handy for folks who ship software to sites where the
exact CPU and operating system may be unknown, e.g. vendors and
internal software support personnel. It can be shipped along with
other software, and quickly linked and run if there is a need to know
any of the items that it reports.
We ship it now with CONNECT and SYLOG, so that if there are problems
and we need to dial in we can immediately determine what we are deal-
ing with.
This version is enhanced over a previous submission on the 1991 swap
tape and on the 3226 CSL tape. It includes the A990 and a much bet-
ter report of the .FREV value(s), which no longer worked correctly in
the previous submission on RTE Rev 6000. Here is a typical report on
an A400:
CI> entries
$OPSY Operating System = -125
$DATC OPSY Date Code = 6000
$BC# Blank Common Size = 5267
.CPUID CPU Type = 7 A400
.FREV CPU Control Store = Bank 0 Rev 12 Package= 1 Base Set
.FREV CPU Control Store = Bank 1 Rev 12 Package= 1 Base Set
.FREV CPU Control Store = Bank 2 Rev 12 Package= 1 Base Set
.FREV CPU Control Store = Bank 3 Rev 12 Package= 1 Base Set
CI>
Note: At RTE Rev 6000, the OPSY and DATC values are also displayable
with CI's SET command. However, this program should link and run on
almost ANY revision of RTE.
S01101
-----------------------------------------------------------------------------
HPIB59309 S011
SET TIME FROM HPIB 59309A CALENDAR CLOCK
-----------------------------------------------------------------------------
Contribution Name......(16).: HPIB59309
Title...............(64).: Set Time from HPIB 59309A Calendar Clock
File Names...............: 00. Rename Transfer File (INTEREX supplied)
: 01. HPIB59309.SBMT This file
: 02. SET59309.FTN Set Clock Source
: 03. SET59309.LOD
: 04. SET59309.REL
: 05. SETTIME.FTN Set RTE Time Source
: 06. SETTIME.LOD
: 07. SETTIME.REL
: 08. LEFTJUSTIFY.MAC
: 09. LEFTJUSTIFY.REL
Operating System(s)......: RTE-A
Uses hierarchical files?.: Yes
Language(s)..............: FTN7X
Keywords.................: DATE
: TIME
: CALENDAR
External Support Req'd...: None
If Re-submission, Reason.:
Contributor's Name..........: Donald A. Wright
Company.......: Interactive Computer Technology
Street........: 2069 Lake Elmo Avenue North
City..........: Lake Elmo
State.........: MN
Zip Code......: 55042
Country.......: USA
Phone Number..: 612/770-3728
Date..........: 93 Mar 20
Program Abstract............:
The venerable HP 59309A HPIB clock has long been a good instrument
for automatically setting the RTE time at bootup. It is no longer in
the HP catalog, but there seem to be lots of them kicking around. I
recently was given one which would otherwise have been scrapped, and
resurrected some 10-year-old software to manage it. There are two
programs:
1. SET59309 is used interactively to set the date and time on the
clock itself. It is much more convenient than using the clock's
front panel controls.
2. SETTIME is used at bootup to set the RTE time from the HPIB clock.
See the source for runstring information.
The 59309 needs one HPIB LU configured as an "instrument". I did
some testing of the clock on my disk HPIB and found that it did not
slow down disk accesses at all except while actually addressed as a
listener or a talker, so I genned it with disk HPIB card and it works
fine.
Note: The 59309 knows the month, day, and time, but not the year. If
you use it with this software, you will need to edit the WELCOME file
as soon as possible in each new year to tell the SETTIME program the
correct year.
Note also: The 59309 has room inside for a standard 9-volt "tran-
sistor" battery to preserve the time during a power failure. You'll
never be sorry if you use a good quality alkaline battery, which is
much less likely than a carbon-zinc battery to ooze nasty stuff into
the clock when the battery fails. Best yet - replace it every year
on January 1.
S01201
-----------------------------------------------------------------------------
PROTOTYPES S012
CREATE PROTOTYPE ID'S QUICKLY AND SILENTLY
-----------------------------------------------------------------------------
Contribution Name......(16).: PROTOTYPES
Title...............(64).: Create Prototype ID's Quickly and Silently
File Names...............: 00. Rename Transfer File (INTEREX supplied)
: 01. PROTOTYPES.SBMT This file
: 02. PROTOTYPES.FTN Source
: 03. PROTOTYPES.LOD
: 04. PROTOTYPES.REL
: 05. PROTOTYPES.DAT Example RP list
: 06. APPEND.FTN
: 07. APPEND.REL
Operating System(s)......: RTE-A
Uses hierarchical files?.: Yes
Language(s)..............: FTN7X
Keywords.................: BOOT-UP
: ID_SEGMENTS
External Support Req'd...: None
If Re-submission, Reason.:
Contributor's Name..........: Donald A. Wright
Company.......: Interactive Computer Technology
Street........: 2069 Lake Elmo Avenue North
City..........: Lake Elmo
State.........: MN
Zip Code......: 55042
Country.......: USA
Phone Number..: 612/770-3728
Date..........: 93 Mar 20
Program Abstract............:
Prototype ID Segments provide one of the simplest and most efficient
ways to speed up RTE for operators. In addition they provide by far
the best way to create program "aliases", where a single program may
be known by more than one name. In particular, they are considerably
more efficient than the new Symbolic Links provided in RTE 6.0.
Most of us have a list of Prototype ID's we want created at bootup:
CI, CIX, EDIT, IS, LI, WH, etc. These are usually RP'd in the
WELCOME file using CI's RP command.
However, each RP command in CI generates a line on the screen even if
logging is off. This program RP's the segments quietly and quickly,
still reporting errors if any occur. It takes its input from a data
file which you create and maintain, making it easy to add and delete
Prototype ID's for the next boot.
Part of the contribution is ICT's PROTOTYPES.DAT file, as an example
of a typical RP list.
S01301
-----------------------------------------------------------------------------
MOUSELIB S013
MOUSE-HANDLER LIBRARY AND DEMO PROGRAM
-----------------------------------------------------------------------------
Contribution Name......(16).: MOUSELIB
Title...............(64).: Mouse-Handler Library and Demo Program
File Names...............: 00. Rename Transfer File (INTEREX supplied)
: 01. MOUSELIB.SBMT This file
: 02. MOUSELIB.FTN Main program source
: 03. MOUSELIB.FTNI Include file
: 04. MOUSELIB.LIB LINDEXed relocatable
: 05. MOUSELIB.CMD Creates MOUSELIB.LIB
: 06. MOUSELIB.MER Merge file
: 07. MOUSE_PAPER.TXT Paper for INTEREX conf
: 08. CNLUAB.MAC CNLUAB MACRO source
: 09. CNLUAB.REL CNLUAB relocatable
: 10. DEMO.FLDS DEMO prog field definitions
: 11. DEMO.FORM DEMO prog form file
: 12. DEMO.FTN DEMO prog source
Note that the above file, DEMO.FTN, is to be used only as
an example - it is missing an include file. Use the .rel file
to load the demo.
: 13. DEMO.REL DEMO prog relocatable
: 14. DEMO.LOD DEMO prog link file
: 15. INTTODECIMAL2.FTN
: 16. INTTODECIMAL2.REL
: 17. SCREENLIB.LIB
Operating System(s)......: RTE-A
Uses hierarchical files?.: Yes
Language(s)..............: FTN7X, MACRO
Keywords.................: FORMS
: MOUSE
: SOFTKEYS
: TERMINAL
External Support Req'd...: Some forms package would be nice
If Re-submission, Reason.:
Contributor's Name..........: Donald A. Wright
Company.......: Interactive Computer Technology
Street........: 2069 Lake Elmo Avenue North
City..........: Lake Elmo
State.........: MN
Zip Code......: 55042
Country.......: USA
Phone Number..: 612/770-3728
Date..........: 92 July 1
Program Abstract............:
MOUSELIB is a small library of subroutines used to manage the
input from a Logitech Mouseman 3-Button Serial Mouse. Using
MOUSELIB in combination with a screen package you can use the
mouse to modernize your HP1000 data-entry applications in a very
impressive and intuitive way.
The associated DEMO program may be linked and run, but it is not
an actual application. Its purpose is to show a few ways that
MOUSELIB might be used in real applications.
Note that the included SCREENLIB relocatable library is an
undocumented package which has not been formally contributed.
The reason for its inclusion here is simply to allow the DEMO
program to link and run.
For additional documentation, see the following files:
MOUSE_PAPER.TXT
MOUSELIB.FTN
DEMO.FTN
S01401
-----------------------------------------------------------------------------
OSAVE AND ORSTR S014
PHYSICAL SAVE OF DISK TO FILE
-----------------------------------------------------------------------------
Contribution Name......(16).: OSAVE and ORSTR
Title...............(64).: Physical Save of Disk to File
File Names...............: 00. Rename Transfer File (INTEREX supplied)
: 01. OSAVE.SBMT This file
: 02. OSAVE.FTN OSAVE source
: 03. OSAVE.FTNI Include file
: 04. OSAVE.LOD LINK command file
: 05. OSAVE.REL OSAVE relocatable
: 06. ORSTR.FTN ORSTR source
: 07. ORSTR.LOD LINK command file
: 08. ORSTR.REL ORSTR relocatable
: 09. OLIB.CMD CI command file
: 10. OLIB.FTN Fortran Library Source
: 11. OLIB.FTNI Include file
: 12. OLIB.LIB Merged Lindexed Library
: 13. OLIB.MER Merge command file
: 14. OLIB.REL Fortral Lib Relocatable
: 15. OMAC.MAC Macro Library Source
: 16. OMAC.REL Macro Library Relocatable
Operating System(s)......: RTE-A
Uses hierarchical files?.: Yes
Language(s)..............: FTN7X, MACRO
Keywords.................: BACKUP
: ABSOLUTE
: DISC
: FILES
External Support Req'd...: None
If Re-submission, Reason.:
Contributor's Name..........: Donald A. Wright
Company.......: Interactive Computer Technology
Street........: 2069 Lake Elmo Avenue North
City..........: Lake Elmo
State.........: MN
Zip Code......: 55042
Country.......: USA
Phone Number..: 612/770-3728
Date..........: 92 Aug 20
Program Abstract............:
OSAVE and ORSTR are utility programs which perform a physical save or
restore of complete disk LU's to files on a large "backup disk" such as
a rewritable Optical disk, hence the name O(ptical)SAVE.
They have essentially the same function as ASAVE and ARSTR, except they
save the LU's to named files rather than to tape.
They meet these specifications:
1) Command set very similar to ASAVE and ARSTR.
2) Commands may come from runstring, same as ASAVE and ARSTR.
3) Non-CDS, non-segmented, 32 pages or less, no EMA or VMA.
4) Reasonably fast, with their own speed metrics and %-done display.
5) Multiple disk LU's may be saved per file.
6) Destination file automatically sized to exactly contain saved LU's.
7) Disk LU's may be restored selectively and to different LU numbers.
A typical user might protect his system disks by first placing a
bootable memory-based system containing ORSTR in the reserved area of
an MO cartridge, then using OSAVE to save his system disks to the FMP
space on that same cartridge. Now s/he has a slick, quick, tapeless
way to completely recover from a disk crash.
Speed is quite reasonable, with some care taken to make it as high as
possible without going over 32 pages or using EMA for either program.
Internal buffers are 16 K words. This table shows the time required
for an A400 to save a 20-Mbyte disk LU from a 7958A drive to a Series
6300 650-Mbyte MO disk with SCSI interface:
Option Minutes:seconds Mbytes/min Kbytes/sec
------ --------------- ---------- ----------
NC 3:19 6.03 100.5
(none) 4:27 4.49 74.9
VE 7:42 2.60 43.3
Where:
NC option means that the write is not verified and checksums are not
calculated.
(none) The absence of options means that checksums are calculated and
written to disk for use in later restore, but the write is not
verified.
VE option means that checksums are calculated for use in restore and
a bit-for-bit verify is done immediately after writing.
In another test, OSAVE wrote from a 7945 10-Mbyte LU to a 7958A with
the NC option in 1 minute 13 seconds, for a speed of 8.22 Mbytes/min or
137 Kbytes/sec.
Speed will be a bit higher on an A900 or A990, especially when doing
checksums or verify, and higher yet if both the source and destination
disks are big, fast rigid disks. Restore speeds are significantly
higher than save speeds when the destination is an MO disk, but this is
hardly a critical issue for most folks.
There is very little unusual programming in the software. No tricks.
HP's undocumented disk libraries are not used. I/O with the disk LU
being saved or restored is done with standard EXEC calls, and I/O with
the save file is done with FMP. Overlapping writes or write/reads are
not done, and overlapping reads are done only during verify. There is
a small library of MACRO routines, most of which are in MACRO because
they are a bit faster than they could be in Fortran. A couple are
included just because they are a standard part of the ICT library and
were handy.
See also the documentation in the sources, and enter ? at an OSAVE or
ORSTR prompt for a description of available commands.
S01501
-----------------------------------------------------------------------------
AUTO1 S015
AUTOMATICALLY ASSIGN LU 1 TO VCP DEVICE AT BOOT
-----------------------------------------------------------------------------
Contribution Name......(16).: AUTO1
Title...............(64).: Automatically Assign LU 1 to VCP Device at Boot
File Names...............: 00. Rename Transfer File (INTEREX supplied)
: 01. AUTO1.SBMT This file
: 02. AUTO1.FTN Main program source
: 03. AUTO1.LOD LINK command file
: 04. AUTO1.REL Main program relo
: 05. AUTO1MACLIB.LIB LINDEXed MACRO Library
: 06. AUTO1MACLIB.MAC MACRO Library source
: 07. AUTO1MACLIB.REL MACRO Library relo
: 08. WHAT1.FTN Fortran source
: 09. WHAT1.LOD LINK command file
: 10. WHAT1.REL Relo
: 11. SWAPLU.FTN Fortran source
: 12. SWAPLU.LOD LINK command file
: 13. SWAPLU.REL Relo
: 14. INIT_NOT1.CMD Example CI command file
Operating System(s)......: RTE-A
Uses hierarchical files?.: Yes
Language(s)..............: FTN7X, MACRO
Keywords.................: BOOT-UP
: CONFIGURE
External Support Req'd...: Zip
If Re-submission, Reason.:
Contributor's Name..........: Donald A. Wright
Company.......: Interactive Computer Technology
Street........: 2069 Lake Elmo Avenue North
City..........: Lake Elmo
State.........: MN
Zip Code......: 55042
Country.......: USA
Phone Number..: 612/770-3728
Date..........: 92 Aug 20
Program Abstract............:
AUTO1 is executed at bootup to determine the type of serial I/O card
associated with the VCP device and to rummage around in the operating
system for an appropriate driver for it. It functions as follows:
1) Determine what kind of VCP device we have: ASI card, C-MUX, D-MUX,
or A400 OBIO.
2) Starting with LU 1, search forward for a logical unit generated to
match the VCP card (same select code, correct drivers, MUX port 0).
If found, make it LU 1.
3) If not found, start again at LU 1 looking for an LU which matches
except for select code. If found, make it LU 1 and also assign
the real select code to this IFT.
4) Initialize the port, whatever it is.
5) Schedule the specified next startup program (e.g. CI).
This program allows you to generate a generic system which can run on
any computers with the same disk layouts - the VCP devices need not be
the same.
Possible applications:
1) You have a number of HP1000's all with the same subset of disk LU's.
Let's say the disks are configured like the Primary, for example.
Some old computers have ASI cards, some C- or D-MUXes, and some new
ones are A400's with no other serial devices. You can now generate
a single operating system that can be used on any of these.
2) You have several HP1000's, all of which have a floppy disk drive (or
a CS/80 tape) generated in. They do not all have the same serial
cards. You can now create offline utilities and diagnostics which
can boot on ANY of those systems, rather than having a different
offline tape for each system.
There is actually a program like this on the HP primary, but for some
reason HP does not allow access to either the source or the
relocatable. This one is better anyway, because it will even
reconfigure the select code if it needs to.
Example of a simple usage in a BUILD command file for ARSTR:
arstr.sys:::1:2048
/system/ict920417.snp
/system/ict920417.sys
yep
256
rp /programs/auto1.cmd
st,,,ar,st,r
rp /programs/arstr.run
/e
Write the resulting BUILD system file to tape, and now you can boot
ARSTR on any system with a tape drive.
The whole AUTO1 package consists of four parts:
1) AUTO1: The RTE startup program.
2) WHAT1: Program which returns the LU 1 MUX type in CI's $RETURN_S.
3) CI command file written by you (see INIT_NOT1.CMD example).
4) SWAPLU: Exchanges two LU numbers.
Example of usage in booting a complete system. The system is generated
with no LU 1 but with the following serial devices:
LU's Devices
------- ---------------------------------------------
70 - 77 C-MUX
80 - 81 ASI cards (using either the new or old driver)
90 - 94 OBIO
100-107 D-MUX
The BOOT.CMD file contains the following RP and startup commands:
RP,CI,START
RP,AUTO1
ST,,3,ST,AR,T
This ST command instructs AUTO1 to schedule START when it is done, and
to pass it the value 3 in RMPAR(2) so that WELCOME3.CMD will be used.
WELCOME3.CMD contains commands to configure an additional terminal as
LU 2 in the destination system (could be any list of terminals), which
will depend upon the type of actual serial hardware discovered:
RU,WHAT1
SET LUTYPE = $RETURN_S
IF IS $LUTYPE = A ASI card
THEN
SWAPLU 81 2 So swap in 81
ELSE
IF IS $LUTYPE = C C-MUX (or B-MUX) card
THEN
SWAPLU 71 2 So swap in LU 71
CN 2 30B 152331B And configure it
ELSE
IF IS $LUTYPE = D D-MUX card
THEN
SWAPLU 101 2 So swap in LU 101
CN 2 30B 130B And configure it
ELSE
IF IS $LUTYPE = O A400 OBIO
THEN
SWAPLU 91 2 So swap in LU 91
CN 2 30B 130B And configure that
FI
FI
FI
FI
CN 2 20B PROMT
UNSET LUTYPE
See sources AUTO1.FTN and WHAT1.FTN for additional usage information.
S01601
-----------------------------------------------------------------------------
DP S016
DISPLAY DRIVER PARAMETERS FOR RTE-A
-----------------------------------------------------------------------------
Contribution Name...........: DP
Title....................: Display Driver Parameters for RTE-A
File Names...............:00. Rename Transfer File (Interex-supplied)
:01. DP.SBMT
:02. DP.FTN
:03. DP.REL
Operating System(s)......: RTE-A ONLY
Language(s)..............: FTN7X
Keywords.................: 1. SYSTEM_TABLES
: 2. DRIVER
: 3. TOOLS
External Support Req'd...: NONE
If Re-submission, Reason.: ENHANCEMENT
Contributor's Name..........: Donald L. Clapp
Company.......: Eli Lilly & Co.
Street........: Lilly Corporate Center
City..........: Indianapolis
State.........: Indiana
Country.......: USA
Zip Code......: 46285
Phone Number..: (317) 276-1207
Internet......: CLAPP@LILLY.COM
Contribution Abstract.......: This program was originally submitted
by Dan Felman on the 2730 Tape. Works fine, I added an 'OK'
parameter to allow use in the WELCOMEnn.CMD file.
7-6-92 Changed the display format to accomodate 16 bit UNsigned values.
Should now match what the generator was told.
Added a '+Q' option, for those who know what they are doing and
don't need the confirmation of the changes.
Additional Documentation....: The code makes interesting reading.
S01701
-----------------------------------------------------------------------------
TOUCH S017
TIMESTAMP EDITOR ( SEE MAKE)
-----------------------------------------------------------------------------
Contribution Name...........: TOUCH
Title....................: Timestamp editor ( see MAKE)
File Names...............:00. Rename Transfer File (Interex-supplied)
:01. TOUCH.SBMT
:02. TOUCH.FTN
:03. TOUCH.REL
:04. DAYNUMBER.FTN
:05. DAYNUMBER.REL
:06. DAYTIMETOSECS.FTN
:07. DAYTIMETOSECS.REL
:08. LEAP.FTN
:09. LEAP.REL
:10. JULIAN.FTN
:11. JULIAN.REL
:12. MONTHNUMBER.FTN
:13. MONTHNUMBER.REL
:14. TOUCH.LOD
:15. TOUCH.MAKE
Operating System(s)......: CI files ONLY
Language(s)..............: FTN7X
Keywords.................: 1. TIME
: 2. EDITOR
: 3. UPDATE
: 4. CI
: 5. UNIX
External Support Req'd...: NONE
If Re-submission, Reason.:
Contributor's Name..........: Donald L. Clapp
Company.......: Eli Lilly & Co.
Street........: Lilly Corporate Center
City..........: Indianapolis
State.........: Indiana
Country.......: USA
Zip Code......: 46285
Phone Number..: (317) 276-1207
Internet......: CLAPP@LILLY.COM
Contribution Abstract.......: This program is an extension of the
program of the same name that was included in the contribution
called MAKE. This attempt will alter all three of the timestamps
of a file. There are some date manipulation routines that may
be useful for other applications.
WARNING************This program may overlay the RTE Rev 6.0 version of
*******************the program with the same name*********************
S01801
-----------------------------------------------------------------------------
CTT S018
COPY TAPE TO TAPE
-----------------------------------------------------------------------------
Contribution Name...........: CTT
Title....................: Copy Tape to Tape
File Names...............:00. Rename Transfer File (Interex-supplied)
:01. CTT.SBMT
:02. COUNT.FTN
:03. CTT.FTN - main
:04. CTT.FTNI - include file
:05. CTT.HELP - help file (GENIX)
:06. CTT.LOD - link command file
:07. CTT.TEXT - help file (ASCII)
:08. CTT2.LOD - link a 2nd version
:09. CTT_COMP.CMD - compile command file
:10. CTT_DATA.FTN - common initialization
:11. CTT_EMA.FTNI - EMA include file
:12. CTT_SEG1.FTN - segments 1 ..
:13. CTT_SEG2.FTN
:14. CTT_SEG3.FTN
:15. CTT_SEG4.FTN - .. to 4
:16. CTT_WP5P1.DOC - doc in WP 5.1 format
:17. DEVICETYPE.FTN
:18. DRIVERNAME.FTN - get driver name (RTE-6)
:19. DRIVERNAMEDUMMY.FTN
:20. EMACMW.MAC - compare EMA arrays
:21. FITSCHECK.FTN
:22. FIX6ID.FTN - juggling with ID-
:23. FIXAID.FTN segments in RTE-6 & A
:24. FORMATCHECK.FTN
:25. FST1.CTT - configuration file
:26. FST2.CTT - id for 2nd version
:27. GET6SHEMATABLE.FTN - get SHEMA table (RTE-6)
:28. GETASHEMATABLE.FTN - get SHEMA table (RTE-A)
:29. GETNEXTFILE.FTN
:30. HELP.FTN - help routine
:31. INSERT.FTN
:32. INSTALL.CMD - installation cmd file
:33. LIST.FTN
:34. LOGDEVICE.FTN
:35. POSINPUTTAPE.FTN
:36. POSOUTPUTTAPE.FTN
:37. REPORTFMPERROR.FTN
:38. SENDMSG.FTN
:39. SHOW.FTN - shows settings
:40. WRITETAPE.FTN - CTTS's companion
:41. WRITETAPE.LOD - link command file
:42. WRITETAPE_COMP.CMD - compile cmd file
:43. COUNT.REL
:44. CTT.REL
:45. CTT_DATA.REL
:46. CTT_SEG1.REL
:47. CTT_SEG2.REL
:48. CTT_SEG3.REL
:49. CTT_SEG4.REL
:50. CTT_WP51.DOC
:51. DEVICETYPE.REL
:52. DRIVERNAME.REL
:53. DRIVERNAMEDUMMY.REL
:54. EMACMW.REL
:55. FITSCHECK.REL
:56. FIX6ID.REL
:57. FIXAID.REL
:58. FORMATCHECK.REL
:59. GET6SHEMATABLE.REL
:60. GETASHEMATABLE.REL
:61. GETNEXTFILE.REL
:62. HELP.REL
:63. INSERT.REL
:64. LIST.REL
:65. LOGDEVICE.REL
:66. POSINPUTTAPE.REL
:67. POSOUTPUTTAPE.REL
:68. REPORTFMPERROR.REL
:69. SENDMSG.REL
:70. SHOW.REL
:71. WRITETAPE.REL
Operating System(s)......: RTE-6/VM, RTE-A
Language(s)..............: FTN7X, MACRO
Keywords.................: 1. Magnetic_tape
: 2. Copy
: 3. Files
External Support Req'd...:
If Re-submission, Reason.: Now also handles Exabyte
Contributor's Name..........: Eric Allaert
Company.......: European Southern Observatory
Street........: Casilla 19001
City..........: Santiago 19
State.........:
Country.......: Chile
Zip Code......:
Phone Number..: [56]-(2)-6954263
Telex.........: 240881 ESOGO CL
Contribution Abstract.......:
This Copy-Tape-to-Tape program has been developed in-house to cover our
high demands on tape copying. CTT allows you to extract files from one
tape and put them on up to 9 output tapes simultaneously. CTT can select
files by their positional number on input and output tapes, append to
output tapes, set the density of HP tape streamers, log its messages to
any file/device, run other programs, and so on. It also does a very good
job in verifying the copied files against the original tape. CTT can
alternatively compare tapes without writing on them. Commands can be
given interactively or taken from a command file.
CTT is a direct tape-to-tape copier, i.e. there are no scratch disc files
involved. It does however use a lot of RTE resources. The result is a
verrrry fast tape copy program.
Use INSTALL.CMD to bring CTT to life, and pay attention to any comments
this command file will spit out. CTT has on-line help, and error/warning
messages help cure eventual problems quickly. Try it, you'll love it.
A word of warning: CTT might need some modifications when RTE-A 6.0 is
released, as there will be extensions to EMA/VMA for the A990 which may
affect CTT. An excellent description of EMA/VMA for RTE-A can be found
in the August and November 1991 issues of "REAL-TIME INTERFACE".
Additional Documentation....:
See CTT_WP5P1.DOC, a 28 page document in WordPerfect 5.1 format.
S01901
-----------------------------------------------------------------------------
R_CLIENT S019
PROVIDE BSD IPC CLIENT-SERVER PAIR
-----------------------------------------------------------------------------
Contribution Name...........: R_CLIENT
Title....................: Provide BSD IPC client-server pair
File Names...............:00. Rename Transfer File
:01. R_CLIENT.SBMT
:02. INSTALL.CMD Installation file
:03. R_CLIENT.DOC Documentation
:04. R_CLIENT.FTN Main program
:05. R_CLIENT.REL Main relocatable
:06. R_CLIENT.LOD Link command file
:07. R_CLIENT.CMD Installation commands
:08. R_CLIENT.CF Example /etc file
:09. R_SERVER.TAR TAR file for HPUX end
Operating System.........: RTE-A
Uses hierarchical files?.: yes
Language(s)..............: Fortran, C (files for HP-UX only)
Keywords.................: 1. system
: 2. network
External Support Req'd...: BSD IPC
If Re-submission, Reason.:
Contributor's Name..........: F. Stephen Gauss
Company.......: U.S. Naval Observatory
Street........: 3450 Massachusetts Ave. NW
City..........: Washington
State.........: DC
Country.......: USA
Zip Code......: 20392-5400
Phone Number..: 202-653-1510
: Internet: fsg@sicon.usno.navy.mil
Program Abstract............: r_client runs on RTE-A, r_server runs
on HP-UX. This allows the 1000 to display information from the HP-UX
system. The services are provided using Berkeley Sockets. Commands that
can be given on the 1000 include nslookup, man and bdf.
Included here are a set of files for r_client and a tar file for r_server
to be moved to an HP-UX system.
Additional Documentation....: see r_client.doc
See also my submission of whozn which operates in a similar fashion and
displays who is logged on.
S02001
-----------------------------------------------------------------------------
WHOZN-RTE S020
WHO IS LOGGED ON - RTE VERSION
-----------------------------------------------------------------------------
Contribution Name...........: WHOZN-RTE
Title....................: Who is logged on - RTE version
File Names...............:00. Rename Transfer File
:01. WHOZN.SBMT
:02. WHOZN.FTN Main program
:03. WHOZN.REL Main relocatable
:04. UIDSL.FTN Slave program
:05. UIDSL.REL Slave relocatable
:06. WHOZN_F_LIB.FTN Fortran library
:07. WHOZN_F_LIB.REL
:08. WHOZN_M_LIB.MAC Macro library
:09. WHOZN_M_LIB.REL
:10. UID_NODE.FTN UID node access
:11. UID_NODE.REL
:12. UIDGET_6.FTN UID for RTE-6
:13. UIDGET_6.REL
:14. UIDGET_A.MAC UID for RTE-A
:15. UIDGET_A.REL
:16. BSD_WHZND.FTN Calls BSDWHOZN for sockets
:17. BSD_WHZND.REL
:18. WHOZN.LOD WHOZN load file
:19. UIDSL.LOD UIDSL load file
:20. TERMINALS Sample terminals file
:21. WHOZN.DOC Documentation
:22. node_dummy.ftn
:23. node_dummy.rel add to .lod file if no DS
:24. get_special.ftn allow special logon
:25. get_special.rel
:26. is_tn.ftn SEE SOURCE - Needs values
:27. BSDWHOZN.FTN | Load only if you use BSD
:28. BSDWHOZN.REL | sockets.
:29. BSDWHOZN.LOD |
:30. WHZND.FTN | BSD sockets daemon
:31. WHZND.REL |
:32. WHZND.LOD |
:33. IS_TN.REL
Operating System.........: RTE-6VM and RTE-A
Uses hierarchical files?.: yes
Language(s)..............: Fortran, Macro
Keywords.................: 1. logon/logoff
: 2. network
External Support Req'd...: HPC.LIB
If Re-submission, Reason.: updated from CSL 3226: Rev 3.2
Contributor's Name..........: F. Stephen Gauss
Company.......: U.S. Naval Observatory
Street........: 3450 Massachusetts Ave. NW
City..........: Washington
State.........: DC
Country.......: USA
Zip Code......: 20392
Phone Number..: 202-653-1510
: Internet: fsg@sicon.usno.navy.mil
Program Abstract............: Displays the log-on name and LU for
each person logged on and can show their physical location.
Runs on RTE-A, RTE-6 and HP-UX. Also operates
across network link using DS 1000/IV services to other 1000's and using BSD
sockets to HPUX systems. This compensates for the lack of rwho on RTE.
Additional Documentation....: see WHOZN.DOC
S02101
-----------------------------------------------------------------------------
WHOZN-HPUX S021
WHO IS LOGGED ON - HPUX VERSION
-----------------------------------------------------------------------------
Contribution Name...........: WHOZN-HPUX
Title....................: Who is logged on - HPUX version
File Names...............:00. Rename Transfer File
:01. whozn.sbmt
:02. whozn.copy copies these files to proper
directories
:03. whozn Main script (ksh)
:04. whoplace.ftn aux program for whozn
:05. whoplace executable (700)
:06. whoform.ftn aux program for whozn
:07. whoform executable (700)
:08. places terminal location file
:09. whoznd.c whozn daemon source
:10. whoznd executable (700)
:11. rwhozn.c whozn program for remote host
:12. rwhozn executable (700)
:13. whoznd.sh script run by whoznd
:14. whozn.doc Documentation
Operating System.........: HP-UX
Language(s)..............: Fortran 77, C
Keywords.................: 1. logon/logoff
: 2. network
External Support Req'd...:
If Re-submission, Reason.:
Contributor's Name..........: F. Stephen Gauss
Company.......: U.S. Naval Observatory
Street........: 3450 Massachusetts Ave. NW
City..........: Washington
State.........: DC
Country.......: USA
Zip Code......: 20392-5420
Phone Number..: 202-653-1510
: Internet: fsg@sicon.usno.navy.mil
Program Abstract............: Displays the log-on name and LU for
each person logged on and can show their physical location.
Runs on HP-UX. Also operates across network link using BSD
sockets to RTE systems. This compensates for the lack of rwho on RTE.
All files go on /usr/local/bin except the places file.
Additional Documentation....: see WHOZN.DOC
S02201
-----------------------------------------------------------------------------
SAMFO S022
A PROGRAM TO MONITOR SAM AND XSAM
-----------------------------------------------------------------------------
Contribution Name...........: SAMFO
Title....................: A program to monitor SAM and XSAM
File Names...............: 00. rename transfer file
: 01. SAMFO.SBMT
: 02. SAMFO.FTN
: 03. SAMFO.HLP
: 04. SAMFO.MAKE
: 05. SAMFO.DOC
Operating System.........: RTE-A
Language(s)..............: FTN7X
Keywords.................: 1. System
: 2. MONITOR
External Support Req'd...: None
If Re-submission, Reason.:
Contributor's Name..........: Jim Cox
Company.......: Cox Computer Consultants Ltd
Street........: Burwell Farmhouse
City..........: Witney
State.........: Oxfordshire
Country.......: England
Zip Code......: OX8 7LA
Phone Number..: 0993 705070
Fax Number....: 0993 705092
Contribution Abstract.......: SAMFO monitors the level of SAM and
XSAM and will display a warning message if the level of free SAM or
XSAM falls below a specified level.
Additional Documentation ...: None
S02301
-----------------------------------------------------------------------------
WHOSE S023
IDENTIFY OWNERS OF A DIRECTORY MASK
-----------------------------------------------------------------------------
Contribution Name...........: WHOSE
Title....................: Identify owners of a directory mask
File Names...............:00. rename file
:01. WHOSE.SBMT
:02. WHOSE.FTN
:03. WHOSE.HLP
:04. WHOSE.MAKE
:05. WHOSE.DOC
Operating System.........: RTE-A
Language(s)..............: FTN7X
Keywords.................: 1. LIST
: 2. DISPLAY
: 3. DIRECTORY
External Support Req'd...: None
If Re-submission, Reason.:
Contributor's Name..........: Jim Cox
Company.......: Cox Computer Consultants Ltd
Street........: Burwell Farmhouse
City..........: Witney
State.........: Oxfordshire
Country.......: England
Zip Code......: OX8 7LA
Phone Number..: 0993 705070
Fax Number....: 0993 705092
Contribution Abstract.......: The standard OWNER command in CI will
only display the ownership of individual directories, this program
allows the use of a file mask to select the directories required
and outputs the result to the screen or to a file. The output is
formatted to resemble the OWNER command so that it can be modified
and used as a command file to change ownership. Ideal if users have
been deleted and left the ownership as unknown.
Additional Documentation .....: None
S02401
-----------------------------------------------------------------------------
ENV S024
GLOBAL ENVIRONMENT VARIABLES
-----------------------------------------------------------------------------
Contribution Name...........: ENV
Title....................: Global environment variables
File Names...............:00. Rename Transfer File (Interex-supplied)
:01. ENVIRONMENT.SBMT
:02. ENVIRONMENT.FTN
:03. ENVIRONMENT.REL
:04. HPC_ENVIRONMENT.FTN
:05. HPC_ENVIRONMENT.REL
:06. ENVIRONMENT.LOD
:07. ENVIRONMENT.VARS
:08. INSTALL.CMD
:09. MAKEFILE.MAKE
:10. EXAMPLE.CMD
:11. ACCESS_ENV.FTN
:12. ACCESS_ENV.REL
:13. ACCESS_ENV.LOD
Operating System(s)......:RTE-A
Language(s)..............:FTN7X
Keywords.................: 1. CI
: 2. GLOBALS
: 3. SYSTEM
External Support Req'd...:
If Re-submission, Reason.:
Contributor's Name..........: Larry Ridgley
Company.......: Hewlett-Packard, 1BS-C
Street........: 1412 Fountaingrove Parkway
City..........: Santa Rosa
State.........: CA
Country.......: USA
Zip Code......: 95403
Phone Number..: (707) 577-2155
Fax Number....: (707) 577-4771
Contribution Abstract.......:
This program is used to create and manipulate global "environment"
variables contained in a central file. Access to the variables is
possible from CI as shown (see ACCESS_ENV.FTN for programmatic
access example):
RU,ENV,variable -Returns value in $RETURN_S
RU,ENV,variable,=,value -Sets variable to value; if value
contains spaces, enclose in ` `.
RU,ENV,?? -Get help
RU,ENV,-l -List all variables
I use this program to allow "generic" systems to be created with
system-specific variables kept in the /SYSTEM/ENVIRONMENT.VARS file.
The data for each specific system cloned from the generic system is
edited into this file on each seperate system.
I access the variable name(s) from various command files and use the
value(s) to properly set up system values, primarily at bootup. Some
good examples are the local system NS-ARPA/1000 nodename & IP address:
I use EDIT pattern-matching & variable substitution to batch edit a copy
of a template file that replaces the NSINIT.ANS file used by the NSINIT
program to initialize NS-ARPA/1000 on each RTE-A system.
I have not tried this program with RTE-6V/M but it should work.
Additional Documentation....: See source code.
S02501
-----------------------------------------------------------------------------
WALL S025
WRITE TO ALL USERS
-----------------------------------------------------------------------------
Contribution Name...........: WALL
Title....................: Write to all users
File Names...............:00. Rename Transfer File (Interex-supplied)
:01. WALL.SBMT
:02. WALL.FTN
:03. WALL.REL
:04. WALL.LOD
:05. MAKEFILE.MAKE
:06. HPC_WRITETOUSER.FTN
:07. HPC_WRITETOUSER.REL
Operating System(s)......: RTE-A
Language(s)..............: FTN7X
Keywords.................: 1. SYSTEM
: 2. MANAGEMENT
: 3. MESSAGE
External Support Req'd...:
If Re-submission, Reason.:
Contributor's Name..........: Larry Ridgley
Company.......: Hewlett-Packard, 1BS-C
Street........: 1412 Fountaingrove Parkway
City..........: Santa Rosa
State.........: CA
Country.......: USA
Zip Code......: 95403
Phone Number..: (707) 577-2155
Fax Number....: (707) 577-4771
Contribution Abstract.......:
This program is used to write messages to all logged-on users
(similar to UN*X version). The module HPC_WriteToUser may also be
called programmatically. Usage:
RU,WALL,`Text string` -Sends text as shown (` `'s needed)
RU,WALL,<filename -Sends text file (leading '<' is required)
Additional Documentation....: See source code.
S02601
-----------------------------------------------------------------------------
SHUTDOWN S026
REBOOT OR HALT SYSTEM
-----------------------------------------------------------------------------
Contribution Name...........: SHUTDOWN
Title....................: Reboot or Halt System
File Names...............:00. Rename Transfer File (Interex-supplied)
:01. SHUTDOWN.SBMT
:02. SHUTDOWN.FTN
:03. SHUTDOWN.REL
:04. SHUTDOWN.LOD
:05. MAKEFILE.MAKE
:06. HPC_WRITETOUSER.FTN
:07. HPC_WRITETOUSER.REL
:08. HPC_REBOOT.MAC
:09. HPC_REBOOT.REL
Operating System(s)......: RTE-A
Language(s)..............: FTN7X
Keywords.................: 1. SYSTEM
: 2. BOOT-UP
External Support Req'd...:
If Re-submission, Reason.:
Contributor's Name..........: Larry Ridgley
Company.......: Hewlett-Packard, 1BS-C
Street........: 1412 Fountaingrove Parkway
City..........: Santa Rosa
State.........: CA
Country.......: USA
Zip Code......: 95403
Phone Number..: (707) 577-2155
Fax Number....: (707) 577-4771
Contribution Abstract.......:
This program is designed to allow the system manager to reboot or
halt the system. Reboot can be done remotely, but halt (which gives
the VCP> prompt) must be done at the console. This version is similar
to the UN*X program of the same name. Usage is as follows:
RU Shutdown -h | -r [-y] [grace]
Running SHUTDOWN with no parameters displays help screen.
NOTE: I have included the HPC_WriteToUser module that is part of the
WALL program, since it is used by SHUTDOWN as well.
Additional Documentation....: See source code
S02701
-----------------------------------------------------------------------------
TMAP S027
PROG. TO HELP WITH CS/80 TRACK MAP BUILDING
-----------------------------------------------------------------------------
Contribution Name...........: TMAP
Title....................: Prog. to help with CS/80 track map building
File Names...............:00. Rename Transfer File (Interex-supplied)
:01. TMAP.SBMT
:02. TMAP.FTN
:03. TMAP.REL
:04. TMAP.LST
Operating System(s)......: RTE-6/VM, RTE-A
Language(s)..............: FORTRAN
Keywords.................: 1. SYSTEM
: 2. GENERATION
: 3. CS80
External Support Req'd...: NONE
If Re-submission, Reason.:
Contributor's Name..........: Mark F. Allen
Company.......: U. S. Air Force
Street........: OO-ALC/TISAB
City..........: Hill AFB
State.........: UTAH
Country.......: USA
Zip Code......: 84056
Phone Number..: (801) 775-2865
Fax Number....:
Contribution Abstract.......: This is a crude simple program to help you
when you are building a CS/80 track map that is non-standard for RTE-A or
are building a track map for RTE-6/VM for a NON-SYSTEM disc or 2nd CS/80
disc drive interface.
Additional Documentation....: This program simply asks for the TOTAL number
of blocks on the drive and then asks for the number of tracks and number
of blocks per track for each sub-channel and displays the STARTING BLOCK
number for each sub-channel. This is useful when trying to handle
conversion of 32 bit starting block numbers to two 16 bit words.
S02801
-----------------------------------------------------------------------------
CONVERT S028
PROG TO CONVERT BASIC TYPE 4 TO/FROM TYPE 10
-----------------------------------------------------------------------------
Contribution Name...........: CONVERT
Title....................: Prog to convert basic type 4 to/from type 10
File Names...............:00. Rename Transfer File (Interex-supplied)
:01. CNVRT.SBMT
:02. CNVRT.FTN
:03. CNVRT.REL
:04. CNVRT.LST
Operating System(s)......: RTE-4A/4B,RTE-6/VM, RTE-A
Language(s)..............: FORTRAN
Keywords.................: 1. CONVERSION
: 2. BASIC
External Support Req'd...: BASIC 1000/D or BASIC 1000/L
If Re-submission, Reason.:
Contributor's Name..........: Mark F. Allen
Company.......: U. S. AIR FORCE
Street........: OO-ALC/TISAB
City..........: HILL AFB
State.........: UTAH
Country.......: USA
Zip Code......: 84056
Phone Number..: (801) 775-2865
Fax Number....:
Contribution Abstract.......: This is a utility program to aid in converting
large numbers of BASIC/1000D or BASIC/1000L programs from TYPE 10
interpretive code to source code TYPE 4 files or the reverse.
Additional Documentation....: This program works ONLY with BASIC files and
hence is coded for ONLY FMGR files. The FMGR disc directory can be scanned
to find all the files to convert, or optionally you may specify the BASIC
file name as B##### that is B followed by a 5 digit number and the program
will process one or more files as specified. See the Fortran source code
for any additional information on how the program works. We have
sucessfully used this program to convert large numbers of ATE test programs
from interpretive code to source code for conversion and loading on new
test systems.
S02901
-----------------------------------------------------------------------------
CALLS DATABASE S029
HELP FILE FOR SUBROUTINE CALLS
-----------------------------------------------------------------------------
Contribution Name...........: CALLS Database
Title....................: Help file for subroutine calls
File Names...............:00. Rename Transfer File
:01. calls_db.sbmt
:02. base_rte_calls.txt
:03. callm.ftn
:04. callm.lod
:05. calls_db.make
:06. commentline.mac
:07. fmgr_commands.txt
:08. fmp_calls.txt
:09. hpcrt.txt
:10. insert.mac
:11. other_rte_calls.txt
:12. rte.cmrg
:13. vis_calls.txt
:14. antlb.lib
:15. install.doc
Operating System(s)......: RTE-A
Language(s)..............:
Keywords.................: 1. Help
External Support Req'd...:
If Re-submission, Reason.: Support for HP's CALLS utilitiy
Contributor's Name..........: Paul Schumann
Company.......: E-Systems, Inc.
Street........: 1200 S. Jupiter Rd.
City..........: Garland
State.........: Texas
Country.......: USA
Zip Code......: 75042
Phone Number..: (214) 205-5356
Telex.........:
Contribution Abstract.......: CALLS is an interactive help program for
standard HP subroutines and system calls. It gives you the format,
parameter list, etc. for most calls.
For, example, CALLS,EXEC(3 shows how to use an EXEC control call.
This is a re-submission of Alan Tibbetts' CALLS contribution with some
very important and major changes -- the CALLS utility itself is not
included here because H-P is supplying it as of revision 5.26 of RTE-A
(DEBUG/1000) and possibly RTE-6. Because H-P's CALLS works a little
differently than Alan's, some changes were required.
The calls and base-page information which apply to RTE-6 only have been
removed from the BASE_RTE file and, to some extent, from the FMP_CALLS
file. I hope you don't miss them. I have added some of the newer calls
to these files, however, so maybe it all balances out. I intend, as I
find the time, to continue adding definitions to the calls database
files; perhaps it will be complete for the next regular CSL release.
Additional Documentation....: see Install.Doc
S03001
-----------------------------------------------------------------------------
BSDTIMESYNC S030
SYNCHRONIZE NETWORKED SYSTEM TIMES
-----------------------------------------------------------------------------
Contribution Name...........: BSDTIMESYNC
Title....................: SYNCHRONIZE NETWORKED SYSTEM TIMES
File Names...............:00. Rename Transfer File
:01. BSDTIME.SBMT submit file
:02. TIMESRV.LOD
:03. TIMECHECK.LOD
:04. TIMESRV.FTN
:05. TIMECHECK.FTN
:06. README
:07. SHAR
Operating System.........: RTE-A 5.24 & 5.27 / HP-UX 7.0 & 8.0
Uses hierarchical files?.: YES
Language(s)..............: FORTRAN,C
Keywords.................: 1. TIME
: 2. SOCKETS
: 3. NETWORK
External Support Req'd...: BERKELEY SOCKETS & TCP
If Re-submission, Reason.:
Contributor's Name..........: Wendy King, Richard Schmidt
Company.......: U.S. Naval Observatory
Street........: 3450 Massachusetts Ave. NW
City..........: Washington
State.........: DC
Country.......: USA
Zip Code......: 20392-5420
Phone Number..: 202-653-0486 wendy@newton.usno.navy.mil
Phone Number..: 202-653-0487 res@tuttle.usno.navy.mil
Program Abstract............: These programs use BSD IPC (tcp) to send or
receive time across a network between systems which support "Berkeley
sockets". The Timesrv responds to connection requests from Time_Set or
TimeCheck by sending the current system time in seconds since 01/01/1970.
These programs can be used to sychronize networked system times to
within one or two seconds, depending on the particular network environment.