This memo announces the availability of Version 1 of XPORT, a BLISS Transportability Support Package, for VAX/VMS, RSX-11M, IAS, RSTS/E and RT-11. The new edition of the XPORT Programmer's Guide (corresponding to XPORT Version 1) is also available and can be ordered from the SDC. Its order number is AA-J201A-TK. For your convenience, until you obtain the new manual, use the previous (baselevel 7) edition and the attached XPORT Version 1 Release Notes. You should use the following command sequence to install XPORT on your VAX/VMS system (Release 2.0 or later): Log into the SYSTEM account. $ COPY/LOG METOO::SYS$PUBLIC:XPONETGEN.COM * . . . $ @XPONETGEN . . . This procedure will place the following files into the directories indicated: SYS$LIBRARY: XPORT.REQ - XPORT REQUIRE file XPORT.L16 - LIBRARY version of XPORT.REQ for BLISS-16 XPORT.L32 - LIBRARY version of XPORT.REQ for BLISS-32 XPORT.OLB - Default XPORT object module library (copy of XPOVMS.OLB) XPOVMS.OLB - VAX/VMS XPORT object module library XPO11M.OLB - RSX-11M XPORT object module library XPO11N.OLB - RSX-11M XPORT non-EIS object module library XPOIAS.OLB - IAS XPORT object module library (copy of XPO11M.OLB) XPORST.OLB - RSTS/E XPORT object module library XPORTE.OBS - RT-11 XPORT object modules (concatenated) XPORTN.OBS - RT-11 XPORT non-EIS object modules (concatenated) SYS$SYSTEM: XDUMP.EXE - XPORT Structure Dump Generator SYS$MESSAGE: XPORTMSG.EXE - XPORT Messages Current directory: XPONETGEN.COM - XPORT installation command procedure XTEST.BLI - XPORT test program source file, XTEST.LIS - compiler listing file, XTEST.OBJ - object file, XTEST.EXE - and executable image. Note to BLISS-16 Sites The XPORT installation procedure does not install XPORT object files on a PDP-11 system. Instead, the XPORT installer is responsible for creating an appropriate XPORT object module library on each desired PDP-11 system. Chapter 7 of the BLISS-16 User's Guide describes procedures for transferring object files and building object libraries on PDP-11 systems. Please feel free to contact me if you have any difficulties with XPORT installation or any questions about XPORT coding or debugging. +-------------+ +-------------+ | | | | | | | | | | | | | | | | |d|i|g|i|t|a|l| I N T E R O F F I C E M E M O R A N D U M |d|i|g|i|t|a|l| I N T E R O F F I C E M E M O R A N D U M | | | | | | | | | | | | | | | | +-------------+ +-------------+ To: XPORT Users Date: 11 June 1981 From: Edward Freedman Dept: Methods and Tools Ext: DTN 264-8090 Loc/Mailstop: ZK1-3/B21 DECnet: METOO::FREEDMAN Subject: XPORT Version 1 Release Notes 1.0 Introduction There have been a limited number of user-visible changes to XPORT between Baselevel 7 (Field Test) and Version 1. The XPORT Programmer's Guide has been being updated to reflect these changes. The new edition of the XPORT Programmer's Guide (corresponding to XPORT Version 1) can be ordered from the SDC. Its order number is AA-J201A-TK. For your convenience, until you obtain the new manual, use the previous (Baselevel 7) edition and the summary of XPORT Version 1 changes which appears below. 2.0 Recompilation of Existing Programs XPORT Version 1 includes a number of changes to XPORT macro and symbol definitions (e.g., descriptor class codes). It is therefore necessary to recompile all of your BLISS source programs which use XPORT ___ facilities before attempting to link a program with the XPORT Version 1 run-time routines (e.g., XPORT.OLB). 3.0 Differences between XPORT Baselevel 7 and XPORT Version 1 This section describes the differences between the XPORT syntax and semantics described in the Baselevel 7 edition of the XPORT Programmer's Guide (dated June 24, 1980) and XPORT Version 1 syntax and semantics. The XPORT Version 1 macro definitions (in XPORT.REQ) provide interim support for XPORT syntax which has recently changed -- existing, valid BLISS modules can be recompiled to produce valid Version 1 object files; obsolete syntax will, however, result in %INFORM messages in the compiler listing files. XPORT Version 1 Release Notes Page marks in sequenced files A "page mark" in a sequenced file (e.g., created by an SOS editor) is now defined to be a single-character record containing a form-feed character and having a sequence number of zero (0), regardless of how the page mark is actually represented on the host system. $XPO_GET now returns these page marks to the caller as individual records rather than simply counting and ignoring them; $XPO_GET will continue to recognize page marks in input files and will maintain the IOB$H_PAGE_NUMB field in the IOB. $XPO_PUT will no longer automatically generate page marks in an output file. As a result, the PAGE_NUMBER= parameter has been eliminated from the $XPO_PUT and related macros. $XPO_GET_MEM use of descriptors The $XPO_GET_MEM function no longer supports the use of an "incomplete descriptor" as both an input and output parameter. This function now defines the DESCRIPTOR= parameter for output purposes only; an element size parameter (CHARACTERS=, UNITS=, FULLWORDS=) must now be used to specify the size of the requested dynamic memory element. New names for $ASCII, $FORMAT and $CONCAT The names of the $ASCII, $FORMAT and $CONCAT macros have been changed to $STR_ASCII, $STR_FORMAT and $STR_CONCAT to avoid possible conflicts in the future with VAX/VMS macro names. String Package routine names The names of the routines called by the XPORT String Package macros (e.g., $STR_COPY) have been changed from "STR$routine" to "XST$routine" to avoid routine naming conflicts with the string functions in the VAX/VMS Run-time Library. This change should only affect users who refer to these routines during program debugging since these routine names should not appear in BLISS source programs. The names of the XPORT String Package failure action routines (e.g., STR$FAILURE) have not been changed. ___ $DESCRIPTOR name conflict The XPORT definition of the $DESCRIPTOR data structure macro has been changed so that it can coexist with the macro of the same name in SYS$LIBRARY:STARLET.REQ (or .L32) on a VAX/VMS system.