CMSTPF What's New on the Host 02.00.01

What’s New in CMSTPF; SOURCE VIEW & CTFS in Host 02.00.01

Distribution in $DISKARC format

With Host 02.00.01 all software distributed for Host Files is in the $DISKARC format. This file format has a better compression ratio and is more efficient in transferring file from our website to the customer.

To use the $DISKARC format, please review the instructions $DISKARC Procedures. To obtain the $DISKARC.EXEC and VMARCHIV.MODULE contact TPF Software, these 2 files are needed to use the $DISKARC format.

Support for TPF/GI 4.0.1

CMSTPF, SOURCE VIEW and CTFS have been updated to support TPF/GI Version 4.0.1. The customer versions of $QHOST.TABLE and the $RHOST.TABLE should be updated to reflect that CMSTPF 02.00.01 supports TPFGI Version 4.0.1.

Support for NON�standard ECB (customized ECB)

With Host 02.00.01, CMSTPF has support for non-standard ECB definitions. If a customer has an ECB that does not match the standard ECB as defined by the IBM TPF product, the ECB was not supported by CMSTPF. With this Host/Release CMSTPF can now handle these non-standard ECBs.

Support for TPF Put 25

Host 02.00.01 has support for TPF Put 25. With this Release/Version, the TPFPUT level can be set to 25 (if the customer is running TPF Put Level 25). The TPFPUT option of the $CSYS macro supports Put 25.

Support for zOS 1.1.1

Host 02.00.01 has support for the zOS 1.1.1 C/C++ compiler, with this version of zOS, the compiler generated information for debugging a C/C++ program changed in the C/C++ program header. This version fixes the C/C++ program header changes due to the zOS 1.1.1 compiler.

Support for 64K cylinders on 3390 disks

With Host 02.00.01, CMSTPF has been updated to allow an installation to define 3390 disk devices with up to 64K number of cylinders. The $CDEV macro now allows for up to 65,535 cylinders to be defined.

Generating Source View Control files for Assembler Programs - from SYSADATA output

With Host 02.00.01 the $ASVGEN commands should NOT be used to generate the Source View Control files for Assembler programs.

The ADATA information can be generated in VM, zOS or Linux and then the STRPADTA routines should be invoked to generate the Source View files.

The document explaining the STRPADTA process is STRPADTA process.

Generating Source View Control files for C/C++ Programs

With Host 02.00.01 the $CSVGEN command should NOT be used to generate the Source View Control files for C/C++ programs. C/C++ programs should be compiled with the TEST option (refer to the COMPILE OPTIONS file on the CMSTPF Install disks). Compiling the programs with the TEST option causes the SV line table and variable information to be generated.

Support for the DIGNUS C/C++ Compiler

With Host 02.00.01 CMSTPF and TPFGI now support the DIGNUS C/C++ compiler. Programs compiled using the DIGNUS compiler can now be Source View traced.

The DIGNUS compiler has been updated to generate correct DEBUG information for TPFGI.

Support for 200 $CUDA macros

Host 02.00.01 Build 080612 has support for up to 200 data areas.

Support for 16 I-Streams

Host 02.00.01 Build 080625 has support for 16 I-Streams, space is now carved out for up to 16 I-Streams in the SSUT tables.

GETSWB and RELSWB functions are now supported in the $USREXT

Host 02.00.01 Build 080519 has support for customers to issue the GETSWB and RELSWB functions inside the User Exit Routines ($USREXT.ASSEMBLE).

RTF Updates

No major updates done for RTF.

CTFS 02.00.01 - Updates

For customers NOT using CTFS, this whole section can be skipped.

Several new features of CTFS have been added with this Release/Version, the features are:

