View previous topic :: View next topic
|
Author |
Message |
aditya_gupt
New User
Joined: 14 Jan 2006 Posts: 5 Location: Mumbai
|
|
|
|
Hi All,
We are using XCOMJOB program in our application.
Need information on what exactly different modes for XCOMJOB means (EXECUTE, SCHEDULE, INQUIRE). Jobs use XCOMJOB (Pgm) or XCOMINQ (Proc) or XCOMEXEC (Proc) to perforom XCOM.
XCOMINQ and XCOMEXEC procs are internally calling XCOMJOB only, XCOMINQ calling in SCHEDULE & INQUIRE mode while XCOMEXEC calls in EXECUTE mode.
Please let us know the exact difference and functionality of 3 modes.
Regards,
Aditya |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
What have you found in the documentation that is not clear?
If you post what is not clear, someone may be able to clarify. |
|
Back to top |
|
|
aditya_gupt
New User
Joined: 14 Jan 2006 Posts: 5 Location: Mumbai
|
|
|
|
Following are three different types:
First:
//STEP1 EXEC PGM=XCOMJOB,PARM=('TYPE=EXECUTE')
Second:
//STEP1 EXEC PGM=XCOMJOB,PARM=('TYPE=SCHEDULE')
Third:
//STEP1 EXEC PGM=XCOMJOB,PARM=('TYPE=INQUIRE')
Need to know what's the importance of these 3 different TYPEs. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
To repeat:
Quote: |
What have you found in the documentation that is not clear? |
Or, said slightly differently - what does the documentation say?
What have you done to find any of the info? |
|
Back to top |
|
|
aditya_gupt
New User
Joined: 14 Jan 2006 Posts: 5 Location: Mumbai
|
|
|
|
Sorry, if I couldn't answer your first question.
Let me try to explain, as of now we are using program XCOMJOB in our application to send out the files.
This program XCOMJOB is used in three different types, which i have mentioned above.
I am not refering any document, I tried to search docs on google but couldn't find anyhting explaining this difference.
As per my understanding, we use TYPE= EXECUTE to run the XCOM for immediate transfer.
But we are using SCHEDULE & INQUIRE in combination. First we are executing XCOMJOB program with SCHEDULE type, and then just after that with INQUIRE type.
What I feel, we use this schedule option for scheduled transfer, ie delayed transfer.
Now we are doing migration and trying to go away from XCOM, so we are trying to provide equivalent solutions. So i need to understand the the current functionality.
Hope it explains the situation. |
|
Back to top |
|
|
aditya_gupt
New User
Joined: 14 Jan 2006 Posts: 5 Location: Mumbai
|
|
|
|
Sorry, if I couldn't answer your first question.
Let me try to explain, as of now we are using program XCOMJOB in our application to send out the files.
This program XCOMJOB is used in three different types, which i have mentioned above.
I am not refering any document, I tried to search docs on google but couldn't find anyhting explaining this difference.
As per my understanding, we use TYPE= EXECUTE to run the XCOM for immediate transfer.
But we are using SCHEDULE & INQUIRE in combination. First we are executing XCOMJOB program with SCHEDULE type, and then just after that with INQUIRE type.
What I feel, we use this schedule option for scheduled transfer, ie delayed transfer.
Now we are doing migration and trying to go away from XCOM, so we are trying to provide equivalent solutions. So i need to understand the the current functionality.
Hope it explains the situation. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004 Posts: 4652 Location: Raleigh, NC, USA
|
|
|
|
It took me about a minute to go to the CA website, locate the product manuals for XCOM for z/OS, pick the User's Guide for the latest version, download the PDF, open it, search for "TYPE=EXECUTE", and immediately skip to the page in the PARM Parameters chapter which describes the different options for TYPE.
Again, as Dick already asked:
Quote: |
What have you found in the documentation that is not clear? |
It says that "TYPE" specifies how Unicenter CA-XCOM Data Transport is to process the transfer request. SCHEDULE queues the file transfer request and ends the job step when the transfer request is queued. TYPE=SCHEDULE is recommended for production jobs. TYPE=EXECUTE indicates that the file transfer is to be processed during the
execution of the current job. If the file transfer cannot be
executed before the specified job time-out interval, Unicenter
CA-XCOM Data Transport generates condition codes and
messages. TYPE=INQUIRE indicates whether all transfers specified in a job request have completed successfully, and whether any transfers were
incomplete or unsuccessful.
I don't know anything about the product, but it sounds like Synchronous processing, Asynchronous processing, and then administrative processing. |
|
Back to top |
|
|
aditya_gupt
New User
Joined: 14 Jan 2006 Posts: 5 Location: Mumbai
|
|
|
|
Many thanks for the help.
I found this link supportconnectw.ca.com/public/xcom/infodocs/xcom-mvs_menu.asp
before but couldn't access it as I don't have login to access it at CA website.
Would you please share product manuals for XCOM for z/OS to have a complete look. As per your explanation, the different Types are clear to me but I want to see the restrictions on every type. I mean which one to use in whihc case.
Many thanks in advance.
Best Regards,
Aditya Gupta |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Quote: |
but couldn't access it as I don't have login to access it at CA website.
Would you please share product manuals for XCOM for z/OS to have a complete look |
If your organization is licensed to use the product, you can register for CA support and download everything needed.
Much (most) of the CA documentation is covered by copyright and we may neither post it nor link to it via our forum. If any posts the same it is deleted and if people repeatedly post improper links/content they become banned.
Personally, i believe it is too dangerous to use a product and not have support. . . |
|
Back to top |
|
|
|