To Execute this Example
Ensure that JSM is working and started and in particular that the DC@W29 entry for this example has been added.
Example 235 requires this row in table DC@W29 on the remote host system:
To use the SVHEAD keyword, a configuration entry needs to be added to the HTTPService.Properties file, typically located in your iSeries IFS system in the /jsm/instance/properties directory. Edit this file and add two lines:
# for SET_235
sv.head.SET235S=EMPNO
Ensure that LANSA User Agent is installed correctly on your PC.
Put the contents of zip file SET_JSM_UserAgent.zip into the LANSA User Agent directory on your PC:
If everything is configured correctly, a file called SET_235_Response.csv should be created in the same directory. This file should contain the report that was produced on the server.
What to do if a JSM based example does not work
If you are running the LANSA User Agent using the HTTPClient service:
| LANSA User Agent - Batch File Conversion and Upload | The Things that Make Up this Example |
Ensure that JSM is working and started and in particular that the DC@W29 entry for this example has been added.
Example 235 requires this row in table DC@W29 on the remote host system:
| Column Name | Value | Comments |
| W29SRV – Service Name | SET_235_CSV | |
| W29LHO – Web server ip address | eg: 123.123.123.123:80 | Enter iSeries IP address in Host:Port format |
| W29MOD – Process Name | SET_235 | |
| W29FMT – Function Name | SET235S | |
| W29P#I – Partition | <ppp> | Specify the partition in which the SET collection was installed (<ppp> is typically DEM) |
| W29PLN – Language | Blank or< LLL> | If the partition is monolingual set this column to blanks. Otherwise set it to the language your are using (<LLL> is typically ENG, FRA, JPN). |
| W29PGM – Program | Set to blanks | Do not specify this value |
To use the SVHEAD keyword, a configuration entry needs to be added to the HTTPService.Properties file, typically located in your iSeries IFS system in the /jsm/instance/properties directory. Edit this file and add two lines:
# for SET_235
sv.head.SET235S=EMPNO
Ensure that LANSA User Agent is installed correctly on your PC.
Put the contents of zip file SET_JSM_UserAgent.zip into the LANSA User Agent directory on your PC:
- If you imported the windows SET import material, SET_JSM_UserAgent.zip can be found in the partition execute directory.
- If you imported the iSeries SET import material, SET_JSM_UserAgent.zip can be found with the web images, or in the SETIMGCUR save file.
- the host – this is the ip address of your web server
- the host uri for file sources (if “/cgi-bin/jsmdirect” is not the location of jsm direct in your iSeries web server configuration. )
If everything is configured correctly, a file called SET_235_Response.csv should be created in the same directory. This file should contain the report that was produced on the server.
What to do if a JSM based example does not work
If you are running the LANSA User Agent using the HTTPClient service:
- Check the response tab sheet on the LANSA User Agent
- Locate the HTTP Server instance job used by your job and read the messages in its job log.
- Trace files (see section on obtaining trace files)