Allow for 2 megabyte transfer between CMSTPF clients and the TPF Server
- This feature caused changes in both CMSTPF and TPF Server programs, and the procedure below describes how to migrate to CMSTPF 02.00.01while still using CTFS 01.04.01 or CTFS 01.04.02.
Allow for User Command in CTFS – ZCTFS UCMD support
- This feature allows for user commands to be passed between the CMSTPF client and the TPF Server. This requires updates to C3SX/C4SX – the customer should update their user exit programs (C3SX/C4SX) to use this feature.
- Please contact TPF Software if you have questions on using this feature.
Allow for an updated and full feature Context Table in CTFS
- This feature allows for a new Context Table support in CTFS, some customers are already using the existing Context Table support supplied as a sample in earlier CTFS versions. If the customer wishes to use the new context table support, then 2 new programs are supplied C3SZ/C4SZ are also supplied and need to be allocated.
- Sample code is supplied in C3SX42.ASSEMBLE and in C3SZ41.ASSEMBLE for customers using SNA support, and sample code is provided in C4SX42.ASSEMBLE and C4SZ41.ASSEMBLE.
- Please contact TPF Software if you have questions on this feature.

These new features caused extensive changes in the CTFS routines (ECB programs in the TPF Server). Customers who are currently running CTFS have the following options when installing Release 2.0.1, they are:

Check the date of $TFSFUN.TEXT on your current CMSTPF system.
If the date of $TFSFUN.TEXT is newer than 01/01/2008, then the new version CMSTPF 02.00.01 is compatible with the existing CTFS Server ECB programs, and you can run the new CMSTPF 02.00.01 along with the CTFS 01.04.01 or CTFS 01.04.02.
If the date of $TFSFUN.TEXT is older than 01/01/2008 then the new CMSTPF 02.01.01 is not compatible with the existing E-type programs associated with CTFS, and to use CMSTPF 02.00.01, you have to use the $TFSFUN.OTEXT file, which is compatible with your existing E- type CTFS Server programs.
The procedure for customers with $TFSFUN.TEXT older than 01/01/2008 is as follows:
- Install CMSTPF 02.00.01 on your test CMSTPF Installation Id
- Rename $TFSFUN.TEXT. to $TFSFUN.NEWTEXT.
- Rename $TFSFUN.OTEXT to $TFSFUN.TEXT
- This allows the new CMSTPF 02.00.01 to run with the older CTFS Server programs
- This also provides more time to get CMSTPF 02.00.01 to be checked out and to go production.
- After CMSTPF 02.00.01has been in production, implement all the CTFS ECB programs and get them tested and loaded to your VPARS system.
- Once it is loaded the $TFSFUN.NEWTEXT (created earlier), can be renamed to $TFSFUN.TEXT and the CMSTPF Control program saved ($SAVECP).

For additional information or if you have technical questions, please contact TPF Software.

CMSTPF – Other problems/fixes

Other problems/fixes related with CMSTPF that have been fixed with this Release/Version can be viewed at the following link.

http://www.tpfsoftware.com/support/buildinfo.phtml

SOURCE VIEW – Other problems/fixes

Other problems/fixes related with SOURCE VIEW that have been fixed with this Release/Version can be viewed at the following link.

http://www.tpfsoftware.com/support/buildinfo.phtml

CTFS – Other problems/fixes

Other problems/fixes related with CTFS that have been fixed with this Release/Version can be viewed at the following link.

http://www.tpfsoftware.com/support/buildinfo.phtml

$DISKARC Procedures

Usage Data

Need FTPSERVE on VM
Need exec $DISKARC.EXEC on host to run this procedure
Need module VMARCHIV.MODULE on host to run this procedure
Both these files ($DISKARC.EXEC and VMARCHIV.MODULE) should be saved in the customers tools disk (Y-disk, etc.)
(If you need these files, download from TPF Software website or contact TPF Software)
Warning: $DISKARC always unpacks files to the A-disk

CMSTPF.193 disk – C-Drive.zip

This zip file contains the entire CMSTPF.193 disk - C-Drive host files.
The C-Drive host files are the Base User Disk (C-disk).

The procedure to unzip and load the entire C-drive is as follows:

Unzip the file on the PC and call it CDRIVE.BIN
Log on to the CMSTPF Test Id
Backup Test Id to virtual tape (if necessary)
Transfer C-drive files to host (Use FTP Procedure, listed below)
Call the file CDRIVE BIN – Temporary file on the host
On the 193 disk – 193 disk is usually the C-disk
Erase all files, except the CDRIVE BIN file – (TPF Software always ships a full replacement)
ACC 193 A – $DISKARC unpacks to the A-disk
$DISKARC UNARCHIVE A CDRIVE BIN A – Receives and unpacks the files
ERASE CDRIVE BIN A – Erase the Temporary file
IPL CMS
Should have all the files on the C-Drive

