|
View previous topic :: View next topic
|
| Author |
Message |
Balaji Canabady
New User
Joined: 07 Dec 2011
Posts: 19
Location: India
|
|
|
|
When submitting a job using FTP, how do one specify in which region to run that job?
I have the following script SCRIPT1.SCR
| Quote: |
USER
mainframeuserid
mainframepassword
QUOTE SITE FILETYPE=JES
GET 'USERID.ABC.XYZ(MYJOB)'
QUIT
|
(Jobname is my userid +1 char )
However when I submit the job using FTP, the job runs in the production region instead of the development region and fails ?
| Code: |
| FTP -n -s:script1.scr XX.XX.XXX.XX |
where XX.XX.XXX.XX is my host ip.
Can anyone suggest how to submit the job in development region/ testing region ? |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| Can anyone suggest how to submit the job in development region/ testing region ? |
we do not belong to You organization, we do knot know your <setup>, we do not know Your standards ... ... ...
ask Your support
but since today is wednesday ==> psychic day
... You have two/three alternatives
1) FTPING directly to the IP Of the development region
2) change Your job to use a route control statement
3) ask Your support |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
Since you are NOT using standard terminology, it is difficult to determine just what your issue is. When you say "production region" and "development region" -- are you talking about different machines? different LPARs on one machine? different CICS regions (which is how the term normally is used -- but makes no sense in conjunction with an FTP task)?
Assuming you are talking about using a development LPAR instead of a production LPAR, you need to talk to your site support group. Each LPAR has its own unique IP address, so if you change the IP address you change where the FTP connects to. And only someone working at your site will know what the IP addresses are for the various LPARs involved. |
|
| Back to top |
|
|
Balaji Canabady
New User
Joined: 07 Dec 2011
Posts: 19
Location: India
|
|
|
|
Hi Enrico and Robert,
I am sorry for the parlance used in describing my issue.
As you have rightly guessed, I was actually meaning the development LPAR and production LPAR.
Thanks for the different options suggested. I will try them and update the post... |
|
| Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011
Posts: 556
Location: USA
|
|
|
|
Ummm, I think the GET command runs JCL that is already on the mainframe That means you'd have to change it it up there to change it at all.
On the other hand, the PUT command takes a JCL deck in a text file and submits it to the mainframe. I use that option to change my JCL on the fly.
The advantage of "GET" is that the FTP command WAITS FOR THE JOB TO FINISH and then retrieves the output. The "PUT" command does NOT WAIT.
To get the output from the PUT command, you have to turn around and do a DIR command using the jobid until the job status says "OUTPUT". Then you have to go to that job and GET the output.
You could also FTP the changed job up to a dataset, then do the GET command from that dataset. |
|
| Back to top |
|
|
|
|
