This document contains an overview of the public parameter group UNIT, (part of) which is included in several NEWSTAR programs.
The document describes the individual parameters in alphabetical order. This description centers on the Help texts, which have been designed to guide the user to the proper choice at each junction, even if his knowledge of the overall workings of the program is only superficial.
Please note that the generic prompt and help texts defined for these parameters are frequently superseded in the actual applications by alternative texts that are more appropriate to the situation at hand. Unfortunately, the present architecture of NEWSTAR precludes the inclusion of such texts in the documentation system, so the only opportunity to read that information is during program execution (in your terminal window!).
Prompt: input 'tape' unit: number or 'D' for 'disk' | (may vary per application)
Expected input: Character *1: 1 value
Specify the input unit for your data:
0,..9 Tape/optical disk/DAT unit D Disk
The correspondence between the unit numbers and the devices on your host machine is defined by the environment variables MAG<n>. The list below shows the values with which NEWSTAR is distributed, but your local installation may be different, so you do wello to check with your local site manager
classic 0.5-inch magtape: 0 1600 bpi 1 6250 bpi 2 800 bpi
optical disk, formatted as a magtape: 4 5
DAT, ExaByte or similar tape: 6 7 8 9
You may enter '*' to get a list of unit numbers available for you, but this will not tell you to what physical devices these correspond.
Prompt: output 'tape' unit: number or 'D' for 'disk' | (may vary per application)
Expected input: Character *1: 1 value
Specify the input unit for your data:
0,..9 Tape/optical disk/DAT unit D Disk
The correspondence between the unit numbers and the devices on your host machine is defined by the environment variables MAG<n>. The list below shows the values with which NEWSTAR is distributed, but your local installation may be different, so you do wello to check with your local site manager
classic 0.5-inch magtape: 0 1600 bpi 1 6250 bpi 2 800 bpi
optical disk, formatted as a magtape: 4 5
DAT, ExaByte or similar tape: 6 7 8 9
You may enter '*' to get a list of unit numbers available for you, but this will not tell you to what physical devices these correspond.
Prompt: Output volume name (may vary per application)
Expected input: Character *6: 1 value
Specify the full name for the output volume.
This name is used for the administration in MEDIAD
Prompt: Overwrite (YES/NO) (may vary per application)
Expected input: Yes/No: 1 value
Specify if one wants to overwrite the current label (YES) or not (NO).
BEWARE: All subsequent labels will also be overwritten.
Prompt: 'tape' unit: number or 'D' for 'disk' | (may vary per application)
Expected input: Character *1: 1 value
Specify the input unit for your data:
0,..9 Tape/optical disk/DAT unit D Disk
The correspondence between the unit numbers and the devices on your host machine is defined by the environment variables MAG<n>. The list below shows the values with which NEWSTAR is distributed, but your local installation may be different, so you do well to check with your local site manager
classic 0.5-inch magtape: 0 1600 bpi 1 6250 bpi 2 800 bpi
optical disk, formatted as a magtape: 4 5
DAT, ExaByte or similar tape: 6 7 8 9
You may enter '*' to get a list of unit numbers available for you, but this will not tell you to what physical devices these correspond.
Prompt: Abbreviated medium type (may vary per application)
Expected input: Character *4: 1 value
Specify the type for the output volume.
This name is used for the administration in MEDIAD
DOD - DEC Optical Disk DAT - Digital Audio Tape 800 - 9-track tape, 800 bpi 1600 - 9-track tape, 1600 bpi 6250 - 9-track tape, 6250 bpi
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.