CMSTPF.194 disk – D-Drive.zip

This zip file contains the entire D-Drive host files.
The D-Drive host files are the Base Installation Disk (D-disk).

The procedure to unzip and load the entire D-drive is as follows:

Unzip the file on the PC and call it DDRIVE.BIN
Log on to Test Id
Transfer to host (Use FTP Procedure, listed below)
Call the file DDRIVE BIN – Temporary file on the host
On the 194 disk – 194 disk is usually the D-disk
Erase all files, except the DDRIVE BIN file. – (TPF Software always ships a full replacement)
ACC 194 A – $DISKARC unpacks to the A-disk
$DISKARC UNARCHIVE A DDRIVE BIN A – Receives and unpacks the files
ERASE DDRIVE BIN A – Erase the Temporary file
IPL CMS
Should have all the files on the D-Drive

CTFS.191 disk – F-Drive.zip

This zip file contains CTFS host files (F Drive) (If CTFS installed).

The procedure to unzip and load the entire F-drive is as follows:

Unzip the file on the PC and call it FDRIVE.BIN
Log on to Test Id
Transfer to host (Use FTP Procedure, listed below)
Call the file FDRIVE BIN – Temporary file on the host
On the 196 disk – 196 disk is usually the F-disk
Erase all files, except the FDRIVE BIN file. – (TPF Software always ships a full replacement)
ACC 196 A – $DISKARC unpacks to the A-disk
$DISKARC UNARCHIVE A FDRIVE BIN A – Receives and unpacks the files
ERASE FDRIVE BIN A – Erase the Temporary file
IPL CMS
Should have all the files on the F-Drive

APMSERVE.192 disk – I-Drive.zip

This zip file contains APMSERV host files (I Drive).
This is the 192-disk of the APMSERV Virtual machine.
APMSERVE should have a 191 disk � which should contain all the installation configuration files and installation modified execs.

The procedure to unzip and load the entire I-drive is as follows:

Unzip the file on the PC and call it IDRIVE.BIN
Log on to Test APMSERV Id – **Test APMSERV Id
Transfer to host (Use FTP Procedure, listed below)
Call the file IDRIVE BIN – Temporary file on the host
On the 192 disk – 192 disk is usually the I-disk
Erase all files, except the IDRIVE BIN file. – (TPF Software always ships a full replacement)
ACC 192 A – $DISKARC unpacks to the A-disk
$DISKARC UNARCHIVE A IDRIVE BIN A – Receives and unpacks the files
ERASE IDRIVE BIN A – Erase the Temporary file
IPL CMS
Should have all the files on the 192 disk of the APMSERV Test Id.

FTP Procedure using TCPIP

Procedure to move a PC file from the PC to the Host.

(Note: The sample session is for the Cdrive, this same procedure should be used for transferring each of the different drives).

Start an MS/DOS Prompt session
Switch to the directory where the unzipped Host file are defined
Ex. If the Host files are unzipped in a MISC directory, and if the files are:
CDRIVE.BIN; DDRIVE.BIN; FDRIVE.BIN & IDRIVE.BIN
Then CD/MISC – Switch to the Miscellaneous directory
FTP vmid – FTP to the VM system – Ex. FTP VM4
Will prompt for a User Id – Enter User Id – Ex. CMSTPFxx
Will prompt for a Password – Enter Password – Ex. password
CD CMSTPFGI.193 – Switch to the 193 disk or whatever disk
(Note: Need write access to disk, you may have to logoff the User Id)
(Note: If the disk has a write password, use QUOTE ACCT write_password)
BINARY – Set transfer to binary/image
QUOTE SITE FIX 80 – Set transfer to fixed 80 byte records
PUT CDRIVE.BIN CDRIVE BIN – Transfers CDRIVE.BIN to host & call it CDRIVE BIN
QUIT – End FTP session
EXIT – Exit DOS Prompt session

