SO 'id
RGII State
MICROSYSTEMS
User Manual for the
RCA MicroDisk Development System
MS2000
MPM-241
Suggested Price $5.00
User Manual for the
RCA MicroDisk Development System
MS2000
noI"
Solid I Somerville, NJ • Brussels • Paris • London
• • State Hamburg. Sao Paulo • Hong Kong
CLASS A
RADIO INTERFERENCE WARNING
This equipment complies with the requirements in Part 15 of
FCC Rules for a Class A computing device. Operation of this
equipment in a residential area may cause unacceptable
interference to radio and TV reception requiring the operator
to take whatever steps are necessary to correct the
interference.
2488834-1
The software described In this manual Is copyrighted by RCA Corporation.
Information furnished by RCA is believed to be accurate and reliable. However, no responsibility is
assumed by RCA for its use; nor for any infringement
of patents or other rights of third parties which may
result from its use. No license is granted by implication or otherwise under any patent or patent rights of
RCA.
Tradmark(s)® Registered
Marca(s) Registrada(s)
Copyright 1984 by RCA Corporation
(All rights reserved under Pan-American Convention)
Printed in USA 5-84
3
Foreword
The RCA MicroDisk Development System MS2000 is a microprocessor computer system designed to facilitate the development of
hardware and software for applications based on the RCA 1800 series
of CMOS microprocessors. It utilizes 3-~ inch, high-density microfloppy disk drives. The disks provide 645 kilobytes of on-line mass
memory storage. Featuring higher speeds than its predecessors, the
MS2000, with its new DMA controller, has reduced system load time
to 0.6 second.
The MicroDisk Development System is contained in a 20-s10t Microboard Industrial Chassis containing not only the four Microboards
provided, but also the power supply and the complete Dual Microfloppy Disk Drives. The chassis provides four additional spare slots for
expansion and enhancements with any of the extensive line of RCA
Microboards.
The memory includes 632 kilobytes of RAM, 2 kilobytes of ROM,
and 645 kilobytes of on-line mass memory storage on microfloppy
disks. Software provided includes an augmented resident monitor
program UT71 and the MicroDOS operating system. MicroDOS
includes an Editor and a MacroAssembler ASM8 that operates not
only with all the RCA CMOS Microprocessors CDPI802A,
CDPI805AC, CDPI806C, and CDPI806AC, but with RCA Microprocessors to be added to the expanding line.
Conversion programs are included that provide transportability of
source code from all other RCA Development Systems to the MS2000.
Optional add-ons include a PROM Programmer package, BASICI,
BASIC2, the CDPI8S040 CRT Terminal providing full-screen editing, and the MS3001 MicroEmulator.
This Manual describes in detail the hardware structure and the
software features and commands of the MicroDisk Development System MS2000. The user should also refer to the User Manualfor the
CD P1802 Microprocessor, MPM-20 I, for a detailed description ofthe
instruction set and the architecture of the CDPI802 CMOS Microprocessor.
5
CONTENTS
Page
System Structure and Set-up .................... 8
Chassis .................................... 8
Microboard Computer ....................... 9
Microboard Memories ....................... 9
MicroboardDisk Controller .................. 10
Dual Disk Drives .......................... 10
Power Supply ............................. 10
System Set-up ............................. 11
Monitor Program Check .................... 11
Disk Operation Check ...................... 11
Page
MERGE .................................. 27
PERTEC ................................. 28
PRINT ................................... 29
PROM25 ................................. 29
RENAME ................................ 29
SUBMIT ................................. 30
SySGEN ................................. 34
TAPED .................................. 37
U ........................................ 37
VERIFy ................................. 37
Understanding MicroDOS ..................... 13
Introduction .............................. 13
MicroDOS System Ingredients ............. 13
Files and File Names ..................... 13
Diskettes and Diskette Handling ............ 14
Memory Requirements .................... 14
Utility Program UTI 1 .................... 15
Peripheral Devices ....................... 15
Program Creation and Translation .......... 15
How MicroDOS Operates ................... 15
Resource Management .................... 15
Device Name Format ................... 15
File Name Format ..................... 15
"Wild-Card" Construct .................. 16
Referencing Files ....................... 16
Development Station Console ............ 16
Command Intepreter ..................... 16
Command Format ..................... 16
Error Messages ........................ 17
Diskette File Management ............... 17
File Types ............................ 17
File Attributes ......................... 17
Diskette Structure ........................ 18
MicroDOS Commands ................... 18
User Program Generation ..................... 39
Case 1 .................................... 39
Case 2 .................................... 39
Case 3 .................................... 40
MicroDOS Command Descriptions ............. 19
CDSBIN ................................. 19
CONASM ................................ 20
COpy ................................... 20
DEL ..................................... 21
DIAG .................................... 22
DIR ..................................... 22
EXAM ................................... 24
FRMT ................................... 26
FREE .................................... 26
HELP .................................... 26
MEM .................................... 27
MEMTST ................................ 27
Disk Editor ................................. 41
Introduction .............................. 41
Operating Instructions ...................... 42
Memory Space Requirements ............. .42
Input and Output Files ................... .42
Record Formats ......................... 42
Buffer Pointer ........................... 43
EDIT Command Operation .................. 44
Command Strings ........................ 44
Command Formats ....................... 44
Correcting Command Typing Errors ........ 44
Interrupting EDIT Execution .............. 45
Filled Workspace Warning ................ 45
File Assignments ......................... 45
EDIT Commands - Single ................... 45
Pointer Control Commands ................ 45
BEGINNING ......................... 45
END OF BUFFER .................... 45
CHARACTER STEP .................. 46
LINE STEP ........................... 46
TYPE LINE NUMBER ................. 46
File ManipUlation Commands .............. 46
INPUT FILE SELECTION ............. 46
OUTPUT FILE SELECTION ........... 46
APPEND ............................. 46
NEXT ............................... 46
MERGE FILE ........................ 46
Deletion Commands ...................... 47
DELETE ............................. 47
KILL ................................ 47
Text Insertion and Data Manipulation ....... 47
INSERT .............................. 47
SAVE ................................ 47
6
User Manual for the RCA MicroDisk Development System MS2000
Page
GET ................................. 47
FIND ................................ 47
SUBSTITUTE ........................ 47
Output Commands ....................... 47
TyPE ................................ 47
PRINT ............................... 47
TYPE EDITOR STATUS ............... 47
WRITE and DELETE ................. .47
END ................................. 48
FILE CLOSE ......................... 48
QUIT EDIT SESSION ................. 48
RETURN TO UTILITY PROGRAM .... .48
Summary of Commands and Control
Characters ............................ 48
EDIT Commands - Composite ............... 49
Horizontal Tabs ........................... 51
Additional Note ......................... 51
File Development and Manipulation .......... 51
Creating a File ........................... 51
Adding to a File ......................... 52
Deleting a Section in a File ................ 52
Moving a Section in a File ................. 52
Modifying a Section in a File .............. 53
Some Command Examples ................ 53
File Manipulation Summary ................. 53
Creating a New File ...................... 53
Changing an Existing File ................. 53
Disk Assembler (AS8) ........................ 55
Assembler Operation ....................... 55
Backus-Naur Format (BNF) ................. 56
Basic Definitions ........................... 57
Character Set ............................ 57
Character Strings, Identifiers, and Labels ..... 57
Constants ............................... 57
Keywords ............................... 58
Level I Assembly Language .................. 58
Line and Statements ...................... 58
Expression Evaluation .................... 58
Arithmetic Expressions .................... 58
Relational Expressions .................... 59
Logical Expressions ...................... 59
Bitslice Expressions ....................... 59
Limitations ............................. 60
Executable Statements: Level I ............. 60
First Class Instructions .................... 60
Second Class Instructions ................. 60
Third Class Instructions ................... 60
Fourth Class Instructions .................. 60
Macro Call Statement .................... 60
Directives ............................... 61
Minor Statement. ........................ 61
Sample Program Level I .................. 61
Page
Major Statements ........................ 61
Status Statements ........................ 61
Conditional Assembly Statements ........... 62
Sample Program - Major Statements ........ 64
Level II Assembly Language ................. 64
Executable Statements: Level II ............ 64
Substitution Instructions ................ 64
D-Sequence Instructions ................ 65
Sample Program Illustrating D-Sequences. 67
Macros and Their Use ...................... 67
The Mechanics of Macro Usage ............ 67
Sample Program Using Macro ............. 68
Assembler (ASM8) Operating Procedures ...... 68
Cross-Reference Listing ..................... 70
Error Messages ............................ 70
Non-Fatal Errors ........................ 70
Fatal Errors ............................. 71
Warnings ............................... 71
MicroDOS User Functions .................... 72
110 Control Block and Buffers ............... 72
IOCB Initialization ....................... 72
Byte 0 - Open Parameter ................ 72
Byte I - Status Byte .................... 72
Bytes 2 to 4 - Non-User Area ............. 73
Bytes 5, 6 - Start of Sector Buffer ......... 73
Bytes 7, 8 - End of Sector Buffer .......... 73
Byte 9 - Write Parameter ................ 73
Byte II - Unit Number .................. 73
Bytes 12 to 20 - Name and Extension ...... 73
Byte 24 - File Definition ................. 73
Byte 31, 32 - Device Mnemonic ........... 73
IOCB Changes After a File Is Opened ....... 73
Bytes 5 to 8 - Sector Buffer .............. 73
Byte 0 - Open Parameter ................ 73
Byte 9 - Write Parameter ................ 73
Bytes II to 20 - Unit Number, Name, ...... 73
and Extension ....................... 73
Bytes 31. 32 - Device Mnemonic .......... 73
IOCB Example .......................... 73
Introduction to User Functions ............... 74
Console 110 Routines ...................... 74
CREAD ................................ 74
TyPE .................................. 75
Disk 110 Routines ......................... 75
GETCHR .............................. 75
PUTCHR .............................. 75
GETSEC ............................... 76
PUTSEC ............................... 76
CLOSE ................................ 76
OPEN ................................. 76
REWIND .............................. 77
CDERR ................................ 77
Contenm ___________________________________________________________
Page
10CB Setup Aid Routine .................... 77
SRNAM ............................... 77
Return to MicroDOS Operating System
Routine ................................ 79
CDENT ................................ 79
Operating Sequence Summary ............... 79
Monitor Programs UI71 ...................... 80
Register Save .............................. 80
Self Test .................................. 80
UT7l Commands .......................... 80
T:
Test RAM/PROM .......... 80
0:
Display Memory ............ 80
I:
Insert into Memory .......... 81
M:
Move Memory .............. 81
F:
Fill Memory ................ 81
S:
Substitute Memory .......... 81
P:
Run Program ............... 82
L:
Load System, Drive 0 ........ 82
B:
Load System, any Drive ...... 82
R:
Read a Sector .............. 82
W:
Write a Sector .............. 82
?:
Input from Port ............. 82
!:
Output to Port .............. 82
Terminal Interfacing ............ , ............. 83
UART Action ............................. 83
ASCII Coding ............................. 83
UT71 Routines READ, TYPE, and OSTRNG .... 83
Register Use ............................... 83
READ ................................... 84
TyPE .................................... 84
OSTRNG ................................. 84
Examples of READ and TYPE Usage ........... 85
READ Routine ............................ 85
7
Page
Type Routine .............................. 85
Example I (TYPES) ...................... 85
Example 2 (TYPE6) ...................... 85
Example 3 (TYPE and TYPE2) ............ 85
Example 4 (OSTRNG) .................... 85
Additional Monitor Routines .................. 86
ASCII to Hex Conversion (CKHEX) .......... 86
Initialization Routines (INIT! and INIT2) ...... 86
Example I (IN IT! ) ....................... 86
Example 2 (INIT2) ....................... 86
Restarting UT71 (GOUT7I) ................. 86
Line Printer Interfacing (LINEPR) ............ 86
Disk Routines ............................. 86
Calls to Driver Routines ..................... 88
Appendices
A. Diskette Organization and Structure ....... 89
B. BNF Syntax of Assembler ASM8 ......... 93
C. MS2000 Memory Test. .................. 96
D. Error Messages ......................... 97
l. MicroDOS ........................ 98
2. Utility Program UT71 ............... 98
3. Editor ............................ 98
E. Sample Program Illustrating User
Functions ............................ 100
F. I/O Group Assignments ................ 105
G. Utility Program (UT71) Listing .......... 106
H. ASCII Hex Table ...................... 132
I. Terminal Interface Cable CDPI8S516 ..... 133
J. Adding Generic Devices ................ 134
K. MicroDisk Development System MS2000
Specifications ....................... 136
L. Contents Directory of System Diskette
(Typical) ............................. 138
M. Format of SUBMIT Command .......... 139
8
1. System Structure and Set-up
Two Memory
Disk Drives
FourExpan~on Pow.rSup~yand
Positions
Control Panel
30-kB RAM
2-kB ROM
Fig. 1 - MS2000 chassis with two front covers removed to show typical module locations.
One of the features of the MicroDisk Development
System MS2000 is its modular construction. Fig. I
shows an arrangement of the modules that provides
good mechanical and electrical balance. The modules
that make up the MS2000 include:
I. 20-Slot Microboard Industrial Chassis with
Backplane
2. CMOS Microboard Computer (CPU)
3. Microboard Memory Module with 32 Kilobytes
of RAM
4. Microboard Memory Module with 30 Kilobytes
of RAM and 2 Kilobytes of ROM
5. Microfloppy Disk Controller
6. Dual Disk Drive Module
7. Power Supply Module
Chassis
The chassis supplied with the MS2000 is a 20-slot
customized MSI8820 Industrial Chassis. It includes an
integral card rack, backplane, and case. The top and
bottom covers are perforated and removable. The front
and back covers are removable as are the side panels and
end bezels.
The backplane is a standard Microboard universal
backplane in which any module may occupy any position. To prevent magnetic interference between the
MSIM40 power supply and the MSIM50 Disk Drives,
always mount the modules with at least four card slots
between them. Table I shows the backplane signals and
their pin assignments.
The signal naming convention is to give each signal an
9
1. System Structure and Set-Up
Table I-Pin Terminals and Signals for the RCA Microboard Universal Backplane.
Component Side
Wire Side
Pin
Mnemonic
A
B
C
D
E
F
H
J
K
L
TPA-P
TPB-P
DBO-P
DB1-P
DB2-P
DB3-P
DB4-P
DB5-P
DB6-P
DB7-P
AO-P
A1-P
A2-P
A3-P
A4-P
A5-P
A6-P
A7-P
MWR-N
EF4-N
+5V
GND
M
N
p
R
S
T
U
V
W
X
y
Z
Signal
Flow
Out
Out
In/Out
In/Out
In/Out
In/Out
In/Out
In/Out
In/Out
In/Out
Out
Out
Out
Out
Out
Out
Out
Out
Out
In
Description
Pin
Mnemonic
System Timing Pulse 1
System Timing Pulse 2
Data Bus
Data Bus
Data Bus
Data Bus
Data Bus
Data Bus
Data Bus
Data Bus
Multiplexed Address Bus
Multiplexed Address Bus
Multiplexed Address Bus
Multiplexed Address Bus
Multiplexed Address Bus
Multiplexed Address Bus
Multiplexed Address Bus
Multiplexed Address Bus
Memory Write Pulse
External Flag
+5V dc
Digital Ground
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
DMAI-N
DMAO-N
RNU-P
INT-N
MRD-N
Q-P
SCO-P
SC1-P
CLEAR-N
WAIT-N
-5/-15V
SPARE
CLOCK OUT
NO-P
N1-P
N2-P
EF1-N
EF2-N
EF3-N
+12V/+15V
+5V
GND
alphanumeric name descriptive of its major logic function, followed by either -N or -Po The -N means that the
named function is true or asserted when the voltage on
that particular wire is at ground. The -P means that the
named function is true when the voltage is at +5 volts.
Thus, a signal NAME-N, after passing through a logic
inverter, becomes NAME-P, and vice versa.
The user may wish to rearrange the position of the
existing modules when adding expansion modules. For
example, if a UART card or a Modem card is added, the
two memory cards can be moved to slots 13 through 16
to place the serial-interface card near the left side for
ease of cable entry. Alternatively, the cable may be
passed under the disk-drive assembly at the front, top,
or bottom and the serial card placed in slots 13 through
16. There is sufficient space to pass a 34-wire flat cable
(wider cables may be folded). The size of the connector
needed with the wider cables will require that the disk
module be pulled part way out while placing the cable.
When using the PROM Programmer CDP18S680,
the left side panel may be removed and the Programmer
placed in slot 1 for access through the left-hand end
bezel.
Always allow clearance for air circulation at the top
and bottom of the chassis. Overheating and drive or
supply failure could result otherwise.
Signal
Flow
In
In
-
In
Out
Out
Out
Out
In
In
-
Out
Out
Out
Out
In
In
In
-
Description
. DMA Input Request
DMA Output
Run Utility Request
Interrupt Request
Memory Read
Programmed Output Latch
State Code
State Code
Clear-Mode Request
Wait-Mode Request
Auxiliary Power
Not Assigned
Clock from CPU Osc.
I/O Primary Address
I/O Primary Address
I/O Primary Address
External Flag
External Flag
External Flag
Auxiliary Power
+5Vdc
Digital Ground
Microboard Computer
The Microboard Computer supplied as the CPU of
the system is a variant of the CDPl8S605 Microboard
Computer. The on-board memory has been left out
because the system memory is wholly contained in the
two memory Microboards. As a result, the CDPI802A
Microprocessor and the CDPI854A UART are the
main functional units. The U ART provides the serial
data path to an external data terminal through an
RS232C interface. The baud rate is selectable by the
setting of a DIP switch on the CPU Microboard. Baud
rates from 50 to 19,200 are available. Table II is a baud
rate selection chart showing the position of each of the
four rockers of switch S 1 for each output baud rate
available.
Microboard Memories
Both memory Microboards supplied with the MS2000
are made from the CDP18S628. One is populated with
32 kilobytes of RAM and occupies memory space from
OOOOH through 7FFFH (H indicates hexadecimal notation). The other is populated with 30 kilobytes of RAM
and 2 kilobytes of ROM. The ROM contains the monitor program UT71. The ROM occupies memory space
User Manual for the RCA MlcroDlsk Development System MS2000
10
Table II-Selection Chart Showing Rocker Positions for
Each Baud Rate Available on the CPU Board.
Switch S1
4
3
2
1
C
C
C
C
C
C
C
C
C
C
0
C
0
C
C
0
0
C
C
C
0
C
0
C
0
0
0
0
0
0
0
0
0
0
0
0
0
C
C
C
C
C
C
0
0
0
0
C
C
0
0
0
0
0
C
0
C
0
C
0
Output Rate
Baud"
19200
50
75
134.5
200
600
2400
9600
4800
1800
1200
2400
300
150
110
·Actual Input to UART IS 16 times the indicated output rate,
assuming a clock frequency of 2.4578 MHz. 0 = open; C =
clothes.
SOOOH through S7FFH, and the RAM SSOOH through
FFFFH.
Microboard Disk Controller
The Microboard Disk Controller CDPlSS6S1 provides the I/O interface between the system software and
logic and the two disk drives. Instruction and status data
are transferred by output and input commmands; bit
data are transferred by Direct Memory Access (DMA).
The logic to control the DMA process is built into the
disk controller Microboard to interface with the on-chip
DMA controller of the CDPlS02A on the CPU Microboard. At the end of a DMA transfer, external flag EF3
is used to signal the completion to the software.
The monitor program UT71 contains the I/O driver
routines for performing all the commands for the disk
operating system (MicroDOS). The disk controller can
perform the following functions:
1.
2.
3.
4.
S.
6.
7.
Seek a track
Format a track
Write a sector
Read a sector
Read mUltiple sectors
Write multiple sectors
CRC READ (Read without data transfer but
with error checking).
S. Recalibrate (Return heads to home position on
track 00).
The disk controller is capable of a variety offormats.
Appendix A - Diskette Organization and Structure
shows the format and disk organization used by the
MS2000 MicroDisk Development System.
Dual Disk Drives
The two MicroDisk drives are contained in the
MSIMSO module. The module occupies eight slots in
the 20-slot chassis. An edge connector picks up power
from the backplane, and power-conditioning circuits
then provide +S and +12 volts to the two disk drives. The
signal cable is a "daisy chain" configuration using a
26-wire flat cable. The controller end of this cable is a
SO-pin connector mating with the CDPlSS6S1 Microboard Controller. The controller is located immediately
to the left of the disk drive module in the chassis. Be
careful that the cable doesn't "push" on the cover of
Drive 0: disk errors will result.
The drives are labeled 0 and 1, corresponding to the
drive number used in MicroDOS commands. Drive 0 is
the left drive.
The mating 3 Yl-inch diskette has a hard cover with a
sliding cover over the head access window. As supplied,
the diskettes are not write protected. Activate this feature by breaking out the protect tab, rotating it 90°
counterclockwise, and reinserting it. Slide the tab outward for write protect and inward for write enable.
Always mount the MSIMSO at least four card slots
away from the MSIM40.
Power Supply
The MSIM40 Power Supply Module plugs into the
system chassis and occupies four slots. The edge connector supplies +S, + IS, and -IS volts to the system backplane and interfaces the control logic to the system.
An AC input cord, fuseholder, power on-off switch,
and power-on indicator (+S volt LED) are on the front
panel. In addition to the power functions, the front
panel provides two system control switches and a running indicator.
The two control switches are momentary-action,
double-throw types having a center-off position. The
R UN UTILITY (RNU) switch, when pressed down,
causes a system reset followed by a start at address
SOOOH, the beginning of the monitor program UT71.
The RUN PROGRAM (RNP) switch, when pressed
down, causes a system reset followed by a start at
address OOOOH, where a user program may have been
stored in RAM. If either switch is pressed upward, a
system reset is generated and latched until either switch
is pressed down. The indicator LED labeled RUN is
lighted during program execution and extinguished
when an IDLE instruction, aWAIT condition, a
11
1. System Structure and Set-Up
RESET condition,or any malfunction preventing normal fetching of instructions is encountered.
System Setup
As the first step in system setup, remove the chassis
from the carton and place it on a table on its four rubber
feet. Using a No. I Phillips screw-driver, remove the two
screws from the left-most front cover (the one with the
"RCA" on it). Remove the cardboard spacer that held
the boards in place during shipment. Remove the leftmost board (the CPU board) by lifting up on the black
card extractor on the top of the board. Push the card
extractor down and carefully remove the CPU board.
NOTE: Handle the board on the edges only since the
CMOS parts on it are sensitive to static electricity.
Locate the red four-position baud-rate switch and set
the baud rate corresponding to your terminal, as given
in Table II. In this table, C means on, 0 means off. Now
reseat the other three boards by lifting up on their
extractor. Then push it down and firmly press the
boards back into place. Any of the boards may be
removed for your inspection but remember to be careful
in handling them; and make sure that they are firmly
reseated. Finally, replace the CPU board in the left card
slot. NOTE: Make sure the component side of the board
faces left.
The lO-pin connector on the top edge of the board is
the RS-232 terminal connector. Remove the black cable
from the parts box, push the lO-pin end ofthe cable into
the back of the chassis between the left rear handle and
the chassis body. Then feed it into the slot in the forward
part of the plate on the left side next to the CPU board.
Finally, place the lO-pin connector over its mating pins
on the CPU board, being careful to align the plugged
hole with the position of the missing pin. Now connect
the other end with the 25-pin D connector, to your
terminal. If the sex of the connector is incorrect for your
terminal, use the "gender bender" included in the parts
box.
Next plug in the computer system and terminal; turn
on the terminal, then the computer system. The red
"5V" light on the right panel indicates the presence of
the +5 volts DC.
Monitor Program Check
With the +5 volts available, the red "RUN" light will
come on and an asterisk and UT71 version number will
be displayed on the terminal. The asterisk is the prompt
for the UT71 Monitor program. (If no asterisk appears,
try restarting the monitor program by depressing and
releasing the RUN U toggle switch.)
Now type T (CR)
where (CR) means carriage return. The system should
respond with
MEMORY OK
•
The "T" command does a checksum of the Monitor
ROM, and does a read-write test on all RAM (RAM is
left filled with "AAsj.
Now type
D8000 20 (CR)
The system will respond with
8000 7100 F880 BOF8 8CBI F81F
AIFI 21F8 D073
8010 81F6 CFF9 IOFC 8151 F33A
26D I 7381 FF03
•
The monitor command "D" displays the contents of
memory at the terminal. The command displays the 20
hex (32 decimal) bytes of data starting at location 8000
on the terminal, then returns the prompt. Since terminal
communication has been established, the front cover,
removed earlier, can be replaced.
Disk Operation Check
The system disks can now be used. Take the blueplastic-enclosed 3Y2-inch diskette with the white stickon label from the parts box. This diskette contains the
MicroDOS Operating System, some utility programs,
and the Editor and Assembler.
Check to see if this disk has been "write-protected" to
prevent data being inadvertently written to it, possibly
destroying existing programs. To do this, find the small
rectangular cutout in the corner of the back of the
diskette, the side with the round metal hub in the center.
If the removable tab is either missing or has slid against
the outside edge of the cutout, the disk is write protected. If the disk has not been write-protected, you
must complete the procedure described in the next
paragraph.
Carefully pry up the tab and break it loose. Turn the
tab 90° from its original position. On one of the short
ends, there is a small protrusion. This will line up with
the depression in the side of the slot from which the tab
was removed. Carefully insert the tab in the slot, aligning the protrusion on the tab with the depression on the
side of the slot, and snap the tab in place. When properly
inserted, the tab will slide back and forth in the slot
without coming out. Slide the tab towards the closest
edge of the diskette. This will write-protect it. You can
12
User Manual for the RCA MlcroDlsk Development System MS2000
un-write-protect a disk with a missing tab by covering
the slot with tape.
Turn the diskette over and slide the metal protector so
that the oval cutout is in the center of the diskette in line
with the load access hole in the blue plastic. The recording media can be seen through this hole. Now insert the
diskette into the left disk drive, the one marked
"DRIVE 0." Orient the diskette so that the metal hub is
towards the right (away from the CPU board) and the
edge with the head access hole fits into the disk drive slot
first. Push the diskette all the way into the drive until it
clicks into place and the red light on the drive blinks on
then off. The diskette will not latch if improperly
oriented. This completes the loading of the diskette.
Auto-shutter diskettes, mounted in drives so-equipped, will open and close the cover automatically.
Now load the disk operating system. Type "L", and
the system will load the 12 kilobytes of operating system
into memory. About 0.6 second after typing L, the
MicroDOS prompt is issued:
(C) Copyright 1982 RCA Corporation
MicroDOS X.X
The ">" sign is the MicroDOS prompt. The X.X will be
two digits, the revision number ofthe diskette (e.g., 0.0).
Now type DIR;S (CR) . This entry will run the disk
directory program, which will display the name of the
diskette and an alphabetical listing of all the files on the
disk.
Next type HELP (CR) and follow the instructions
given you on the first screen. The HELP utility gives a
brief description and format of each of the MicroDOS
utilities.
As a first use for the system prepare a second diskette
in the parts box for use. This diskette must be formatted
and initialized for MicroDOS;this is done by using
FRMT and SYSGEN. Place this diskette in drive I in
the same manner as described above for the system
diskette, but don't write-protect it. Type FRMT (CR)
and follow the instructions. When this task is complete,
type SYSGEN;E (CR) and follow those instructions.
You will then have created- a duplicate of the system
diskette. The original can be removed and set aside for
safe keeping.
This description demonstrates only a very small part
of the system capability. Refer to the remainder of this
manual for descriptions of the other utilities and the
Editor and Assembler.
13
2. Understanding MicroDOS
Introduction
The Microboard Disk Operating System (MicroDOS) associated with the MicroDisk Development
System MS2000 is a powerful and easy-to-use tool for
software development. It is an interactive mass-memory
storage system capable of dynamic file operation and
management. Its commands, obtained via the system
console, reference files stored on the diskette. By means
of its dynamic operating system, MicroDOS keeps
track of changes in file size during software development and allocates disk space as needed. Disk space not
needed by a file is freed and made available for use by a
different file. The file operating system can have multiple input and output files open at the same time and can
thereby provide the user with considerable design flexibility. The operating system also provides a set of functions that can be called by a user program to perform
utility operations such as open files, close files, and the
like.
MicroDOS System Ingredients
Use of the MicroBoard Disk Operating System
(MicroDOS) requires a MicroDisk Development System MS2000. The software needed for MicroDOS
operation includes the UT71 Utility Program, provided
on ROM, and the programs provided on the MicroDOS System Diskette. These programs include:
On Disk:
1. MicroDOS Operating System (OP. SYS)
2. MicroDOS System Commands (CDSBIN,
COPY, DEL, DIR, FREE, MERGE, PRINT,
RENAME, SUBMIT, SYSGEN, U, VERIFY)
3. MicroDOS Macro Disk Assembler (ASM8)
4. MicroDOS Disk Editor (EDIT)
5. Memory Save Program (MEM)
6. Diskette File Examination and Modify Program
(EXAM)
7. Diskette Diagnostic Program (DIAG)
8. ASM4 to ASM8 Source Conversion Utility
(CONASM)
9. Pertec to or from MicroDisk Transfer Utility
(PERTEC)
10. Cassette to or from MicroDisk Transfer Utility
(TAPED)
11.
12.
13.
14.
Memory Test Utility (MEMTST)
Diskette Format Utility (FRMT)
Instructions for MicroDOS (HELP)
Twelve User Functions
On ROM (UT7l)
1. Disk Loader
2. 110 Transfer Routines (READ, WRITE)
3. UT71 Self-Test Routine
Files and File Names
All user-generated programs stored on diskette are
identified by file names of up to nine alphanumeric
characters. The names for these files are devised and
assigned by the user. Each diskette maintains a dynamic
directory of all user files kept up to date automatically
by the MicroDOS Operating System. Access to a user
file is by its name only; the user has no need to know
where a program resides and need not maintain track
number information for any of the programs.
The major advantage of the MicroDOS Operating
System and its use of file names is that only the Operating System is loaded into memory. All other function
files stay on diskette and go into memory only when
they are used. This dynamic file management system
gives the user maximum service from the MS2000
memory capabilities for programming needs.
A file is composed of a set of sectors grouped into a set
of clusters. Each cluster contains one sector. Files are
located by MicroDOS only on one disk and are identified by name, extension, and device unit number.
The file name consists of from one to six alphanumeric characters and an extension consisting of from
one to three alphanumeric characters. The first character of the file name and the extension must be alphabetic. The standard format for a file name is given by the
following example:
FILENl.SXX:#
where FILENI is a 1 to 6 character name
SXX is a 1 to 3 character extension, and
# is the number of the drive unit (either 0 or 1)
All the MicroDOS system commands are files on the
system diskette. These commands are brought into
execution when the command name is typed on the
console input. Because the main Operating System
14
User Manual for the RCA MlcroDlsk Development System MS2000
resides in memory in locations 9000-BFFF, its area
cannot be used by any program. Care must be taken,
therefore, not to write a program that uses that area.
The majority of memory, however, is left available for
execution of the system commands or the user programs. Once a system command or user program has
finished operation, the memory area used is returned to
the system so that other programs can use that same
area.
All file names are stored on a special area of a
diskette. This special area is called the Directory and is
not the same as the DIR.CM utility which is discussed
later in this manual. The Directory resides on track 0 of
all diskettes and cannot be deleted. Any diskette that is
to be used by MicroDOS must have this file. It can be
generated only by the SYSGEN command. Thus, each
new diskette must be initialized using the SYSGEN
command before it can be used.
MicroDOS supports two types of files: ASCII and
binary. ASCII files contain only ASCII characters.
Examples are assembly source and object files. Binary
files contain only binary information and are used for
system programs such as the Assembler and Editor.
Binary files require only half the space for storage and
can be loaded twice as fast as their ASCII equivalents.
Files generated by the system, however, are ASCII
unless they have been created by use of the program
CDS BIN, which converts an ASCII object file to
binary.
A file called the Operating System appears in the
Directory as OP.SYS and is designated as file type 3.
this file is the actual MicroDOS Operating System and
cannot be copied or merged. It can be deleted if the
delete protection is removed with the RENAME command. It resides on tracks I through 3 and is also
transferred only by the SYSGEN command. The
information in this file is in binary. The Operating
System does not have to be on a MicroDOS diskette. It
only has to be on the diskette that is used to load
MicroDOS. Not having the Operating System on the
diskette frees three tracks for user information, approximately 4% of the diskette area. By means of the DIR
command with S option, the presence of the Operating
System on a diskette can be ascertained.
diskettes, although fairly rugged, must be handled and
stored with care. To avoid damage to the recording
surface and to prevent diskette deformation, the following specific precautions should be carefully observed.
*
*
*
*
*
Close the disk guard cover when not in use.
Do not touch its recording surface.
Do not smoke when handling the diskette.
Do not clean the recording surface.
Do not bend the diskette or deform it with paper
clips or other similiar mechanical devices.
The operating and storage environment must be
compatible with the materials of the diskette. The environment of the diskette should meet the following
criteria:
*
*
*
*
*
*
No noticeable dirt, dust, or chemical fumes in
the immediate area.
Temperature between 500 F (100 C) and 115 0 F
(45 0 C).
Relative humidity between 8 and 80 percent.
Maximum wet-bulb temperature of 85 0 F (30 0
C).
No direct sunlight on diskette surface for prolonged periods.
No nearby magnetic fields.
Loading a diskette into a drive mechanism and removing it requires a few precautions to avoid damage
and to assure proper operation. These precautions
include:
*
*
*
*
*
*
Do not insert or remove a diskette unless power
is applied to the System.
Insert diskette with read/write access slot first.
Insert diskette until it automatically becomes
locked in.
Do not remove a diskette from a drive if the
select light for that drive shows any sign of
activity.
Format each new diskette with the FRMT
utility and then initialize it with the SYSGEN
utility
Do not leave diskette idling in system for prolonged periods.
. Memory Requirements
Diskettes and Diskette Handling
The diskettes used by MicroDOS are of the doubledensity type and can store over 322,000 bytes. The drive
mechanism has two drive units (the left hand one is
designated 0; the right hand one is designated I). The
system has a capacity of over 644,000 bytes of on-line
storage.
To assure trouble-free reading and writing files, the
MicroDOS requires memory in the following areas:
HexaDecimal
Decimal
Address
Address
0000-7FFF
COOO-FFFF
Utility Program
8000-8FFF
Operating System Area 9000-BFFF
User Areas
0-32767
49152-65535
32768-36863
36864-49151
15
2. Understanding MlcroDOS
The user area (OOOO-7FFF and COOO-FFFF) is used
by either the user programs or by MicroDOS commands. The memory area from 9000 to BFFF is
reserved for MicroDOS.
Utility Program UT71
The Utility Program UTII contains the bootstrap
program that initially loads the Operating System into
memory. It may be loaded from drive 0 with the "L"
command or from any drive with the "B" command. If
the specified drive does not contain a diskette, an error
message is printed and control remains with UT71. To
load the Operating System, place the system diskette in
drive unit 0 and type L.
After the Operating System has been loaded, control
is transferred to it. If the user wishes to use the debug
feature in UT71, the user must press the RESET / RUN
U key or return to the UT71 by typing U,8000. If the
user is operating under UTI I and wishes to return to the
Operating System, which was previously loaded, he
must type P9000(CR).
Peripheral Devices
All communications between the peripheral devices is
handled by either UT71 or the Operating System. Whenever the command interpreter requires I/O, it goes to
the appropriate routine in UT71 or MicroDOS where
the function takes place. When the function has been
completed, control returns to the command interpreter.
Usually the user will not have to be concerned with the
peripheral devices because communication with them is
handled by MicroDOS automatically.
Program Creation and Translation
With the Editor, the user can create or modify an
existing program. The program may be stored on the
diskette under a file name with or without an extension.
Once the source file has been created on the diskette, it
can be input to the Assembler or Editor by referring to
its file name.
To speed the loading of object file modules and save
space on the diskette, MicroDOS has a command that
converts ASCII-HEX object files into binary object files
(CDSBIN).
How MicroDOS Operates
Resource Management
A major function of MicroDOS is to manage the
resources of the development system so that the user
does not have to. MicroDOS provides these functions
by having a fixed way of identifying each file on the
diskette and the peripheral devices such as the console
or line printer.
Device Name Format. With MicroDOS, a specific
name is assigned to each peripheral generic device. The
device name always begins with the symbol "#" and
includes two additional characters. The generic device
names pre-assigned by MicroDOS include:
#TY Teletypewriter console printer
#KB Console keyboard
#LP Line printer
#SC CRT screen
Additional names for other peripheral devices can be
assigned by the user. A device name for the disk drive
mechanism is not needed because its designation is
implicit in the file name format.
File Name Format. Each file to be stored on the diskette
is identified by a three-part designation consisting of a
NAME, an EXTENSION, and a DRIVE NUMBER.
Fig. 2 shows the format for assigning identifying designations to files. In this format, NAME is a user-assigned
name consisting of an alphabetic character followed by
up to five alphabetic or numeric characters.
T
INAMEI
.1~1:~
LIto
3 Ilphonumoric
, to 8 IIph8nurneric ch.rectan
numbor
"'"roct"n
92CS-31642
Fig. 2 - Format for naming files.
The EXTENSION, separated from the NAME by a
period, may be used to differentiate versions or revisions
ofthe same program. The EXTENSION is one to three
alphanumeric characters the first of which, like the
NAME, must be alphabetic. Although an EXTENSION is not required when a file designation is assigned,
if an EXTENSION is added it must be used every time
the file is referenced. When the command CDS BIN is
used, if an EXTENSION is not specified by the user,
MicroDOS will assign one (CM).
The DRIVE portion of the file designation is a
number, either 0 or I, preceded by a colon(:) and is the
logical number ofthe drive unit. Ifthe DRIVE number
is not specified, MicroDOS assumes it is 0 except for the
Editor and Assembler. If the file does not reside in the
unit specified, an error message is printed.
Whenever FILENAME is used throughout this
manual, it means:
::=[. ] [: < DRIVE> ]
User Manual for the RCA MlcroDlsk Development System MS2000
16
Examples of FILENAMES are:
AB
AB.XY
AB.XY:O
"Wild-Card" Construct. When a directory is being
searched for a file name, the user can take advantage of
the "wild-card" construct with certain commands to
broaden the search. The "wild-card" construct refers to
the use of an asterisk * in the place of some or all the
characters in a name or extension. The asterisk means
match anything when the directory is being searched.
For example:
NAME.* - means match any file name with
NAME and extension or without an
extension.
*.EXT means match any file name with EXT
and any name.
means match any file name.
*.* The asterisk can also specify a wild-card match for the
remainder of the name or extension. For example:
AB*.HEX - means match any file name with AB as
first two characters of the name and HEX as the extension. These file names would match:
ABC.HEX, ABXYZ.HEX, AB.HEX.
Referencing Files. The MicroDOS method of referring
to files by means of a user-selected name that can be
both brief and mnemonic can save the user a great deal
of time as compared to a physical retrieval and defining
of the unit number and track number for a file. MicroDOS keeps track of where the file was established and
where it is located on the disk. The file name is converted by MicroDOS to physical addresses for the system to use when the file is opened.
The opening of a file reserves a table for referencing
the file and for holding pointers to the file's beginning.
As the user accesses the file, the pointers change. The
system or the user program may continue to reference
this file until it is closed. When one of the system commands (such as VERIFY) makes access to files, the
opening and closing of files are done within the command. If the user writes a program that opens or closes
files, the program must contain the open and close
function. Refer to the chapter entitled MicroDOS User
Functions, for more details.
Development Station Console. The console is used to
echo the user input, display messages that direct the user
to perform specific functions, or display data. It may be
either a hard-copy terminal or a CRT terminal and is
used to communicate with MicroDOS. The designation
for the console input device is #KB and is actually the
console keyboard. The designation for the console output device may be either #TY for a hard-copy terminal
or #SC for a CRT terminal.
When #SC is selected as the output device and when a
large data file is sent to the CRT screen, only 22 lines of
data will be displayed at a time. The prompt "****"will
also appear at the bottom of the screen indicating that
more data is to follow. The user may view the next 22
lines by pressing the space bar. This procedure is
repeated until the entire file or message has been viewed.
A program that can be halted with the BREAK key
(EXAM, COPY, etc.) can usually be either aborted with
the Q key or continued with any other key after it has
been halted by the BREAK key.
Command Interpreter
The command interpreter is the main interface
between the user and the Disk Operating System. The
user enters commands through the main console device.
Prior to command entry, however, the Operating System has to be loaded into memory from disk. The
Operating System is designated MicroDOS VV.RR,
where VV is the version number and RR is the revision
number. MicroDOS tells the user that it is ready for
more input, after it is loaded, by the single prompt
">". At this point, interrupts are disabled. If the user's
program sets interrupts and returns to MicroDOS
through the system function CDENT, interrupts remain
as set by the user's program. If the user reenters
MicroDOS through P9000, interrupts will be disabled.
Once MicroDOS is executed either by loading with the
L command or by executing a P9000 from UT71, interrupts are disabled. Entering MicroDOS any other way
will leave the interrupt state as the user program
assigned them.
The command to the Operating System includes the
name of the system file to be executed plus any parameters or options that the file may need. Because all commands are names of files stored on the disk, the user may
add to the existing set of commands very easily.
Command Format. The format for the command line is
given by:
[]
[;]
where
is of the form defined in
Fig. 2
is a non-numeric character
such as comma, space, or slash
is either another file name
or a generic device name
17
2. Understanding MlcroDOS
are either one or more
or a depending on the command
All system commands are given the extension "CM".
If the user does not type an extension with the filename
when specifying a command, MicroDOS will assume
that it is "CM". A command cannot have a blank extension. When the user wishes to load an object file with a
blank extension, he must add an extension after the file
name with the RENAME command. The unit number
default value is 0, unless otherwise specified.
When a file is loaded, one ofthree actions is taken. (I)
Ifthe file is a binary file created by CDS BIN, the file is
loaded and executed at the starting address given by the
COS BIN program. (2) If the file is an ASCII-HEX file,
with no SU information at the end of the file, the file is
loaded and control is passed to the command interpreter. To execute the loaded file, the user must press
RESET / RUN U followed by a P and execution address
command on the console device. (3) If the file is an
ASCII-HEX file with the SU information at the end of
the file, such as a listing or hex file created by the
Assembler, the file will be loaded and executed at the
address following the SU.
between file names in the command
must be non-alphanumeric characters (such as .::l or = or
/ or ,) that are not used by the file name.¢ The following
commands, therefore, would all perform the same
function.
DIRMEM.SOH
DIR=MEM.SOH
DIR/ MEM.SOH
DIR,MEM.SOH
In addition to the above delimiters, MicroDOS
ignores leading spaces of a command and treats multiple spaces between commands as one delimiter.
If the file name is not found on the system, the
"FILENAME NOT FOUND"
message will be printed. If an erroneous file name such
as 1.# is typed, the message
WHAT?
is typed and control is returned to the command interpreter. The CTRL-C character (03) will cause deletion
of the entire command line. The LF character (OA) will
type the current contents of the command line.
The rubout key (7F) will print a left bracket "["
followed by the deleted character. When the key for
non-delete character is pressed, a right bracket "]" is
printed followed by the pressed character. The rubout
¢
Symbol .::l is used here to indicate a blank space.
deletes the last character entered into the buffer. NOTE:
Unless otherwise specified, all console inputs are terminated by a carriage return (CR). Note also that corrections cannot be made by backing the cursor and typing
over the erroneous characters.
To pass control from MicroDOS to the Utility Program UT71:
Type U,8000 (CR) or press the RESET/RUN U
key.
To pass control from UT71 to MicroDOS:
Type P9000 (CR)
Error Messages. All error messages are displayed in a
text manner. If a file name cannot be found, MicroDOS
prints a message giving the file name requested and
stating that it was not found. Recovery from error
message depends on the MicroDOS program being
executed. Subsequent chapters of this Manual explain
the recovery from certain error messages and provide a
listing of the error messages along with a description.
The description aids in leading the user to a recovery
procedure. A list of the MicroDOS error messages is
given in Appendix D.
Diskette File Management
File Types. All data on the disk are in a combination of
ones and zeroes. In different files, however, the combination of one and zero bits is interpreted in different
ways. The Assembler and Editor, for example, create
ASCII files and accept only ASCII files. The use of
other types of files, such as binary, would yield unpredictable results. ASCII files may be printed. Other files
on disk may have some printing result but they will
probably be unreadable. For loading purposes, ASCIIHEX files must have an address associated with the
object code.
Transferring a file from ASCII-HEX to binary is
performed by the CDS BIN program. The resultant
binary files consist of only a machine language representation ofthe program. There are no addresses in the file
because all address information is in the file's descriptor
area. An ASCII-HEX file, therefore, cannot be loaded
as a binary file.
Some of the programs in MicroDOS such as CDSBIN
add specific extensions to the file. Its default extension is
CM. The other programs, however, such as the Editor,
do not have any default extensions. Their default extension is three blank characters.
File Attributes. The attributes that may at the user's
option be associated with a disk file include:
1. System (invisible)
2. Write protection
User Manual for the RCA MlcroDlsk Development System MS2000
18
3. Delete protection
4. Contiguous
When a file is created, all attributes are usually false or
not set. By means of the RENAME command, all the
attributes except contiguous may be set or reset. Contiguous must be set when the file is created.
A system file is one that is constantly used, such as the
Assembler or Editor. These files do not appear in Directory lists and are not members of deleted sets unless a
special option is selected when the DIR or DEL command is used.
Write protection is set so that a file cannot be written
to. This protection prevents the user from inadvertently
destroying a file.
Delete protection is set so that a file cannot be deleted
with the delete command. To delete a delete-protected
file, the user must first unprotect the file with the
RENAME command and then delete the file.
A contiguous file is one that is stored without interruption in a set of contiguous sectors. The only file in the
system that must be contiguous is the binary file because
of the manner in which binary files are loaded by the
operating system.
Diskette Structure
Refer to Appendix A for details on diskette organization and structure.
MlcroDOS Commands
Files on a disk can be manipulated by the user with
either the system functions or the system commands.
This section deals only with file manipulation by means
of the system commands. The system functions are
discussed later.
MicroDOS commands perform the following operations:
l.
2.
3.
4.
Format new diskette
Initialize new diskette
Load and execute programs
Create, delete, and list diskette files and directories
5. Change file formats
All diskettes that have never been used are completely
blank and must first be formatted with the FRMT
utility. Once formatted, the diskettes must be initialized
with the SYSGEN utility. Complete system diskettes
may be generated.
Program loading and execution are performed by
entering the file name. If the ASCII-HEX program is
not terminated by SUXXXX, control returns to the
command interpreter. Control can then be passed to the
program by means of UT71 or the MicroDOS U command. If the file is binary, execution starts at the address
established by CDS BIN when the file was generated.
Program creation, deletion, and the control operations such as the listing of diskette files and directories
are performed by the following commands.
COPY
DEL
DIR
EXAM
FREE
MERGE
PRINT
RENAME
U
VERIFY
Transfers data
Deletes unprotected files
Displays directory and associated
information
Displays or modifies actual information on a diskette
Lists unused areas of the diskette
Merges two or more files into one
file
Transfers data to line printer with
more flexibility than COPY command
Changes file names and attributes
Starts programs from MicroDOS
Verifies one file against another
The use of the Assembler (ASM8) and Editor (EDIT) in
the creation of files and the use of additional programs
for diskette control and problem diagnosis are covered
in later sections.
The changing of file formats and the editing and
assembly of files are performed by the following
commands.
CDSBIN
EDIT
ASM8
CONASM
PERTEC
TAPED
Converts MicroDOS ASCII-HEX
files to MicroDOS binary files
Creates and changes ASCII files
Converts source programs in assembly language into executable (hexadecimal) machine code.
Converts ASM4 source files into
ASM8 source files.
Transfers files from Pertec drives
to MicroDisk drives and from
MicroDisk drives to Pertec drives.
Transfers files from cassettes to
MicroDisk drives and from MicroDisk drives to cassettes.
NOTE: Diskette Recovery
If the directory on a system diskette becomes unusable, there is no way of recovering the data on that
diskette. The user, therefore, should always keep backup
copies of key files.
19
3. MicroDOS Command Descriptions
This chapter describes in detail each system command available on MicroDOS. The commands included
are:CDSBIN, CONASM, COPY, DEL, DIAG, DIR,
EXAM, FRMT, FREE, HELP, MEM, MEMTST,
MERGE, PERTEC, PRINT, RENAME, SUBMIT
SYSGEN, TAPED, U, and VERIFY. ASM8 and
EDIT, which are the Assembler and Editor, respectively, are discussed in greater detail in subsequent
chapters.
For ease of use, the system command descriptions are
given in a standard format which includes the command
name, its purpose, its format, its action, error messages,
and examples. In the description for each command, the
angular braces < and> indicate required inputs. The
square brackets [ and ] indicate optional inputs. The
symbol ::= means "is defined to be." In the examples, the
underlined material represents printout generated by
the system such as prompts ~ or queries to the user.
(CR) means carriage return.
Note: The system diskette is assumed to be in drive 0 in
most of the following examples, so that the command
name does not have to be followed by a specific drive
number. If the system diskette was in drive 1, the command would have a ": I " appended to it.
A listing of all the MicroDOS error messages is given
in Appendix D.
1. Command:
CDSBIN
2. Purpose:
CDSBIN converts an assembler object file, an assembler listing file, or the ASCII-HEX file generated by the
memory save program (MEM) file into a binary object
file.
3. Format:
CDSBIN[,][;
.