Pg. of GC20-1819-2 Rev March 30, 1979 by Supp. SD23-9024-1 for 5748-118 PROFILE, which causes it to be executed the first time you press the
Return key after loading CMS. EXECUTING YOUR PROFILE EXEC Usually, the first thing you do after loading CMS is to type a cas command. When you press the Return key to enter this command or if you
enter a null line, CMS searches your A-disk for a file with a filename
of PROFILE and a filetype of EXEC. If such a file exists, it is
executed before the first CMS command you enter is executed. Because
you do not do anything special to cause your PROFILE EXEC to execute,
you can say that it executes "automatically." You can prevent your PROFILE EXEC from executing automatically by
entering:
access (noprof)
as the first CMS command after you IPL CMS. You can enter:
profile
at any time during a CMS session to execute the PROFILE EXEC, if you had
accessed your A-disk without it, or if you had made changes to it and
wanted to execute it, or if you had changed ycur virtual machine and
wanted to restore its original characteristics. CMS EXECs and How to Use Them
A file named CMS EXEC is created when you use the EXEC option of the LISTFILE command; for example:
listfile pr* document a (exec
The usual display that results from this LISTFILE command is a list of
all the files on your A-disk with a filetype of DOCUMENT that have
filenames beginning with the characters "PR". eMS, however, creates a CMS EXEC file that contains a record for each file that would be listed.
The records are in the format:
&1 &2 filename filetype filemode Column 1 is blank. NOw, if you have the following files on your A-disk:
The
PRFILE1 DOCUMENT PRFILE2 DOCUMENT PRFILE3 DOCUMENT PRFILE4 DOCUMENT CMS EXEC file would contain
&1 &2 PRFILE1 DOCUMENT A1
&1 &2 PRFILE2 DOCUMENT A1
&1 &2 PRFILE3 DOCUMENT A1
&1 &2 PRFILE4 DOCUMENT A1
98 IBM VM/37C eMS User's Guide
the records:

Pg. of GC20-1819-2 Rev March 30, 1979 by Supp. SD23-9024-1 for 5748-XX8 In the preceding lines, &1 and &2 are variables that can receive values from arguments you pass to the EXEC when you execute it. For example,
if you execute this CMS EXEC by issuing:
cms disk dump
the EXEC interpreter substitutes, on each line, the variable &1 with the DISK and the variable &2 with DUMP and executes the commands: DISK DUMP PRFILE1 DOCUMENT A1 DISK DUMP PRFILE2 DOCUMENT A1 DISK DUMP PRFILE3 DOCUMENT A1 DISK DUMP PRFILE4 DOCUMENT A1 You can use this technique to transfer a number of files to another
user. You should remember to spool your punch with the CONT option
before you execute the EXEC, so that all of the files are transferred as
a single spool file; for example:
cp spool d cont library
Then, after executing the EXEC file, close the punch:
cp spool d nocont close
If you pass only one argument to your CMS EXEC file, the variable &2
is set to a null string. For example:
ems erase executes ERASE PRFILE1 ERASE PRFILE2 ERASE PRFILE3 ERASE PRFILE4 DOCUMENT A1 DOCUMENT Ai DOCUMENT A1 DOCUMENT A1 You could also use a CMS EXEC to obtain a listing of files on a
virtual disk. If you want, you can use one of the other LISTFILE command
options with the EXEC option to get more information about the files
listed. For example:
listfile * * a (exec date
produces a CMS EXEC that contains, in addition to the
filetype, and filemode of each file listed, the file format
and date information. You can then use the PRINT command to
printed copy:
print cms exec
filename,
and size,
obtain a
Before printing this file, you may want to use the SORT command to
sort the list into alphabetic order by filename, by filetype, or both;
for example:
sort cas exec a cmssort exec a When you are prompted to enter sort fields, you can enter:
1 25
The file CMSSORT EXEC that is created contains a completely alphabetical
list. Section 6. Introduction to the EXEC Processor 99