[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::decbasic

Title:	DEC BASIC Conference
Notice:	SSB Kit Now available - Note 2.29
Moderator:	TLE::HAYNES

Created:	Wed Sep 15 1993
Last Modified:	Thu Jun 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	210
Total number of notes:	976

208.0. "%BASIC-E-PAREXPFOR, 14 parameters expected for SYS$CREPRC" by CSC32::D_SANFORD () Thu May 08 1997 17:19

    DEC BASIC V1.2, OpenVMS Alpha V7.1

    OpenVMS V7.1 introduced a 14th argument, [node], to the $CREPRC 
    system service.  If you rebuild BASIC$STARLET.TLB the module
    STARLET will include the 14th argument causing compilations to 
    fail for existing applications, for example:

     stat = sys$creprc ( pidadr% by ref, "image", "input", "output", &
............^
%BASIC-E-PAREXPFOR, 14 parameters expected for SYS$CREPRC
at line number 5 in file USER1:[D_SANFORD]CREPRC.BAS;7

    Currently the customer is modifying the module STARLET to only 
    include 13 arguments, is there a better way to deal with this?  
    What he does not want is someone to rebuild this in the future and
    have it fail.

    Regards, Drew Sanford
    Customer Support Center
    C970507-3059


100  DECLARE LONG STAT
     DECLARE BASIC$QUADWORD foo
     %INCLUDE "starlet" %FROM %LIBRARY "sys$library:basic$starlet.tlb"
   
     stat = sys$creprc ( pidadr% by ref, "image", "input", "output", &
		"error", foo by ref, quota% by ref, "prcnam", 3, &
		0, 0, 0, itmlst% by ref)
     END

T.R Title User Personal
Name Date Lines

208.1 bug in starlet definition GIDDAY::GILLINGS a crucible of informative mistakes Fri May 09 1997 00:18 13

T.R	Title	User	Personal Name	Date	Lines
208.1	bug in starlet definition	GIDDAY::GILLINGS	a crucible of informative mistakes	`Fri May 09 1997 00:18`	13
	Drew, > is there a better way to deal with this? That depends on the objectives. If the customers code is targeted at V7.1 and up, then just add the 14th (null) argument. If it must coexist with earlier code, then I'd suggest not using the STARLET definition, just provide your own. On the other hand, the 14th argument must be optional, so the STARLET definition should allow it to be missed. You may need to QAR this against BASIC. John Gillings, Sydney CSC

  Drew,

>   is there a better way to deal with this?

    That depends on the objectives. If the customers code is targeted at V7.1
  and up, then just add the 14th (null) argument. If it must coexist with
  earlier code, then I'd suggest not using the STARLET definition, just 
  provide your own.

    On the other hand, the 14th argument must be optional, so the STARLET
  definition should allow it to be missed. You may need to QAR this against
  BASIC.
						John Gillings, Sydney CSC