PC3270 Transfer Procedure

WARNING: Use only if TCPIP FTP not available on VM system.

Procedure to move a PC file from the PC to the Host

(The sample session is for the Cdrive, this same procedure should be used for transferring each of the different drives).

Unzip the CDRIVE.ZIP file, should contain a file called CDRIVE.BIN
Transfer the file to the Host VM User Id.
Erase all files on the C drive, before the transfer
Call the file CDRIVE BIN on the host VM system
For the transfer use the following 3270 transfer options:
- BINARY
- LRECL 80
- RECFM F
At the end of the transfer (takes a long long time) should have the CDRIVE BIN
File on the host C drive.
End the PC3270 transfer

STRPADTA Process

Purpose

Purpose of STRPADTA program is to read in a SYSADATA file and generate CMSTPFCT, CMSTPFSF, and/or Error File for TPF/IDE. The CMSTPFCT and CMSTPFSF files are used by TPF/GI while debugging Assemble programs. The Error File is used by TPF/IDE at the end of a compile from TPF/IDE.

Platforms

STRPADTA program is available currently on z/VM, z/OS, and Windows Platforms. All Windows Platforms are supported. There are plans to have STRPADTA available on LINUX in the near future.

Format and Parameters

STRPADTA format:

STRPADTA {options} sysadatafile

Where:

STRPADTA — Execute Program

{options} — -i, -ct, -mct, -sf, -fsf, -er, -s, -id, -seh -gs -spoff

Sysadatfile — Location of SysAdata File (output from Assemble Program)

Option parameters:

-i Display Informational messages during processing STRPADTA

-ct ctfilename Generate a CMSTPFCT file called ctfilename

-mct Generate a Minimize CMSTPFCT File (each record only 12 bytes instead of 100)

-sf sffilename Generate a CMSTPFSF file called sffilename

-fsf reclen Make each Record in CMSTPFSF file reclen long by storing multiple and partial lines together

-er errfilename Generate an Error File errfilename (format of Error file is TPF/IDE format)

-seh When generating Error File do not create the Header Line (-s and -id not required if this option is specified)

-s sourcefn When building header of Error file use sourcefn as the Source Filename (format of filename.fileext)

-id idno When building header of Error file use idno as the ID Number for the Header

-gs sourcefilename Generate an source file called sourcefilename

-spoff When building source file, do not include lines within print off (lines will not be included for source file and CMSTPFCT file)

Using STRPADTA with z/VM Assembles

Location of Files

CMSTPF.193 (C Disk) has all files necessary to convert SYSADATA file to CMSTPFCT and CMSTPFSF Files.

STRPADTA.MODULE, $ASVADAT.EXEC, and $SFUNP.EXEC are required files. If your build does not include these files contact TPF Software Inc. for an update.

Options for HLASM

When invoking the HLASM on z/VM option of ADATA needs to be specified. This option will create a SYSADATA file on the A disk.

The file name of the SYSADATA file will be same as the assemble program being assembled.

The SYSADATA file can be fairly large so plenty of disk space is needed on users A disk.

Invoking STRPADTA process after Assemble ($ASVADAT)

For VM it is recommended you do not invoked STRPADTA program directly, instead use $ASVADAT Exec to generate CMSTPFCT and CMSTPFSF files.

