IBM i C# and VB.Net PASE, bash, SSH and XMLSERVICE Data Access Service Wrapper for .Net and .Net Core. Provide IBM i SSH connectivity to your IBM i apps.

This .Net Standard 2.0 class library can be used to interface with an IBM i system over SSH. The library can interface to the IBM i database via SQL, program calls, CL commands, service programs and data queues via the PASE based xmlservice-cli command line program (part of open source package itoolkit-utilities). Regular qsh/bash commands can also be run to interface with utilities such as the IBM i db2util utility or programs written in languages such as Java, Python, PHP, Node.js and more.

Query and program call return data is returned in .Net DataTable format, JSON, CSV or you can process the raw XML responses yourself.

The IBMiXmlServiceStdSsh class library can be installed to your .Net project from Nuget. https://www.nuget.org/packages/IbmiXmlserviceStdSsh

Commercial .Net development and product support can be purchased through MobiGoGo LLC (https://www.mobigogo.net)

https://www.nuget.org/packages/IbmiXmlserviceStdSsh

● XMLSERVICE methods requires xmlservice-cli package installed on the target system via yum packages (/QOpenSys/pkgs.bin/xmlservice-cli). Installs as part of part of itoolkit-utilities.

● Class library Uses SSH.Net for SSH connectivity so IBM i SSH server must be running. (V7R2 and above)

STRTCPSVR *SSHD

● Set up user's SSH shell default to be bash. (See below)

● The XMLSERVICE service program library QXMLSERV must also exist on the system, This library is installed as part of the IBM i operating system

XMLSERVICE is now typically packaged on the IBMi in library: QXMLSERV as part of the operating system, but if you want to play with the code, here's the current Github location as of 1/23/2019

https://github.com/IBM/xmlservice

● Make sure the IBM i user you will be using for SSH access has /QOpenSys/pkgs/bin in the user search path.

export PATH=/QOpenSys/pkgs/bin:$PATH

Note: For appropriate security you should configure your SSH users for appropriate security limitations in the IFS and for libraries and commands that may be accessed over an SSH connection to IBM i.

Nowadays, the best way to do this is to using QSYS2.SET_PASE_SHELL_INFO() SQL procedure from your favorite SQL tool or STRSQL

-- set current user's shell
CALL QSYS2.SET_PASE_SHELL_INFO('*CURRENT', '/QOpenSys/pkgs/bin/bash');

-- set a specific user's shell
-- (requires *SECADM special auth plus *USE and *OBJMGT to the user profile)
CALL QSYS2.SET_PASE_SHELL_INFO('THATUSER', '/QOpenSys/pkgs/bin/bash');

-- set the default shell which is returned for users that do not have
-- (requires *SECADM special auth plus *USE and *OBJMGT to QSYS)
CALL QSYS2.SET_PASE_SHELL_INFO('*DEFAULT', '/QOpenSys/pkgs/bin/bash');

https://stackoverflow.com/questions/23913957/set-default-pase-ibm-i-shell-for-individual-user