2.9 What are some of the differences between the legacy (MPE V) LISTF command and the MPE?iX LISTFILE command?

From Jeff Vance:

A LISTFILE and LISTF of the same filesets do not always produce the same output. E.g. in a job, LISTF shows a date/time stamp and LISTFILE doesn't. Also "LISTF,2" will display '(CONTINUED)' when greater than 58 lines of output have been shown for the same group, but LISTFILE doesn't.

LISTFILE has different formats for Posix vs. MPE named filesets. E.g. LISTFILE /SYS/PUB/@,2 has a different format from LISTFILE @.pub.sys,2 . Also, all Posix style formats are shifted right one byte to allow visual inspection of wrapped around (long) filenames. I have mixed thoughts about this design choice. Probably in hindsight I would choose to not do it this way.

LISTF does not support Posix-named files; however you can do a LISTF from a Posix directory and see Posix style formats. E.g.,

:CHDIR ./dir (or to any location different than your logon group)

:LISTF @,2 (see Posix style output)

[Editor's note: LISTFILE also supports options (such as "ACCESS") that LISTF does not support. In general, if you are new to MPE, get in the habit of using LISTFILE. And, if you are an old-timer like me, try to break yourself of the LISTF habit and re-train yourself to use LISTFILE.]