Retrieve information about the IBM i Access for Windows code installed on the PC.Convert strings and numeric data between host and PC formats.Send and receive data using data queues.Call an IBM i API to retrieve a list of data queues in a library.Call an IBM i API to retrieve a list of user libraries on the server.Retrieve information about an IBM i, such as the: IP address, host version and release levels, password expiration date, number of active connections, etc.
Retrieve the list of IBM i systems which have previously been connected.'.or you could execute additional code when an error is thrown.This Visual Basic Script sample uses the IBM i Access for Windows automation objects to perform the following: Response.Write("Error Number: " & err.Number) Response.Write("Error Source: " & err.Source) Response.Write("Error Description: " & err.Description) '.you could display the error info directly in the page. "console.log('Error source: " & err.Source & "') " & _ "console.log('Error number: " & err.Number & "') " & _ "console.log('Description: " & err.Description & "') " & _ 'You could write the error details to the console. If err.Number 0 Then : showError() : End If
Set oConn = Server.CreateObject("ADODB.Connection")ĬonnStr = "Provider=SQLOLEDB Server=XX UID=XX PWD=XX Databse=XX"
I'm exceptionally new to VBScript, so this may not be considered best practice or there may be a reason it shouldn't be done this that way I'm not yet aware of, but this is the solution I came up with to trim down the amount of error logging code in my main code block.