Page 1 of 1

How to allow MKS Implementer to work with GoAnywhere?

Posted: Fri Jan 20, 2017 6:40 am
by robberendt
We use MKS Implementer to promote changes from our development lpar to other lpars. They use FTP to transmit. They are assuming the NAMEFMT 0 environment. How do I set them up to work?

Re: How to allow MKS Implementer to work with GoAnywhere?

Posted: Fri Jan 20, 2017 9:25 am
by Support_Rick
Rob,

How are you wanting to integrate with MKS? GAMFT can connect and transfer files between servers easily. It can insert records into a DB2 table as well as the IFS.

Are you wanting GAMFT to do the transfers of updated files/tables? Are you wanting to just push data? What are you looking at doing?

Re: How to allow MKS Implementer to work with GoAnywhere?

Posted: Fri Jan 20, 2017 11:45 am
by robberendt
Currently MKS (now known as PTC) uses roughly the following FTP script:
USERID PASSWORD
BINARY
CD /QSYS.LIB
QUOTE SITE NAMEFMT 0
QUOTE RCMD CRTLIB RMTLIB
QUOTE RCMD CRTSAVF RMTLIB/RMTFILE
QUOTE RCMD CLRSAVF RMTLIB/RMTFILE
PUT LOCLIB/LOCFILE RMTLIB/RMTFILE
QUIT

What do we need to set up in their account to allow them to execute this script?

Re: How to allow MKS Implementer to work with GoAnywhere?

Posted: Fri Jan 20, 2017 12:40 pm
by Support_Rick
Rob,

I'm not an MKS or PTC user, so what would be needed from their product, I do not know.

You can run a GAMFT workflow from a remote server (iSeries, Linux/Unix, Windows, etc) using our GACMD.

You can setup a GAMFT workflow to accomplish the attached list of commands.

So, if you can execute commands from MKS or PTC .. then, you should be able to call a workflow and make that happen.

Re: How to allow MKS Implementer to work with GoAnywhere?

Posted: Fri Jan 20, 2017 1:28 pm
by robberendt
I do not believe that PTC would be willing to require all their customers using PTC to install GAMFT workflow on all their machines.
Therefore I need to figure out a way for someone coming from some other client to ftp into this machine and execute that script.