View previous topic :: View next topic
|
Author |
Message |
ug123 Warnings : 1 New User
Joined: 01 Mar 2007 Posts: 39 Location: Chennai
|
|
|
|
Hi,
I want to pass some data through parm to cobol program. Through parm i can send only 100 bytes, but i have a case where i have to send more than 100 bytes.
My program is already running in production so i couldnt touch the code. Even if we send through sysin i have to change the code.
Without changing the code, through jcl can anyone please tell me how to send the data.
Thanks,
Ugandar |
|
Back to top |
|
|
William Thompson
Global Moderator
Joined: 18 Nov 2006 Posts: 3156 Location: Tucson AZ
|
|
|
|
ug123 wrote: |
I want to pass some data through parm to cobol program. |
OK....
Quote: |
Through parm i can send only 100 bytes, but i have a case where i have to send more than 100 bytes. |
That too is do-able.....
Quote: |
My program is already running in production so i couldnt touch the code. Even if we send through sysin i have to change the code. |
Well, that makes it a bit harder....
Quote: |
Without changing the code, through jcl can anyone please tell me how to send the data. |
Now that is darn right stupid, if you didn't change the program, how would it know what to do with this new data? |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Quote: |
My program is already running in production so i couldnt touch the code. Even if we send through sysin i have to change the code. |
Your organization has a process to deal with design oversights and/or enhancements - this is one. Use the process and make the required change(s).
Is there something i don't understand as to why this is in the clist & rexx forum? |
|
Back to top |
|
|
ug123 Warnings : 1 New User
Joined: 01 Mar 2007 Posts: 39 Location: Chennai
|
|
|
|
Actually this is JCL thing.
i should not touch the code but i can play with jcl. this is the requirement
Thanks,
Ugandar |
|
Back to top |
|
|
William Thompson
Global Moderator
Joined: 18 Nov 2006 Posts: 3156 Location: Tucson AZ
|
|
|
|
100 bytes is the limit, either that is all you get or you have to change code somewhere......That is the requirement. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
What nonsense is this?
Quote: |
i should not touch the code but i can play with jcl |
Many bad things happen when someone "plays with jcl". If there was any real configuraton management or change control, production jcl is just as protected as the program code.
If the code no longer works, it needs to be fixed |
|
Back to top |
|
|
Craq Giegerich
Senior Member
Joined: 19 May 2007 Posts: 1512 Location: Virginia, USA
|
|
|
|
i suppose you could edit the load module and make changes to it. Then you wouldn't even have to change the jcl or come to work the next day. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Yup, that's why we have superzap. . . |
|
Back to top |
|
|
IQofaGerbil
Active User
Joined: 05 May 2006 Posts: 183 Location: Scotland
|
|
|
|
Is it possible that the data being passed might be keys or dates upon which the program will act?
Therefore increasing/varying the number of these could be a valid thing to do.
However when that number increases to beyond the 100 byte limit then a problem like this will be encountered.
If the OP could maybe explain what the PARM data is being used for , maybe there is a suggestion out there which could help. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
IMHO, as long as this
Quote: |
i should not touch the code but i can play with jcl. this is the requirement |
is "true", we will not be able to offer much. . . . |
|
Back to top |
|
|
|