Once your client and server are communicating, you have verified that lcolist is running on your server, and the required objects have been successfully deployed to the Server, you are ready to test execution.
- When you are first experimenting with using a Linux Server, we recommend using the sample L4WEX01 function to connect to the server to begin with. (Please refer to Testing with the Verification and Sample Applications for further information.) Later you can write your own connection function, and perhaps automatically call it via the INIT= argument. (See the INIT= and TERM= Parameters in the for more information.)
- When you start executing applications, you will probably use the LANSA owner as your login for testing. However, you will eventually need to allow test or production users access to your application. Users must be able to read, execute, create, or update certain files and directories for successful application execution. Please carefully read Allow Users Access to LANSA in the guide.
- You may need to setup some X_RUN arguments as standard. You may use the $X_RUN environment variable, or an x_lansa.pro profile to set these up. Please refer to Set up default X_RUN parameters in the for more details.
- Client sessions may need to set specific X_RUN arguments for connection to a Linux server. Refer to 2.1 Override X_RUN arguments inherited from the Client for details.
- You will need to execute X_RUN from the command line to check your license status, and possibly to execute batch jobs. Refer to 2.2 Start X_RUN from the command line for details.
- Full details of all the X_RUN arguments can be found in The X_RUN Parameters in the .
You can refer to Troubleshooting for further assistance.