Format: $ASVADAT sysadatafile { ( outputfm}

Sysadatafile – Filename, Fiilename/Filetype, or Filename/Filetype/Filemode can be specified. If Filetype is not specified SYSADATA is used and if Filemode is not specified all disks are searched for Sysadata file.

( outputfm – Optional parameter to specify output filemode of CMSTPFCT and CMSTPFSF files that will be generated. If not specified same filemode as the sysadatafile will be used.

Return Code of 0 indicates process completed without error, non-0 indicates an error.

Using STRPADTA with z/OS Assembles

Location of Files

STRPADTA

STRPADTA Module is required for generating CMSTPFCT and CMSTPFSF files on z/OS.

Download and unzip STRPADTA.XMI (XMIT format) from TPF Software Download page to a PC Drive.

Create your PDS/E (Library) you want to store STRPADTA Module in on z/OS (for our example we will use TPF.TPFGI.LOADLIB).

PDS/E Attributes:

Space Units: CYLINDER
Primary quantity: 5
Secondary quantity: 5
Directory blocks: 0
Record format: U
Record length: 0
Block Size: 6144
Data set name type: LIBRARY

Create a temporary SEQ file to store XMIT file before from the PC (for our example we will use USERID.STRPADTA.XMI)

SEQ File Attributes:

Organization: PS
Record format: FB
Record Length: 80
Block size: 3120
Allocated Blocks: 30

Transfer STRPADTA.XMI from your PC to z/OS transferring as Binary to a temporary SEQ file you created above (USERID.STRPADTA.XMI). You can use FTP or transfer with your z/OS terminal software.

For FTP following options should be specified before PUT command: BINARY, QUOTE SITE RECF=FB, QUOTE SITE LRECL=80

On z/OS at a TSO Prompt:

RECEIVE INDATASET('USERID.STRPADTA.XMI')
DA('TPF.TPFGI.LOADLIB(STRPADTA)')

This will create STRPADTA in your new PDS/E.

$SFUNP

On z/VM $SFUNP.EXEC is on CMSTPF.193 (C Disk). This exec is used to convert created CMSTPFSF file to format that TPF/GI expects.

Options for HLASM

When invoking the HLASM on z/OS option of ADATA needs to be specified. This option will create a SYSADATA (you need to specify a SYSADATA DD card for the HLASM step).

Example JCL (creates a Temporary file to hold SYSADATA)

//ASM       EXEC PGM=ASMA90,
//          PARM='DECK,TERM,ADATA'
//STEPLIB   DD DISP=SHR,DSNAME=SYS1.LINKLIB
//          DD DISP=SHR,DSNAME=TPF.TPFGI.LOADLIB
//SYSLIB    DD DISP=SHR,DSNAME=SYS1.MACLIB
//          DD DISP=SHR,DSNAME=SYS1.AMODGEN
//SYSUT1    DD UNIT=SYSDA,SPACE=(CYL,(5,1))
//SYSUT2    DD UNIT=SYSDA,SPACE=(CYL,(2,1))
//SYSUT3    DD UNIT=SYSDA,SPACE=(CYL,(2,1))
//SYSPUNCH  DD DISP=SHR,DSNAME=NULLFILE
//SYSLIN    DD DISP=OLD,DSNAME=TPF.TPFGI.OBJLIB($HSVTEST)
//SYSTERM   DD SYSOUT=*
//SYSPRINT  DD SYSOUT=*
//SYSIN     DD DISP=SHR,DSN=TPF.TPFGI.SRCELIB($HSVTEST)
//SYSADATA  DD DISP=(,PASS),UNIT=SYSDA,DSN=&&TEMP,
//   SPACE=(CYL,(1,1))

Invoking STRPADTA process after Assemble

For z/OS when assembling using JCL a STEP needs to be added to invoke STRPADTA Module passing in the SYSADATA file from the HLASM step.

Output files for CMSTPFCT and CMSTPFSF need to be setup before running STRPADTA.

Following JCL will Delete CMSTPFCT and CMSTPFSF files if they exist and create new Sequential files:

//ST1       EXEC PGM=IDCAMS
//SYSPRINT  DD   SYSOUT=*
//SYSIN     DD   *
 DELETE TPF.TPFGI.CMSTPFCT.JEFFN NONVSAM PURGE
 DELETE TPF.TPFGI.CMSTPFSF.JEFFN NONVSAM PURGE
//*
//* THIS STEP RUNS CREATE WORK FILES
//*
//ST2       EXEC PGM=IEFBR14
//DD1       DD   DSN=TPF.TPFGI.CMSTPFCT.JEFFN,DISP=(,CATLG),UNIT=SYSDA,
//          SPACE=(CYL,(1,1)),DCB=(RECFM=FB,LRECL=100,BLKSIZE=10000)
//DD2       DD   DSN=TPF.TPFGI.CMSTPFSF.JEFFN,DISP=(,CATLG),UNIT=SYSDA,
//          SPACE=(CYL,(1,1)),DCB=(RECFM=FB,LRECL=4096,BLKSIZE=24516)
//*

Notice the CMSTPFCT is FB 100 and CMSTPFSF in this example is FB 4096. The CMSTPFCT should always be FB 100, the CMSTPFSF can be different values of FB, what ever is the LRECL you use needs to be specified with the –fsf option.

Following JCL will create the CMSTPFCT and CMSTPFSF files from the Temp SYSADATA file created from previous HLASM process:

//STRPADTA EXEC PGM=STRPADTA,
//          PARM='-i DD:SYSADATA -ct DD:CMSTPFCT -sf DD:CMSTPFSF -fsf 4
//             096'
//STEPLIB   DD DISP=SHR,DSNAME=TPF.TPFGI.LOADLIB.STRPADTA
//SYSADATA DD DISP=SHR,DSN=&&TEMP
//CMSTPFCT  DD DISP=SHR,DSNAME=TPF.TPFGI.CMSTPFCT.JEFFN
//CMSTPFSF  DD DISP=SHR,DSNAME=TPF.TPFGI.CMSTPFSF.JEFFN
//SYSTSPRT DD   SYSOUT=*

Note: Continue the Parm field above has parms typed in up to and including column 71 
and then continue the next line starting on column 16.

The –fsf option indicates what size each logical record needs to be. This number must match the LRECL field when creating the File.

Note: -mct is to be added to PARM= field if Source View is using newer method of CMSTPFCT file. If you have questions on which format you should be using please contact TPF Software.

Copying CMSTPFCT and CMSTPFSF files to z/VM for CMSTPF

TPF/GI and CMSTPF run on z/VM system and the CMSTPFCT and CMSTPFSF files built on z/OS need to be copied/moved to z/VM for processing.

When the files get copied and how they get copied depends upon your current setup/process. Here are some methods used today:

CMSTPFCT and CMSTPFSF files are stored on Shared Disk (shared between z/VM and z/OS) and when user request to load a program from TFP/GI the Files are Copied to disk using MOVEFILE process.
As part of the JCL that Assembles and create CT/SF files a message is sent to a VM Server which copies using MOVEFILE or FTP to users z/VM disk.
As part of the JCL that Assembles and creates CT/SF files FTP is done from z/OS to z/VM to copy the files.

There are many different methods to get the files to z/VM, after the files are stored on a z/VM disk specific formats are required for the files:

CMSTPFCT needs to be F 100
CMSTPFSF needs to be V format with a 1 logical record on each line

After you copy the CMSTPFSF file it most likely will not be V Format with 1 record on each line, running $SFUNP sffile will take the current CMSTPFSF file and store in correct format.

Note: In the future TPF/GI will be able to execute the CMSTPFSF in format transferred from z/OS and running $SFUNP will no longer be necessary.

Using STRPADTA on Windows (with Dignus Assembler)

Location of Files

STRPADTA.EXE is available on TPF Software download page.

Contact TPF Software if you do not have this file on your download page and you need it.

Options for Dignus Assembler

Option of –A="fullpathofsysadata" needs to be included so Dignus Assembler will generate the sysadata at the path specified.

After getting a clean Assemble invoke STRPADTA with following options:

Invoking STRPADTA process after Assemble

StrpAdta –i –ct fullctfilepath –sf fullsffilepath

CMSTPFCT and CMSTPFSF files will be created at the paths specified.

These files need to be FTP to z/VM system.

CMSTPFCT FTP parms: Binary, QUOTE SITE FIX 100
CMSTPFSF FTP parms: Binary

The CMSTPFCT should be on z/VM as Fixed 100 but the CMSTPFSF file will need $SFUNP sffile ran on z/VM to reformat the file to have 1 record per line and Variable format.

Note: In the future TPF/GI will be able to handle the CMSTPFSF format without having to run $SFUNP Exec on z/VM.

TPF/IDE Using Dignus Assembler and STRPADTA

If TPF/IDE is being used to communicate with Dignus Assembler ini IDESETUP.INI in the Platform_Assemble section field of CompileLocal=DignusAsm is used to indicate compiles are to be Local on the PC and use section DignusAsm in the LocComp.ini file.

The LocComp.ini, section DignusAsm needs to be setup similar to the following:

'
' Dignus Assemble Procedures
'
[DignusAsm]
' Invoke the assembler, all output files will be store 
  on same location Source is on PC
1=Message iii Starting Local Compile of &filename "c:\dignus\dasm.exe" 
  -q904 
  -xxsd 
  -flisting="&pcdir/&pcfilename.listing" 
  -o"&pcdir/&pcfilename.text" 
  -A="&pcdir/&pcfilename.sysadata" 
  -L"C:/Put18/TPF_Source/&m.mac" 
  -L"C:/Put18/TPF_Source/&m.cpy" 
  -L"C:/Put18/Maclib/T41SYMB0/*.macro" 
  -L"C:/maclibs/T41SYMB0/*.cpy" 
  -L"C:/maclibs/T41SYMB0/*.macro" &pcfullname
’
2=Execute 1 &1 "c:\dignus\" "c:\dignus\dasm.exe" 
  -xxsd 
  -flisting="&pcdir/&pcfilename.listing" 
  -o"&pcdir/&pcfilename.text" 
  -A="&pcdir/&pcfilename.sysadata" 
  -L"C:/Put18/TPF_Source/&m.mac" 
  -L"C:/Put18/TPF_Source/&m.cpy" 
  -L"C:/Put18/Maclib/T41SYMB0/*.macro" 
  -L"C:/maclibs/T41SYMB0/*.cpy" 
  -L"C:/maclibs/T41SYMB0/*.macro" &pcfullname
’
' Read the SysAdata File and build ErrorOutputFile, Control File, 
  and SF Map File
’
3=Message iii Local Compile for &filename completed, processing 
  output files "&pcdir" "C:\StrpAdta\StripAdata.exe" 
  &pcdir\&pcfilename.sysadata &filename &fileid 
  &pcdir\&pcfilename.$$ERROR$ &pcdir\&pcfilename.cmstpfct 
  &pcdir\&pcfilename.cmstpfsf  
’
4=Execute 1 &1 "&pcdir" "C:\StrpAdta\StrpAdta.exe" 
  -i "&pcdir\&pcfilename.sysadata" 
  -s "&filename" 
  -id &fileid 
  -er "&pcdir\&pcfilename.$$ERROR$" 
  -ct "&pcdir\&pcfilename.cmstpfct" 
  -sf "&pcdir\&pcfilename.cmstpfsf"  
'
’ If error > 7 from Assemble go to step 15
’
5=IF &1 > 7 THEN 15
'
' Got a Clean Assemble, Log Into FTP for VM System
6=Message ... Storing &pcfilename.TEXT on VM System
7=Ftp Login &ftpsystem &ftpuserid 
' Change Directory to Store Files too
8=Ftp Chdir &ftpdir
' Store Object (Text)  Binary File with Fixed format 80 length records
9=Ftp Put B 80 &pcdir\&pcfilename.TEXT &pcfilename.TEXT
' Store CMSTPFCT file, Binary File with Fixed format 100 length records
10=Message ... Storing &pcfilename.CMSTPFCT on VM System
11=Ftp Put B 100 &pcdir\&pcfilename.CMSTPFCT &pcfilename.CMSTPFCT
' Store SF File as Binary and Variable Length
12=Message ... Storing &pcfilename.CMSTPFSF to VM
13=Ftp Put B V &pcdir\&pcfilename.CMSTPFSF &pcfilename.CMSTPFSF
' Indicate FTP to Close Connection
14=FTP Exit
15=Message iii End Compile for &filename, RC=&1
' Process the Error File. If Any errors found (besides warnings) this step will 
  stop the Script
16=ProcessErrorFile "&filename" "&pcdir/&pcfilename.$$ERROR$"

Note: $SFUNP EXEC has to be ran against the CMSTPFSF file on VM before using (during Exec that Loads the Assemble Program is best time to do this). In the future TPF/GI will be handle format of CMSTPFSF file without $SFUNP being executed.