Joined: 15 Dec 2002 Posts: 637 Topics: 43 Location: Bengaluru, INDIA
Posted: Wed Sep 10, 2003 2:23 am Post subject:
Coolman,
Would you not be reading the temp dataset created above? Or, you want the name of the temporary dataset? If it is the latter, is there a problem with having a cataloged dataset?
I mean, I do not quite understand the main requirement. _________________ ALL opinions are welcome.
Debugging tip:
When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
-- Sherlock Holmes.
Joined: 03 Jan 2003 Posts: 283 Topics: 27 Location: US
Posted: Wed Sep 10, 2003 3:35 am Post subject:
Cogito,
Good to see you back. BTW, have you quit the other forum. Im not seeing you at all these days.
Coming on to the subject, my first sort step would write out a temp file, which will contain some parm information to the subsequent COBOL program. Answering your question, I would not reading the temp dataset.
Im not able to appreciate your idea behind using a cataloged dataset, what purpose its going to serve.
The objective is that there is a dataset, which has some information, now that dataset has to be re-formatted and passed as parm to a subsequent job step. Now, that is the reason why I had asked whether if parm can be passed as a temporary dataset. (I don't think it can be done, but wanted to know if somebody has "discovered" some workarounds for this).
Also, I dont want to change the program in the next step to read the file itself and re-format the parm.
Joined: 15 Dec 2002 Posts: 637 Topics: 43 Location: Bengaluru, INDIA
Posted: Wed Sep 10, 2003 3:47 am Post subject:
Thanks Coolman.
I am very much present in both the fora! I am Nagesh_S there. Something happened to my ID there.
At first glance, I was not sure. I could make only 2 things. One, you want to read the dataset and the other, you wanted to read only the dataset name. For the latter, a cataloged dataset seems more easy.
But, why send the dataset via a PARM? Even if it were possible, you know that PARM cannot exceed 100 chars. At any rate, a dataset is definitely greater than PARM. So, why not read the temp dataset?
Or, code a step using DFSORT such that the contents of the relevant dataset appears in PARM. That is, something like,
OUTREC FIELDS=(C'// PARM=(',1,nn,C')')
where, 1,n points to the data in the temporary dataset. The SORTOUT can point to INTRDR.
You won't do the above, would you? _________________ ALL opinions are welcome.
Debugging tip:
When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
-- Sherlock Holmes.
Joined: 03 Jan 2003 Posts: 283 Topics: 27 Location: US
Posted: Wed Sep 10, 2003 4:45 am Post subject:
Cogito,
I have been through your profile, and know your name to be Nagesh Subrahmanyam. In fact, I had guessed it(not only with the name, but with your answers as well), but your location used to be Mumbai and now its banglore and that cast a doubt in my mind. Anway, b2b, couple of questions and assumptions here:
1. Parm will hardly be only 10 characters max.
Quote:
So, why not read the temp dataset?
Do you say that I have to read it inside the COBOL Program?If Yes, the answer is no, im not able(allowed) to do it. If no, how else should I read it.
Coming to the DFSORT OUTREC, let me take this example.
Now Inside my COBOL Program, I have a linkage section and an accept statement
Now, how do i pass the SORTOUT created in STEP1 to SOMECBOLPGM in STEP2. Is there a way for this? You have pointed out abt using an INTRDR, again which Im not allowed to do that part.
Hope this clarifies everything.
Cheers,
Coolman.
P.S : I have also proposed a REXX solution to them, but didnt go thro'
________
Ferrari 365
Last edited by coolman on Sat Feb 05, 2011 1:29 am; edited 1 time in total
Joined: 15 Dec 2002 Posts: 637 Topics: 43 Location: Bengaluru, INDIA
Posted: Wed Sep 10, 2003 5:32 am Post subject:
Coolman,
Yes. I am in Banglore nowadays.
I was suggesting (what Kolusu has pointed) that, instead of using PARM, LINKAGE SECTION, process the temp dataset as just any other dataset.
I was wondering, why were you insisting to read via PARM, LINKAGE SECTION, etc. instead of plain old sequential dataset processing. _________________ ALL opinions are welcome.
Debugging tip:
When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
-- Sherlock Holmes.
Joined: 03 Jan 2003 Posts: 283 Topics: 27 Location: US
Posted: Tue Oct 07, 2003 7:53 am Post subject:
Kolusu,
I was wondering, if the scenario was slightly different.
Say we have a file, which has a date(gets updated everyday). Now, i want to execute a job everday which is creating some files. Now, if one of the qualifiers for that file is the rundate(present in the file), how do we go about doing it. Couple of ways of doing it.
1. Run 2 jobs, the first job(SORT job) creating an SET statement, which can be included in the actual job or alternatively, submitting the actual directly to INTRDR, from the 1st job (Add another step to the SORT job)
2. Using skeletons.
Are there any other workarounds or rather simpler way of doing it ??
Joined: 26 Nov 2002 Posts: 12375 Topics: 75 Location: San Jose
Posted: Tue Oct 07, 2003 8:28 am Post subject:
coolman,
If I understand correctly , You want to create a dataset with the parm-value as one of the qualifier.If that is true then the easiest way I can think of is to create the datasets as usual and then do a rename of the dataset.The only hitch is that you cannot rename a tape dataset. You can generate the rename cards in the program which reads the parm-value.
Let me know if my assumptions are correct and I will post the code to generate the rename cards in the program
Joined: 03 Jan 2003 Posts: 283 Topics: 27 Location: US
Posted: Tue Oct 07, 2003 8:47 am Post subject:
Got you sir, the method you had suggested would involve a single job with 1 more step added.
One small clarfication, why not generate the rename cards in a separate step instead of the program. Also, "The usual datasets have to be hardcoded in the rename sysin card".
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
