1 01/08/87  patch_deck, pd
 2 
 3 
 4 Syntax as a command:  pd {key}
 5 
 6 
 7 Function:  add or delete $patch cards to a deck in a tandd_deck_file .
 8 
 9 
10 Arguments:
11 KEY
12    is a key obtained by the user from a deckfile.list which identifies
13    a particular deck in a tandd_deck_file.
14 
15 
16 Control arguments:
17 -brief, -bf
18    suppresses messages from deckfile_manager announcing the
19    deckfile.list and tandd_deck_file that will be used for this
20    request.
21 -deckfile deckfile_path, -df deckfile_path
22    specifies that the deckfile_path is the target deckfile to be used
23    for this requests.
24 -delete, -dl
25    will query the user for deletion of all patches encountered in a
26    specified deck.
27 
28 
29 
30 Notes:  If the add patch function is requested, the user will be
31 queried as to the type of patch (octal or hex) and then for the patch
32 data.
33 
34 
35 
36 Notes on deckfile_path:  If the deckfile_path is not given on the
37 request line then the following sequence is used.  If a deckfile_path
38 is entered in the deckfile_manager command line, it is used.  Otherwise
39 the current working_dir is searched for an entry, if one is found the
40 user is notified of its use.  If an entry is not found and the user has
41 sufficient effective access, the user is queried as to the creation of
42 the tandd_deck_file or deckfile.list.  If the reply is no and the user
43 has sufficient effective access to modify the tandd_deck_file in
44 >system_library_tandd, the user is again query as to its usage.  If no
45 tandd_deck_file is found the command is aborted.
46 
47 
48 
49 Notes on key:  key is unique identifier for each file in a
50 tandd_deck_file and may be up to 24 characters in length.  If no key is
51 supplied the user will be requested to supply one.  The key may be
52 obtained from a deckfile.list and can be inputted as either a complete
53 or partial key.  If a partial key is supplied the user is queried for
54 each match of the given key.