Table of Contents
Advertisement
Section
Subsections
Page
60
30
I
20
03
Dump a DSF Program or Subprogram and Reload It
As a backup procedure, you can dump your often
used programs and subprograms onto cards or paper
tape.
If
anything happened to the disk cartridge,
these items could be reloaded much faster than they
could be recompiled. The job
12 3 4 56 7 B 9 10 1112 1314 1516 171B 1920 2122 2324 2526 2728 2930 3131 1114 lS16 3B8 3940 412
~14H5
/
/
j08
I /
Il/lP
i/) ,niP
/1,4
elo
IT
£11
01
on/;
co
rei
5
Cl,b
o"t
One
L!7
c;,
will cause ITEM to be punched into the deck of blank
cards following the *DUMP card, 54 words per card.
In
addition, a header and end-of-program card will
be punched.
Since the program is punched in such a compact
form, very few programs w
ill
require more than an
inch of cards (about 140 cards, or 6300 words).
Extra, unpunched cards will be bypassed automati-
cally by DUP.
To reload this dumped program, the *DUMP card
should be replaced with
12 3 4 56 78 9 10 1112 1314 1516 1718 1920 2122 2324 2526 2728 2930 3131 1114 3516 3718 394( 123
45
'15
TQ
RE
el.e
LJA
TIT
Ld'1
(if
the program was in DSF) and run as another job.
Dump a DCI (Core Image) Program and Reload It
If
the program to be dumped and reloaded is in core
image format, the procedure must be changed some-
what.
The dump to cards can be accomplished in the
same way, with the *DUMP card.
However, to reload, the STOREDATACI option
is required, and the card count must appear in
columns 27 -30.
For example, a program called
XXXXX, dumped into a deck of 108 cards, would be
reloaded with the card:
12 3 4 56 78 910 1112 1314 1516 1718 1920 2122 2324 2526 2728 2930 3131 3314 lS16 3718 3940 414243
45
i-'"
TO R£
AT
AC
i'CO
lIA
)(X
xxx
01 08
Advertisement
Chapters
Table of Contents
