-------
01
01
0)
0)
c; 10
m <"
4> u)
_ a:
"O
0 C
— to
.a
10 (0
I- —
0
4-
O
4-
._
-o
UJ
0
0)
(0
01
01
0
s:
L.
0
M-
c
O
01
ID
0
CC
ID
•—
L.
0)
4-
L_
0
4-
•—
"O
LU
0>
O)
10
01
01
L. -o c
O c o
3 • —
O O 4-
1- CL —
0 01
N 0 O
O CL
C O 01
10 • C
-C ITl ID
4- r- L.
4-
01 C
01 (0 L.
0 -C O
-J 4- M-
c
ID
f-
4_
—
01 — C
01 ID (D
0 -C
— M- 4-
0
4- L.
O 4-0)
C .C 4-
O1 ID •
01 — Q) 01
•— 0 l_ -o
* D) C
4- 3
-C 4- 4- O
O) 0 O O-
•— c c
0 O
S . — in o
O (D T3 O
4- U4- (D *
0 o> O O m
z N i r-
I-
4-
-C
Ol
0
0 L.
4- 0
ID •+-
-a
' T3 .
(DC 0 >.
(JO 01 (0
c 01 -o
ax 0 0
rj 01 u 01
cr c o —
0 ID L. .c
0) 1- CL4-
•+- 0 >. C
O "0 "0 O
— (D
4-01 0 (D
34- L 4-
O => — 3
O • (0 O
01 01 C.
-00-00
L. 4- L. 4- 0
(D (D (O (O XT
O Q O Q 4-
•
0
t-
3
•o
0
o
0
t_
Q.
-1-
L.
o
01
o
4-
l_
0
M-
0
o:
cc
0
o:
a:
1 , |
LU
O
Z
UJ
~^
0
LU
CO
1
•o
0
0
(0
—
a.
0
i_
0
—
O
. —
r~
0 •
> ^
O
c O
_ —
JD
>^
L_ Q)
4- E
c •—
LU 4-
Q
LU
O
ID
4-
ID
Q
Z
0
1-
o
LU
LU
a:
o
z
25
-------
FlIes. The COLMIS basis computer program uses eight
files (disk or tape) as listed below:
Weekly YTD Master Fi le
Weekly YTD Master Backup File
Monthly YTD Master Fi le
Monthly YTD Master Backup File
Edited Dai ly Data Fi le
Monthly Report Work File
Daily Data Sorted for Monthly File
Weekly Report Work File
Weekly YTD Master Fi les: contain the YTD totals for
each Route, Route Supervisor, District, Area, and the
City as described in Figure 9. The Weekly YTD Master
Files are created by subroutine FILEI and are used by sub-
routine WKCOMP to generate the YTD averages printed by
subroutines WKPRIN, SMPRIN, and MAPRIN.
Monthly YTD Master Files: contain the YTD totals for
each day (Monday through - Saturday) for each Route Supei—
visor and the city as described in Figure 10). The
Monthly YTD Master Files are created by subroutine FILE2
and are used by subroutine MOCOMP to generate the YTD
averages printed by subroutine MOPRIN.
The Edited Daily Data File is generated by sub-
routine EDIT2 and contains information for each day of
data that is accepted (see Figure II). It is used by
subroutines WKCOMP and MOCOMP to generate the sums and
averages printed in the reports.
The Weekly Report Work File is generated by sub-
routine WKCOMP and contains the data printed by sub-
routine WKPRIN, SMPRIN, and MAPRIN (see Figure 12).
The Monthjy Report Work^ Fj I e is generated by sub-
routine MOCOMP and contains the data printed by sub-
routine MOPRIN (see Figure 13).
.2.6
-------
The Daily Data Sorted foj Monthly File is generated
by subroutine MOCOMP and contains the dafa from The Edited
Daily Data File arranged by day of the week.
27
-------
Figure
DESCRIPTION OF THE WEEKLY YTD MASTER FILES
(WYTD and WYTDB)
Position Item
1 District Number
2 Route Number
3 Number of Routes (Week)
4 Total Days of Data Used
5 Total Equipment Costs
6 Total Time to Route
7 Total Mi les to Route
8 Total Time Spent Collecting
9 Total Miles Driven Collecting
0 Total Weight Col lected
1 Total Time Spent Transporting
2 Total Miles Driven Transporting
3 Total Number of Loads
4 Total Number of Loads to Incinerator
5 Total Number of Loads to Landfill
6 Total Number of Loads to Transfer
Stat i on
7 Sum of Vehicle Si ze
8 Total Number of Homes Served
9 Total Weight Collected First Loads
20 Number of First Loads
21 Number of Weighed Loads
22 Total Days of Data with Mileage
23 Sum of Crew Size
24 Number of Breakdowns
25 Number of Lunch Breaks
26 Total Days of Cost Data Used
27 Total Breakdown Time
28 Total Lunch Time
29 Number of Routes (Monthly)
30 Total Manpower Cost
Type Comment
1 nteger
1 nteger
Dol lars
Mi nutes
Mi nutes
Pounds
Mi nutes
Cubic
Yards
Pounds
Mi nutes
Mi n utes
Dol lars
Record Size
Block Si ze
124
2484
No. of Records:
I for each route +
I for each supervisor +
I for each district +
I for each area +
I for the city
28
-------
Figure 10
DESCRIPTION OF THE MONTHLY YTD MASTER FILES
(MYTD and MYTDB)
Posi ti on
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
1 tern
Day
Distri
S uperv
Total
Total
Total
Total
Total
Total
Total
Total
Total
Total
Total
Total
Total
ct Number
i son N umbe r
Days of Data Used
Equipment Costs
Time to Route
Mi 1 es to Route
Time Spent Collect
i ng
Type Comment
1 n tege r
1 ntege r
1 nteger
Dol 1 ars
Mi n utes
Mi n utes
Miles Driven Collecting
Weight Col lected
Time Spent Transpo
rti ng
Pounds
M i nutes
Miles Driven Transporting
Number of Loads
Number of Loads to
Number of Loads to
Number of Loads to
1 nci nerator
Landf i 1 1
Transfer
Stati on
19 Sum of Vehicle Size
20 Total Number of Homes Served
21 Total Weight Collected First Loads
22 Number of First Loads
23 Number of Weighed Loads
24 Total Days of Data with Mileage
25 Sum of Crew S i ze
26 Number of Breakdowns
27 Number of Lunch Breaks
28 Total Days of Cost Data Used
29 Total Breakdown Time
30 Total Lunch Time
31
32 Total Manpower Costs
33 Number of Routes
Cub , -
Yards
Pounds
Mi nutes
Mi nutes
Dollars
Record Size
Block Si ze
= 136
= 5444
No. of Records: 6 for each supervisor +
6 for the city
29
-------
Figure II
DESCRIPTION OF THE EDITED DAILY DATA FILE
(DAILY)
Position Item
1 District Number
2 Route Number
3
4 Date
5 Equipment Cost
6 Total Time to the Route
7 Total Miles Driven to the Route
8 Total Time Spent Collecting
9 Total Miles Driven While Collection
0 Total Weight Col lected
1 Total Time Spent Transporting
2 Total Miles Driven While Transporting
3 Total Number of Loads
4 Total Number of Loads'to Incinerator
5 Total Number of Loads to Landfill
6 Total Number of Loads to Transfer
Station
7 Vehicle Size
8 Number of Homes Served
9 Weight Collected First Load
20 Number of Rrst Loads
21 Total Number of Weighed Loads
22 Number of Days of Data with Mileage
23 Crew Size
24 Number of Breakdowns
25 Number of Lunch Periods Taken
26
27 Total Breakdown Time
28 Total Lunch Time
29 Number of Estimated Mileages
30 Day
* 1 . Monday
2. Tuesday
3. Wednesday
4. Thursday
5. Friday
6. Saturday
Record Size = 124 No. of Records: one
data
Block Size = 124
Type Comment
1 nteger
1 nteger
Cents
Mi nutes
Mi nutes
Pounds
Mi nutes
Cubic
Yard
Pounds
Mi nutes
Mi n utes
for each day of
recei ved
-------
Fi gure 12
DESCRIPTION OF THE WEEKLY REPORT WORK FILE
(WRPT)
Pos
3
43
*l .
2.
3.
4.
5.
6.
7.
i t i on 1 tern
1 District Number
2 Route Number
- 42 Average Data
- 82 Sum of Average Data
83 Day
84 Vehicle Type
Monday
Tuesday
Wednesday
Th ursday
Fri day
Saturday
Average Day
Type
1 nteger
1 ntege r
Real
Real
1 nteger
Al pha-
Numeri c
Comment
See
Array (Out)
See
Array (Out)
*
The above record is generated for each Day, Route, Supervisor,
District, Area, and the City.
Position Item
Type
Comment
1-40 Daily Sum
Real
See Array
(Out)
The above record is generated for each Supervisor.
-------
Figure 12 (Cont'd)
Position I tern Type Comment
I - 40 YTD Averages Real See Array
(Out) !
The above record is generated for each Route, Supervisor, District,
Area, and the City.
Record Size = maximum 340 (variable)
Block Si ze = 5784
No. of Records: 7 for each route +
3 for each supervisor +
2 for each district +
2 for each area +
2 for the city
-------
Figure 13
DESCRIPTION OF THE MONTHLY REPORT WORK FILE
(MRPT)
Posi
3 -
43 -
* 1 .
2.
3.
4.
5.
6.
t i on 1 tern
1 District Number
2 Route Number
42 Average Data
82 Sum of Average Data
83 Vehicle Type
84 Day
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Type
1 ntege r
1 nteger
Re a 1
Rea 1
A 1 pha-
Numeri c
1 nteger
Comment
See Arra
(Out)
See Arra
(Out)
*
The above record is generated for each Route, Supervisor, and the
City for each day of the week (Mon-Sat).
Pos i t i on
I tern
Type
Comment
I - 40 YTD Average
Rea I
See Arra1
(Out)
The above record is generated for each Supervisor in the city for
each Hay of the week (Mon-Sat).
Record Size = maximum 340 (variable length)
Block Size = 5784
No. of Records: 6 for each route +
12 for each supervisor +
12 for the city
33
-------
Fi gure 14
DESCRIPTION OF THE DAILY DATA SORTED FOR MONTHLY FILE
(DSORTD)
Position Item Type
1 District Number Integer
2 Route Number Integer
3
4 Date
5 Equipment Cost
6 Total Time to the Route
7 Total Miles Driven to the Route
8 Total Time Spent Collecting
9 Total Miles Driven While Collecting
10 Total Weight Col lected
II Total Time Spent Transporting
12 Total Miles Driven While Transporting
13 Total Number of Loads
14 Tota.l Number of Loads to incinerator
15 Total Number of Loads to Landfill
16 Total Number of Loads to Transfer
Station
17 Vehicle Size
18 Number of Homes Served
19 Weight Collected First Load
20 Number of First Loads
21 Total Number of Weighed Loads
22 Number of Days of Data with Mileage
23 Crew Size
24 Number of Breakdowns
25 Number of Lunch Periods Taken
26
27 Total Breakdown Time
28 Total Lunch Time
29 Number of Estimated Mileages
30 Day
* 1. Monday Record Size = J 24
2. Tuesday
3. Wednesday Block Size = 124
4. Thursday
5. Friday No. of Records: one for each day of
Comment
Cents
Mi nutes
Mi nutes
Pounds
Mi nutes
Cub i c
Yards
Pounds
M i nutes
Mi nutes
*
data
6. Saturday
rece i ved
-------
CHAPTER I I
SPECIAL PROGRAMMING CONSIDERATIONS
Data Set
Fi les, or data sets, in a Fortran program are
referenced by use of Integer numbers (data set reference
numbers) which the computer's operating software can
equate to external file names and device assignments.
The data set reference numbers can either be literals
or variables within the program. The COLMIS program
uses variable names which are Initialized In statements
00000510-00000519. These are the standard data set
reference numbers which would be used on an IBM computer
with a full Operating System. Use of COLMIS with soft-
ware other than IBM/OS may require changing the values
of the data set reference numbers. This can easily be
accomplished by changing the Initialization of the file
variable names in lines 00000510-00000519 to reflect
the data set reference numbers which are standard for
your system. Once set In the main program, these
variables are stored in a common area accessible to all
subroutines. Therefore these are the only statements
that would need to be changed.
The following tables (-2 -^ 4) reflect the data set
reference numbers and job control language which would
be used under IBM/OS and IBM/DOS.
35
-------
CO
o
Q
'\
S
CD
to
ce
LU
CD
5£
^
Z
LU
4-
c
CD
E
CD c
O D)
> to
CD m
Q <
0
c
^~ C
(D 10
C Z
L.
0 0
4- —
X —
LU Lu
— CM ho -a- 1— iQvD r^
^Si ^5 Si ^5 Z to ^^ ISt ^Q
taCi^-Q— _j y», ts» -Q
totoco^ototocjto co
ir)<^iir>m to
-* CM fn ^~ in vo r^-
^Sl °C^ ^S ^5 TS 73 "t^
CO CO CO CO tO tO CO
>->->->- >- >_ >_
to to co co co to to
~) ~~> — > — 5 —3 — > —5
4- •
0 O
CO Z
(D •
4~ **~
(0 CD
Q Cf
*}• m\o r^ — ho OD trv o
0
^- — ~ — " ~~ — — "~ ~~ "— ~ ^~ — *
1 1 1 ^i ^31 ^i isi ^l 'a ^l >SL 1SI
CC. Ja ^Si ^a JSA TSk la Si IS. ^St
LU LULULULuLuLuLuLu U_
LU
LU
a:
\~
LU
CO tO
o
< ^
h- S
< CD
a —
a
ce
<
Q
0
E
(D
Z
— CM N"» ^ in vo co o» >si
isi ^i TS ^a ^i ^i ^i ^si ~—
HI— 1— h-l— 1— 1— 1— I—
LULuLuLuLuLULuLu LU
4- •
0 O
CO Z
(D •
4- •+-
(0 CD
Q a:
-~ CM r^ ^~ in vo oo CT* o
—
z
1
to en
CD
o
.- CO
(si > a.
CO >-
LU a h-
1
ce LU
*: # *: * LU h- * * *
\X v^ V y^ Q Q -^ V^ v^ v^
to coto coo:
Q
CD CO >- t—
QOQQ |— — 'I— Ct
K-I-H-I- ZD — Q. O
>>>>-ZO- h- 1- 4- 4- CD4-O
4-
CD
CO
ID
4-
ID
Q
-* >_>-(D (0 — (DM-
>-O>~ Q -0 (ft Q>-.-Q>~
•—ID — >~O->~ 04-"O — 4-Lu T3 —
.CCQ j: — 3 — 4- 4-L. 0>~^u. >~0j:
4- 4- -*.*: -2i 3 CO H 4-O-* — 4-4-
cQ c 00 0 Q- .- a. •— — CCLU. ~i_c
Ol— O 010 0 C L.0 TDID O0O (DOO
S>- S ^ CD X — Q-CC LUQ SCtS QcoS
OO
"^5
-sj
CO
CO
CO
Is
CO
>-
to
— o
—
—
1Sl
IS.
LU
—
«
1
Lu
—
*
V1
CO
—
Q
1-
Cu
01
2
+-
o
O-
0 0
a: —
~
>^ Lu
—
v' v*
0 u.
0 O
2 2
.
to
CD
0
•—
CD
13
0
O.
(D
4-
O
4-
•o
0
C
O)
.—
to
to
ID
0
0
C
(0
u
-o
C
ID
—
(D
—
4-
C
0
cr
0
to
0
t^
ID
to
0
—
•~
M-
U1
^*
T3
0
(fl
0
r~
^-
*
-------
TABLE 3. SAMPLE JOB CONTROL LANGUAGE FOR COLMIS
EXECUTION - IBM/DOS
// JOB COLMIS SOLID WASTE COLLECTION MIS
// ASSGN SYS00I,X'131'
// DLBL IJSYS0I,'MONTHLY YTD BACKUP'
// EXTENT SYS00I,,I,,'00020,00100
// ASSGN SYS002,X'131'
// DLBL I JSYS02,'MONTHLY YTD'
// EXTENT SYS002,,I,,00120,00100
// ASSGN SYS003,X' 131 '
// DLBL IJSYS03,'WEEKLY YTD BACKUP'
// EXTENT SYS003,,I,,00220,00100
// ASSGN SYS004,X' 131 '
// DLBL IJSYS04,'WEEKLY YTD'
// EXTENT SYS004,,I,,00320,00100
// ASSGN SYS005,X' 131 '
// DLBL IJSYS05, ' EDITED DAILY DATA'
// EXTENT SYS005,, I , ,00420,0)3100
// ASSGN SYS006,X' I 31 '
// DLBL IJSYS06,'MONTHLY RPT WORK'
// EXTENT SYS006,,I,,00520,00100
// ASSGN SYS007,X'131'
// DLBL IJSYS07,'DAILY SORTED FOR MONTHLY'
// EXTENT SYS007,,I,,00620,00100
// ASSGN SYS008,X'131'
// DLBL IJSYS08,'WEEKLY RPT WORK'
// EXTENT SYS008,,I,,00720,00100
// ASSGN SYSLST,X'OOe'
// ASSGN SYSIN,X'00c'
// EXEC COLMIS
- DATA CARDS -
/*
/&
NOTE: TO AID IN DETERMINING THE SIZE FOR EACH FILE,
SEE FIGURES 9JTHROUGH 14 IN VOLUME II
FOR SIZE AND" NUMBER OF RECORDS.
37
-------
TABLE 4.SAMPLE JOB CONTROL LANGUAGE FOR COLMIS
EXECUTION - IBM/OS
//COLMIS JOB . . . REGION=82K
// EXEC PGM=COLMIS
//STEPLIB DD UNIT=3330,VOL=SER=TS00|4,DISP=SHR,
// DSN=CITY.MIS.LIB
'//FT0IF00I DD DSN=COLMIS.MYTDB,DISP=OLD,
// UNIT=3330,VOL=SER=TS00I4
//FT02F00I DD DSN=COLMIS.MYTD,DISP=OLD,
// UNIT=3330,VOL=SER=TS00I4
//FT03F00I DD DSN=COLMIS.WYTDB,DISP=OLD,
// UNIT=3330,VOL=SER=TS00I4
//FT04F00I DD DSN=COLMIS.WYTDB,DISP=OLD,
// UNIT=3330,VOL=SER=TS00I4
//FT08F00I DD UN IT = SYSDA,SPACE=(CYL,(I, I ))
//FT09F00I DD UN IT=SYSDA,SPACE=(CYL,(I, I )),
// DCB=(RECFM=VBS,LRECL=340,BLKSIZE=5784),
// DSN=&&TEMP,DISP=(NEW,DELETE)
//FTI0F00I DD UNIT=SYSDA,SPACE=(CYL,(I,I))
//FTIIF00I DD UNIT=SYSDA,SPACE=(CYL,(I,I)),
// DCB=(RECFM=VBS,LRECL = 340,BLKSIZE='5784),
// DSN=&&TEMX,DISP=(NEW,DELETE)
//FT06F00I DD SYSOUT=A
//FT05F00I DD *
- data -
/*
NOTE (I): TO AID IN DETERMINING THE SIZE FOR EACH FILE,
SEE FIGURES 9 THROUGH 14 IN VOLUME II
FOR SIZE AND NUMBER OF RECORDS.
NOTE (2): ON THE INITIAL RUN OF THE SYSTEM, IT WILL BE
NECESSARY FOR FILES FTOI, FT02, FT03 and
FT04 TO SET DISP=(NEW,KEEP) AND USE THE SPACE=
PARAMETER TO ALLOCATE DISK SPACE FOR THE
FlLES.
-------
Segmentation for Smaller Computers
The COLMIS program requires approximately I 12K of
core memory if all routines are constantly core resident.
However, it can easily be segmented if used with operating
software which makes provisions for overlaying of programs,
Some systems take the problem completely out of the pro-
grammer's hands by dynamically overlaying the program
during execution. Such systems can fit a program into
practically any amount of core.
Some other systems, such as IBM/OS, provide for
overlaying if the overlay structure is specified by the
programmer before the execution phase. Under IBM/OS, no
modification needs to be made to the source program deck;
the overlay structure is simply specified during the
linkage editor phase. The job control language needed for
compile and linkage editing is illustrated in Table 5.
There are systems such as IBM/DOS which require the
program to call a system subroutine to initiate the over-
lay process duri'ng execution. This will require program
modification before compiling, and also special job con-
trol language structuring during linkage editing. Under
IBM/DOS, before a call to a program subroutine is
executed, a call to the system subroutine "OPSYS" must
be executed to load the program subroutine into memory.
The placement of these statements are detailed in Table 6
The job control needed during _the compile + linkage
edit are illustrated in
The structure of the COLMIS program simplifies the
overlaying process. It is, of course, necessary to keep
the main program core resident. Due to frequent use by
many subroutines, the subroutines HILO and SOLVE should
be kept core resident. It should be noted that under
some systems if one overlay routine calls another (which
overlays or replaces the first one), a return cannot be
made into the calling routine, thus necessitating core
residency of these two routines. Each of the other sub-
routines is essentially an independent function and
therefore are ideal program segments for overlaying.
This type of overlay structure will reduce COLMIS to
approximately 56K.
39
-------
TABLE 5. SAMPLE JOB CONTROL FOR COMPILE AND LINKAGE
EDIT WITH OVERLAY STRUCTURE - IBM/OS
//COLMIS JOB
// EXEC FORTGCL,PARM.LKED='LET,L1ST,XREF,0VLY'
//FORT.SYSIN DD *
- source program -
/*
//LKED.SYSLMOD DD UN IT=3330,DISP=(NEW,KEEP),
// VOL=SER=TS00I4,DSN=C1TY.MIS.LIB(COLMIS),
// SPACE=(TRK,(20,I,5),RISE),
// DCB=(RECFM=U,BLKSIZE=13030)
//LKED.SYSIN DD *
OVERLAY ALPHA
INSERT FILEI
OVERLAY ALPHA
INSERT FILE2
OVERLAY ALPHA
INSERT DUMPFI
OVERLAY ALPHA
INSERT EDIT2
OVERLAY ALPHA
INSERT WKCOMP
OVERLAY ALPHA
INSERT WKPRIN
OVERLAY ALPHA
INSERT MOCOMP
OVERLAY ALPHA
INSERT MOPRIN
OVERLAY ALPHA
INSERT SMPRIN
OVERLAY ALPHA
INSERT MAPRIN
/*
-------
O
Q
CD
I
CD
O VO
us ta na isi ts is
ts ts tsi xs >a isi
I/)
(D
L ID
JD
3 0)
in en
(D
0-a
c
->->->->- c>-v>->->->-
cococococo — cocococococo
Q-CLQ.Q-Q_-)-Q-CLQ-CLQ-Q.
OOOOO (DOOOOOO
—I—l_l—I—I 0) —I —I —I —I —I —I
—l_l—I—I_J-U_I—I—I—J—I—I
0)
coo)
Via
tou
CL O)
Oc
(D
O—
•00
0)1-
tn+-
tnc
ID O
0.0
"-.a
0) o
OOOOO >-O O O O
J3
O
a: ce a: n: cc CD a: Q: a: CL cr a:
UjujLaJLLlUJZUJUJLLlUJLLlLLl
cococococo
UJ
o
z
41
-------
TABLE 7. SAMPLE JOB CONTROL FOR COMPILE AND LINKAGE
EDIT WITH OVERLAY STRUCTURE - IBM/DOS
// JOB CO'LMIS COMPILE, LINK, CATALOGUE
// OPTION CATAL
PHASE COLMIS ROOT
// EXEC FORTRAN
- MAIN (SOURCE 00000010 - 00000920) -
- SOLVE (SOURCE 00035020 - 00036790) -
- HILO (SOURCE 00036800 - 00037070) -
/*
PHASE FILEI,*
// EXEC FORTRAN
- FILEI (SOURCE 00000930 - 00001560) -
/*
PHASE FILE2,FtLEI
// EXEC FORTRAN
- FILE2 (SOURCE 00001570 - 00001970) -
/*
PHASE DUMPFI,FlLEI
// EXEC FORTRAN
- DUMPFI (SOURCE 00001980 - 00002820) -
/*
PHASE EDIT2,FILEI
// EXEC FORTRAN
- EDIT2 (SOURCE 00002830 - 00007690) -
/*
PHASE WKCOMP,FlLEI
// EXEC FORTRAN
- WKCOMP (SOURCE 00007700 - 00011860) -
/*
PHASE WKPRIN,FlLEI
// EXEC FORTRAN
- WKPRIN (SOURCE 00011870 - 00015780) -
/*
PHASE MOCOMP,FILEI
// EXEC FORTRAN
- MOCOMP (SOURCE 00015790 - 00019060) -
-------
Table 7. (cont'd)
/*
PHASE MOPRIN,FILEI
// EXEC FORTRAN
- MOPRIN (SOURCE 00019070 - 00024450) -
/*
PHASE SMPRIN,FlLEI
// EXEC FORTRAN
- SMPRIN (SOURCE 00024460 - 0028070) -
/*
PHASE MAPRIN,FILEI
// EXEC FORTRAN
- MAPRtN (SOURCE 00028080 - 00035010) -
/*
// EXEC LNKEDT
/*
/&
-------
Modification for Approximating Weight from Cubic Yardage
Sometimes it is not possible to obtain weights of
the solid waste vehicles to determine the amount of
refuse collected. Rather than lose the valuable infor-
mation based on weight in the COL.MIS reports, a useable
approximation can be made. If cubic yards are estimated
and entered on the data col lection sheets in place of
weights, a simple change in the EDIT2 subroutine can
trigger the conversion of volume to weight. Using a
representative, city-wide figure for pounds per cubic
yard (compacted inside the vehicle) change statement
00003175 by substituting this pounds per cubic yard
estimate for the constant "1.0". This will cause the
weight of the refuse to be calculated In statement 0000
5700. If this conversion technique is used, it is
necessary to specify a tare weight of zero for all
vehicles when entering the background data into the pro-
gram, see Volume I, Chapter II or Volume II Chapter 1,
Background Data sections.
Modification for Other Route Numbering Schemes
The route numbering system in COLMIS norma.lly allows
for a maximum of nine routes per supervisor. This can be
changed to allow for ten or more routes per supervisor
but it will reduce the number of levels of organization
which can be defined by the route numbering scheme. A
maximum of four levels can be defined when using a two
digit route number. For example, using the route
number 23-11:
2 represents the second district
3 represents the third route supervisor
(foreman) of the second district
I) represents the eleventh route under
the third route supervisor (foreman)
of the second district
The top level of management is assumed and represented by
the number 99-99. For further discussion on the logic of
route numbering schemes see Volume '» Chapter II, Route
Numbering Systems.
To allow for the use of a two digit route nuniber,
source program changes must be made as indicated tn
TabU 8,
44