In this section:
You may call a ReportCaster API subroutine from a:
A procedure must reside in a path defined to the WebFOCUS Reporting Server. On Windows and UNIX, it must be located in EDAPATH. On OS/390, it must be in a partitioned data set (PDS) allocated to ddname EDARPC.
You can call an API subroutine using a -SET Dialogue Manager command. For more information about Dialogue Manager, see the Developing Reporting Applications manual.
A ReportCaster API subroutine passes a required set of arguments in a specified order and supplies a return code to the calling procedure. You can change the Dialogue Manager variable names (amper variables), or replace them with coded values. The following variable names used are samples.
Note: This is the general syntax for all subroutines. For more information about the syntax for each subroutine, see the specific sections that describe the DSTBULK, DSTMEM, and DSTRUN subroutines.
-SET &var_name=API_subrtn_name(srv_userid,srv_userid_length, - 'srv_userpass',srv_userpass_length, - 'hostname_port',hostname_port_length, - 'input7', - 'input8', . . . - 'httpuser/pswd',httpuser/pswd_length, [- 'tcpiplevel',] - 'I4');
Is the variable that will contain the return code.
Is the API subroutine, which can be DSTBULK, DSTMEM, or DSTRUN.
Is a valid Execution ID. It must match the user ID stored in the WebFOCUS repository with the job information.
Is the length of the Execution ID.
Is a valid password for the Execution ID. It must match the password of the user ID stored in the WebFOCUS repository with the job information.
Is the length of the password for the Execution ID.
Is the host name (or IP address) and port number of the web server on which the WebFOCUS Client is installed. The maximum character length is 30.
If the port number is 80 (the default), you may omit the colon and port number. For example,
If the port number is not 80, use a colon as a delimiter and then specify the port number. The maximum character length is 10. For example,
Is the length of the host name and port number. This is only the length of the host name if the port number is omitted.
Are the input arguments (the values required by the subroutine). These arguments are different for each subroutine.
Is a valid user ID and password for the web server, separated by the forward slash character ( / ). A user ID and password are required if the web server is running with security on.
Is the length of the web server user ID and password, including the forward slash character ( / ).
Required only if the WebFOCUS Reporting Server runs on OS/390. This argument is the method the ReportCaster API uses for securing sockets from TCP/IP, based on a specific SAS/C library. Valid values are:
Is the format of the return code. For more information, see ReportCaster API Subroutine Messages.
When you code a ReportCaster API subroutine:
If you do not supply all arguments, the subroutine terminates, and a TSCOM3 message may be generated.
The only exception is the argument tcpiplevel, which is required only if the WebFOCUS Reporting Server runs on OS/390. If your server does not run on OS/390, you must omit this argument.
The ReportCaster API provides a pair of identification arguments as input to certain subroutines.
You can identify a job to the ReportCaster API with either the jobdesc or the scheduleid argument.
Note: The ReportCaster Administrator can determine a schedule ID for a job by running the report from the ReportCaster Console. Both administrators and users can determine a schedule ID by using the Log File icon on gray toolbar of the ReportCaster Interface.
You can call a procedure from an HTML form. The following sample HTML code calls a procedure, which in turn calls a ReportCaster API subroutine. For more details on coding syntax, see the Developing Reporting Applications manual, and the HTML files residing on /ibi_html/broker/.
<FORM ACTION="/cgi-bin/ibi_cgi/ibiweb.exe" METHOD="get"> <INPUT NAME="IBIF_ex" VALUE="procedure_name" TYPE="hidden">
Is the name of the procedure to run. It contains the call to the ReportCaster API subroutine. A procedure must reside in a path defined to the WebFOCUS Reporting Server. On Windows and UNIX, it must be located in EDAPATH. On OS/390, it must be in a partitioned data set (PDS) allocated to ddname EDARPC. Do not specify the file name extension in the VALUE= field.