# Entire Connection to UNIX - workfiles **URL:** \ **Category:** Forum\ **Tags:** Adabas-Natural, Natural, Natural-Other-Addons, Natural-Related-Products, Terminal-Emulation-and-Screen-Scraping\ **Created:** [July 7, 2005, 3:02pm UTC](https://techcommunity.softwareag.com/t/entire-connection-to-unix-workfiles/60063 "2005-07-07T15:02:23Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Priscilla\_Fuller](https://avatars.discourse-cdn.com/v4/letter/p/b5ac83/32.png) [@Priscilla\_Fuller](https://techcommunity.softwareag.com/u/Priscilla_Fuller)\ **Post date:** [July 7, 2005, 3:02pm UTC](https://techcommunity.softwareag.com/t/entire-connection-to-unix-workfiles/60063/1 "2005-07-07T15:02:23Z")
I am not familiar with Entire Connection doing terminal emulation to a UNIX box - only used it to a mainframe. I believe all I have to do is set up workfiles in the Natparm and have PC=ON. I have set up the workfiles (1-5) as Entire Connection - the name is blank. Using SYSFILE it is not showing me that they are PC files. If I do %+ I get a NAT0082 - Invalid Command or Object %+ does not exist in library. I want to use SYSOBJH and was expecting it to pop up a box asking me for the PC file. If I put the name of the PC file it tells me the file doesn’t exist. Is there something else I have to do? NAT611 PL 12, Entire Connection 4.4.1.2 ---
**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\ **Post date:** [July 7, 2005, 3:34pm UTC](https://techcommunity.softwareag.com/t/entire-connection-to-unix-workfiles/60063/2 "2005-07-07T15:34:02Z")
Unfortunately this won’t work because the “host” counterpart (NTC) to the emulation piece (PCC) only exists for mainframe NATURAL ! You will need to SYSOBJH to a local workfile on your UNIX box, then FTP/SCP/… it. ---
**Author:** ![Priscilla\_Fuller](https://avatars.discourse-cdn.com/v4/letter/p/b5ac83/32.png) [@Priscilla\_Fuller](https://techcommunity.softwareag.com/u/Priscilla_Fuller)\ **Post date:** [July 7, 2005, 4:39pm UTC](https://techcommunity.softwareag.com/t/entire-connection-to-unix-workfiles/60063/3 "2005-07-07T16:39:53Z")
Wolfgang Thanks for your prompt reply. What puzzles me is that in the Natural documentation for Unix, there is a whole section about Natural Connection. Seems a bit strange if the product doesn’t exist for Unix! 🙂 I confess I hadn’t spotted it was about Natural Connection and not Entire Connection. What does defining a work file as an Entire Connection file in the Natparms do? Sigh - I guess we’ll just have to carry on doing FTPs. ---
**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\ **Post date:** [July 7, 2005, 4:54pm UTC](https://techcommunity.softwareag.com/t/entire-connection-to-unix-workfiles/60063/4 "2005-07-07T16:54:31Z")
Seems I’m wrong here, you are right, according to the documentation it should work. I apologize for that :oops: I’ll need to try this myself and get back to you. I assume you followed the documentation, defined the workfile as type “TRANSFER” and issued a %+ / SET CONTROL ‘+’ ? ---
**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\ **Post date:** [April 2, 2021, 2:40pm UTC](https://techcommunity.softwareag.com/t/entire-connection-to-unix-workfiles/60063/5 "2021-04-02T14:40:13Z")