So far, we have:
(I would like to add some examples and variations - but this is a good start!)
----------------
(Thanks to Chris Rice From the 4.5 class:)
ABORTJOB kill
ALTACCT chmod
ALTGROUP chmod
ALTSEC chmod
BYE exit
CALC expr, bc
CCXL c89
CCXLLK c89
CHGROUP cd
CI sh
CI callci
COPY cp
DISALLOW chmod
DO r
ECHO echo
EDITOR vi
ELSE else
ENDIF fi
ENDWHILE done
EXIT exit
FCOPY cp, dd, lp
FILE ln
HELP help, man
HPDESK mailx
HPSEARCH grep
IF if
LINK c89
LISTACCT ls -l
LISTEQ ls -l
LISTFILE ls
LISTGROUP ls -l
LISTREDO history
NEWACCT mkdir
NEWGROUP mkdir
PRINT more, cat
PURGE rm
PURGEACCT rmdir, rm
PURGEGROUP rmdir, rm
REDO r
RELEASE chmod 777
RENAME mv
REPORT,DISKUSE du, df, find
RESTORE tar, cpio, pax
SECURE chmod
SET set
SETDUMP set -x
SETJCW =
SETMSG mesg
SETVAR =
SHOWJCW echo
SHOWJOB ps, who
SHOWPROC ps
SHOWME pwd, uname
SHOWTIME date
SHOWVAR @ set
STORE tar, cpio, pax
STREAM at, batch, bg, crontab
TELL talk, write, mailx
WARN talk, write, mailx, wall
Mike Belshe notes:
------------------
I see two meanings for the FILE command: 1) Used to convert between
different file types. This has no meaning in the POSIX context because the
POSIX context really only understands one filetype - "bytestream". 2) Used
to associate one filesystem name to another filesystem name. This can be
done with the link (ln) command.
Dan Hollis Notes:
----------------
MPE: FILE DUMMY=DUMMY2 POSIX: ln -s DUMMY2 DUMMY
(note: this will place an actual file on the drive, e.g. a permanent file
equation so to speak. This is Posix symbolic linking of files.)
There is no reason you have to execute these commands from the posix shell.
E.g., LS.HPBIN.SYS "-al" works just fine from the CI; same as: "ls -al"
does from the Posix shell.
banner.hpbin.sys ":^)"
----------------------------------------------------------------
Eric J Schubert Senior Data Base Analyst
Admin Information Services Univ of Notre Dame, IN USA
(219) 631-7306 http://www.nd.edu/~eschuber
|