| Sending iSeries 400 Physical Files to AB/Remote and Java Users |
| Product: | BusinessLink/WEB |  |
| Modified Date: |
|
The utility for sending iSeries 400 database files to BusinessLink/REMOTE and Java clients is the iSeries 400 ABL command ABLAPI.
The ABLAPI command has full iSeries 400 prompt support and the ability to send two files per
execution: text files and attachment files. Text files can be thought of as header files that can be readily viewed when received at the remote by using the 'View' button icon. They are limited in size to 9999 records with a maximum record length of 80 bytes. Attachments, on the other hand, do not have a maximum record length or total record limitation. All transfers of iSeries 400 database files should be specified as attachments when using the ABLAPI. The minimum information required for a successful file transfer is the device code the registration is attached to ('R' for BusinessLink/REMOTE or 'J' for Java), registration number you wish to send the file to, and iSeries 400 database file location. In the following example, the physical file ABLDATA, member ABLDATA1, library ABLWORK will be sent to registration number 5 on coprocessor device 'R'. ABLAPI DVC( R ) REGN( 5 ) ATTFILE( ABLDATA ) ATTLIB( ABLWORK ) ATTMBR( ABLDATA1 ) The only difference in sending the exact same file to a Java user would be to change the device (DVC) and registration number (REGN) parameters. Note that registrations don't always coincide from device to device. A user may have a registration number of 10 for BusinessLink/REMOTE and a registration number of 22 for the Java client support. Working with remote users and Java users from the ABL menu will list all active registrations. Once the command has been issued, file transfer progress can be readily viewed on the 'Work With Sent / Received Files' option on the ABL menu. When a file has reached a status of 'Queued', it is ready for pickup from the remote registration. When a status of 'Text' appears, an error has occurred in the API. Displaying the information particular to the system reference number with a status of 'Text' will give detail as to what went wrong with the API. Refer to manual for error code descriptions. ** End of Technical Support Bulletin ** |
|
|
 |