HP 3000 Manuals

Programming Language Considerations [ Using NS3000/XL Network Services ] MPE/iX 5.0 Documentation


Using NS3000/XL Network Services

Programming Language Considerations 

The DSCOPY and DSCOPYMSG intrinsics are SPL procedures that may be called
by programs written in other languages.  Following are appropriate data
types and calling sequences for the different languages available.
(Other data types are sometimes possible.)

SPL 

In SPL,  opt, fnum , and r may be integers;  spec may be a logical array;
and  result may be a logical array.  The calling sequences are:

     DSCOPY (OPT, SPEC, RESULT);
     DSCOPYMSG (RESULT, FNUM, R);

COBOL 

In COBOL,  opt, fnum , and r may be numeric data items;  spec may be an
alphanumeric data item; and  result may be a numeric array.  The calling
sequences are:

     CALL INTRINSIC "DSCOPY" USING OPT, SPEC, RESULT.
     CALL INTRINSIC "DSCOPYMSG" USING RESULT, FNUM, R.

FORTRAN 

In FORTRAN,  opt, fnum , and r may be one-word integers;  spec may be a
character array; and  result may be an array of one-word integers.  The
calling sequences are:

     CALL DSCOPY (OPT, SPEC, RESULT)
     CALL DSCOPYMSG (RESULT, FNUM, R)

BASIC 

In BASIC, the intrinsics have a different name.  In addition, only
certain kinds of parameter names are permitted, as illustrated in the
following calling sequences:

     CALL BDSCOPY (O, S$, R)
     CALL BDSCOPYMSG (R, F, R0)

Here O, F, and R0 may be integers; S$ is a string; and R may be an array
of integers.

Pascal 

In Pascal,  opt, fnum , and r may be one-word (subrange) integers;  spec 
may be a packed array of characters or a string (a legal type in HP
Standard Pascal); and  result may be an array of one-word integers.  The
calling sequences are:

     DSCOPY (OPT, SPEC, RESULT);
     DSCOPYMSG (RESULT, FNUM, R);


NOTE In Pascal, if the spec parameter is represented as a character array or string, the numeric zero which terminates it should be represented by the ASCII null character. If spec is a mixed-type structure, the zero can be a numeric (one-byte) zero.


MPE/iX 5.0 Documentation