Okay, we use Extra Attachmate as our emulator to access the mainframe. Extra has a function that allows you to transfer files from the mainframe to your local pc, we use the ind$file function to do so.
What I am trying to figure out is how to do the same thing, but initiate it from the mainframe side. Now I can FTP a file easy enough using REXX or JCL, but I need to know the IP address of the workstation first. And getting that dynamically is proving to be a pain.
So my question…has anyone successfully used rexx or jcl to initiate the ind$file from the mainframe side and transfer to a PC? Or does anyone know of a way to get a station IP address using REXX?
My eyes are actually starting to bleed a little from the number of websites I have looked thru, and while some hint at doing what I need…I just cant find something that works. Of course I am really just a intermediate user of rexx/jcl so perhaps I just dont understand something.
I was arguing with a DBA yesterday about running SQL batch jobs. On the mainframe when we were using IDMS I used to run jobs in local mode, directly reading the packs without using the DBMS. The DBMS kept no pointers, did no logging and provided no rollback facility but ran many times faster. Surely with this more modern system I can do something similar. Apparently not.
I miss the mainframe.
I remember too that I used to have a terminal on my desk and when the LAN went down I just moved my chair and started cutting code on the terminal.
Sometimes I think the relational database is just the triumph of mediocrity. It is socialism for DBs - terrific in theory but death in practice. Network databases just make more sense to me.
For help on these things, you can’t do better than the IBM-MAIN list server. You can get subscription information by sending an email message to listserv@bama.ua.edu with the message: GET IBM-MAIN INFO
You should be able to define a session with a particular device name that will not change regardless of whether that workstation uses a static IP or DHCP.
You can set your job up on the MF to output to that device, and assuming the PC is up and the session established should be ok.
It’s similar to setting up a printer session using emulation. The host knows nothing of the PC’s IP address, but does know that output.xxx is sent to LU00025 etc…