Re: Compile and run later

  From: Ron Hudson 
  Sent: Tuesday, May 18, 2010 10:33 PM
  Subject: [turnkey-mvs] Compile and run later

  I would like to start creating programs that I can run from a TSO session, interactively.
Ron,

I recalled something I wrote. You might find this helpful:


--------------------------------------------------------------------------------

From: Andreas F. Geissbuehler 
To: [email protected] 
Sent: Saturday, April 26, 2008 8:28 AM
Subject: Re: [turnkey-mvs] PA1 in wc3270

Original Message From: M. Khalid Khan 
> ...and it insists that you enter "type", whatever that "type" is. 
> CAN ANYONE OF YOU GURUS TELL WHAT THE HECK IS THIS
> PROGRAM  ASKING FOR ? OR HOW CAN IT BE MADE TO SHUT UP ?

Not sure but I believe this is what you are after:
ASM for Assembler source
COB for COBOL source
CNTL for JCL
CLIST for clists
LIST, OUTLIST, TESTLIST
OBJ
LOAD
PL1, FORT, RPG, ...
DATA for all else

If you enter HELP COMMANDS you see the original repertoire of
TSO commands. Before SPF (prior to 1975) that was all there was.
Some, like the VSAM-related came later (with VS1 and VS2 TSO).

The idea was to save keystrokes and keep order.

EDIT TEST(GENER) CN
edits GENER in the 'KHAN.TEST.CNTL' pds

EX DRYRUN
EXecutes the clist in 'KHAN.DRYRUN.CLIST'
where
KHAN is typically the TSO user-id or better explained,
the prefix from PROF PREF(prefix)

If you want to use TSO wihout adhereing to the naming
convention you can do so, provided you enter the FQDSN:
EDIT 'KHAN.TEST.JCLLIB(GENER)' CN

did you notice? ... the 'CN' ? (short for CNTL)
I believe this is the source of your frustration.
Now, I hope you find the rest by entering
HELP cmd
e.g. HELP EDIT or HELP EDIT SYN, 
HELP COB, HELP EX, HELP ASM, HELP LINK ...

Look, here are the guts of a typycal TSO session, say 1974,
what a user might have typed on his 3270 screen:

EDIT DRYRUN ASM NEW
...enter the program
ASM DRYRUN (assemble it)
LINK DRYRUN (link it)
EDIT DRYRUN CL NEW
... enter your dataset ALLOCs
... enter CALL DRYRUN
... enter your dataset FREEs
EX DRYRUN
... oops, it abended
TEST (by itself, or TEST DRYRUN)
EDIT DRYRUN ASM
L 100 (now put cursor up on displayed line, 
overtype the bad, hit ENTER
END SAVE
EX ASMFCL DRYRUN (forgot, I once made a clist, let's use it here)
EDIT DRYRUN CN NEW
...enter JOB, EXEC, DD
end save
SUB DRYRUN

Hopefully the above 'example' helps to understand why the dataset
types were a good thing. It also made it easier to manage your
disk space, E.G. the above example would have allocated and used:
KHAN.DRYRUN.ASM
KHAN.DRYRUN.CLIST
KHAN.DRYRUN.CNTL
KHAN.DRYRUN.LIST
KHAN.DRYRUN.LOAD
KHAN.DRYRUN.OBJ

Hope that 'HELP's..!

Andreas F. Geissbuehler
AFG Consultants Inc.
http://www.afgc-inc.com/