This user note has relevance only to users of the RL 360/195, and describes the use of the subroutine TOMUG which has been added to the SMOG and SCFOR graphics packages.
Several users of the 360/195 SMOG and SCFOR packages have found the need to send some of their graphical output, which is being spooled, to the MUGWUMP filestore for examination, Users have in the past tried three methods all with serious disadvantages. These are listed below.
Firstly users have tried to mix calls to MUGWUMP routines with calls to SMOG or SCFOR in the same job step. This causes problems in the Link edit step since some routine names are common to both packages whilst their functions are completely different, This drawback has involved the user in a rather messy linkedit step with the inclusion of routines from libraries and the changing of names. Also mistakes here can cause difficulties in debugging the program.
The second method most frequently tried is the use of SMOG or SCFOR to produce a scratch dataset, processing this dataset with VIEW$ to obtain the frame s in the mugwump file ar.d then processing this file with HRMUG to obtain FR80 output. Apart from the obvious tedium of this process there are several more serious disadvantages. VIEW$ is primarily intended to be a debugging aid and as such pictures the entire 16K raster which the packages consider to be the basic region. Hence when reprocessed with HRMUG the frame becomes smaller by a factor of as much as 40% dependent on the camera selected in the original graphics job. Also such settings as character height, intensity and picture definitions will be lost.
The third method is the simplest and in most cases totally unacceptable since it involves the rerunning of the job to produce a scratch dataset for processing by VIEW$. Here the disadvantage is obviously the time wastage incurred.
With these points in mind a new routine has been incorporated into the SMOG and SCFOR libraries and is called TOMUG.
TOMUG is a routine which will route a copy of the graphical output from SMOG or SCFOR to a dataset assigned to a fortran stream number. The routine has one argument of type integer and this argument specifies the fortran stream number to which the copy is to be sent. This copy may later be processed by VIEW$ and, using the options specified in FR80 User Note 9, frames may be selected and sent to MUGWUMP.
It is important that if TOMUG is used it must be called as the first graphical subroutine and should not be called again.
It should also be noted that if TOMUG is used then TOPRIN will not work and should not be called. This however should not be of any disadvantage since printing may be turned on in VIEW$ which will also partially decode the graphical orders.
(1) A program using the SCFOR package in which the first five frames are to be sent to MUGWUMP. Scratch dataset on stream 17
//XAIDJBNM JOB (ACCT,ID),ANYBODY
// EXEC FORTH,SYSLIB='SYS1.SCFOR',CPRINT=YES
//C.SYSIN DD *
CALL TOMUG(17)
CALL SELECT(2)
CALL IDST
Fortran statements
CALL IDEND
STOP
END
//G.GRAPHICS DD SYSOUT= (G,, HCM)
//G.FT12F001 DD SYSOUT=A,DCB=PRINTER
//G.FT17F001 DD DSN=&&SCRA,UNIT=WORK30,
// SPACE=(CYL,(2,1)),DCB=XAFRDISK,DISP=(,PASS)
// EXEC VIEW$,PARM.G='E=5'
//G,FT14F001 DD DSN=&&SCRA,UNIT=WORK30,DISP=(OLD, DELETE)
(The user will notice in the above example that VIEW$ is now a procedure and that the JCL shown is all which is required to run it)
(2) A SMOG job in which all frames are to be sent to mugwump and in the VIEW$ step all orders are to be printed, This may cause a large amount of output. Scratch dataset on stream 20.
//XAIDJBNM JOB (ACCT,ID),ANYBODY
//EXEC FGCLG,SYSLIB='SYS1.SMOG',REGION.G=150K
//C.SYSIN DD *
CALL TOMUG(20)
CALL FRBW35
Fortran Statments
CALL ENDSPR
STOP
END
//G.GRAPHICS DD SYSOUT=(G,,BW35)
//G.FT12F001 DD SYSOUT=A,DCB=PRINTER
//G.FT20F001 DD DSN=&&SCRA,UNIT=WORK30,DISP==(,PASS),
// SPACE=(CYL,(2,1)),DCB=XAFRDISK
// EXEC VIEW$,PARM.G='P=1'
//G.FTl4F001 DD DSN=&&SCRA,UNIT=WORK30,DISP==(OLD,DELETE)