Please document the different SNOBOL processors in mvstk5

[rvjansen]

In the foreground and background ISPF menus Sptibol is already added. The load module is not on the system. In xmi/spitbol.xmi.zip (compressed xmit file) is everything that is needed to link the load module. When received, it restores to userid.newbol.src - the job linksbol in that dataset is a a good model. This is what I used on mvstk5:

//AB2217#  JOB CLASS=A,MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID  
//CLEAN   EXEC PGM=IEFBR14                                       
//*SYSLMOD  DD  DSN=SYS2.NEWBOL.LOAD,DISP=(OLD,DELETE)           
//LINK    EXEC LKED                                              
//SYSPRINT DD  SYSOUT=*                                          
//SYSLMOD  DD  DSN=SYS2.NEWBOL.LOAD,DISP=(NEW,CATLG),            
//             UNIT=SYSDA,VOL=SER=TSO001,SPACE=(CYL,(5,1,10)),   
//             DCB=(DSORG=PO,RECFM=U,BLKSIZE=19069)              
//OBJS     DD  DSN=SYS2.NEWBOL.SRC,DISP=SHR                      
//SYSIN    DD  *                                                 
 INCLUDE OBJS(SBOLOBJ)                                           
 ENTRY OSINT                                                     
 NAME SPITBOL(R)                                                 
/*                                                               
//                                                               

With 3.3 the load module (SPITBOL) can be copied to SYS2.LINKLIB

[peter-sylvester]

For some time now I was motivated by a small challenge from Jay. I have ONE job to compile the SPITBOL 370 source, actually 2, one for TK5 using ASMG and another for Z/OS.

One other reason: The LOADMODS contain binaries no longer useful, or some stuff for CMS. I don't think it is a good idea to use SYS2.LINKLIB. There maybe some naming conflicts

The essential documentation: the green snobol4 book and the spitbol370reference from 1984.

I just hacked a small edelweb.eu/spitbol : spitbol.jcl.xmi

A spitbolZ? (a64 bit version?) The whole spit370 is not even 31bit. The so called 371 version at Jay's site does not even compile. I already have a 372 version, not really necessary for TK5 (for the moment).

Note: The 370 version has some nice new features, e.g. pds members and directory stuff.

[rvjansen]

I changed the title because I know since yesterday that there is a special volume (SYSCPK) dedicated to the languages supported by mvstk5; I will deliver some text to add to the manual(s).