|
View previous topic :: View next topic
|
| Author |
Message |
lavanya.purini
New User
Joined: 21 Jun 2007
Posts: 4
Location: hyderabad
|
|
|
|
| Max length we can give thru PARM parameter is 100. What if we send PARM of lenght more than 100 chars? Will it give any JCL error or any abend?? |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| did You try?? |
|
| Back to top |
|
|
lavanya.purini
New User
Joined: 21 Jun 2007
Posts: 4
Location: hyderabad
|
|
|
|
| No |
|
| Back to top |
|
|
ofer71
Global Moderator
Joined: 27 Dec 2005
Posts: 2358
Location: Israel
|
|
|
|
Please try and let us know... 
O. |
|
| Back to top |
|
|
Phrzby Phil
Senior Member
Joined: 31 Oct 2006
Posts: 1042
Location: Richmond, Virginia
|
|
|
|
| Or perhaps we should grind our work to a halt to save you one minute? |
|
| Back to top |
|
|
lavanya.purini
New User
Joined: 21 Jun 2007
Posts: 4
Location: hyderabad
|
|
|
|
I tried it and its giving jcl error as "EXCESSIVE PARAMETER LENGTH IN THE PARM FIELD"
thanks for ur replies... |
|
| Back to top |
|
|
William Thompson
Global Moderator
Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ
|
|
|
|
| Thank you for the answer. |
|
| Back to top |
|
|
digitalnirmal@hotmail
New User
Joined: 27 Dec 2005
Posts: 1
|
|
|
|
| but isn't there a way around? |
|
| Back to top |
|
|
murmohk1
Senior Member
.jpg)
Joined: 29 Jun 2006
Posts: 1436
Location: Bangalore,India
|
|
|
|
Nirmal,
| Quote: |
| but isn't there a way around |
Using PARM parmeter - NO
But we do have other methods for passing data to the program. Use these methods. |
|
| Back to top |
|
|
Santoshdorge
New User
Joined: 27 Jun 2006
Posts: 48
Location: Pune
|
|
|
|
Hi
You can use the flat file to pass the information to the program if it's length is more than 100 characters.
Thanks,
Santosh |
|
| Back to top |
|
|
lavanya.purini
New User
Joined: 21 Jun 2007
Posts: 4
Location: hyderabad
|
|
|
|
| yes we can use flat file to send record of length more than 100 charecters,but thru PARM prameter its not possible. |
|
| Back to top |
|
|
sundar28
New User
Joined: 30 Jul 2005
Posts: 11
Location: Mysore
|
|
|
|
| lavanya.purini wrote: |
| yes we can use flat file to send record of length more than 100 charecters,but thru PARM prameter its not possible. |
Hi lavanya.purini,
It is possible without using PARM.
You can use SYSIN (in JCL) and ACCEPT to feed to a COBOL program.
This method will not pass the length of the parameter string as the first two bytes. So you have to pass either a fixed length string or length seperated as part of the parameter and interpret it in your program.
Regards
Sundar |
|
| Back to top |
|
|
murmohk1
Senior Member
Joined: 29 Jun 2006
Posts: 1436
Location: Bangalore,India
|
|
|
|
Sundar,
| Quote: |
| You can use SYSIN (in JCL) and ACCEPT to feed to a COBOL program. |
You are using dataset again. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Hi,
I think, Sundar is talking about 'in-stream' data. |
|
| Back to top |
|
|
murmohk1
Senior Member
Joined: 29 Jun 2006
Posts: 1436
Location: Bangalore,India
|
|
|
|
Anuj,
| Quote: |
| I think, Sundar is talking about 'in-stream' data. |
I do agree, you can pass in-stream data in the job, but not in the proc. |
|
| Back to top |
|
|
shreevamsi
Active User
Joined: 23 Feb 2006
Posts: 305
Location: Hyderabad,India
|
|
| Back to top |
|
|
ug123
Warnings : 1
New User
Joined: 01 Mar 2007
Posts: 39
Location: Chennai
|
|
|
|
Hi all,
But for this i have to change the code also..
If the code runs in production and if i could not touch the code and in this case i can change only the jcl..
Any other way to send data more than 100 characters through jcl.. Because im facing this problem..
Can anyone please help me out..
Thanks,
Ugandar |
|
| Back to top |
|
|
murmohk1
Senior Member
Joined: 29 Jun 2006
Posts: 1436
Location: Bangalore,India
|
|
|
|
Ugandar,
| Quote: |
| If the code runs in production and if i could not touch the code and in this case i can change only the jcl.. |
Why the program edit is not allowed? Any specific reasons for this. |
|
| Back to top |
|
|
ug123
Warnings : 1
New User
Joined: 01 Mar 2007
Posts: 39
Location: Chennai
|
|
|
|
Yes the reason is the code is already running in production.. i could not touch the code.. the only thing i can do is i can play with the jcl..
Thanks,
Ugandar |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
Any other way to send data more than 100 characters through jcl.. Because im facing this problem..
Can anyone please help me out.. |
No, no one can help you out. If the program needs more than 100 bytes of "parameter" data, the program will have to be changed.
| Quote: |
the only thing i can do is i can play with the jcl..
|
This is total nonsense. Why in the world would it be ok to "play" with producton jcl and not the program. Both should follow a promotion process and not just be "thrown in". If the need is urgent, most organizations have an "emergency repair" promotion policy that allows immediate correction of a problem rather than the longer procedure. Once the emergency is resolved, the normal process is followed to somplete the repair. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
If the program now needs more than 100 bytes of "parameter data" and previously it did not, how would the existing code use the new data without being modified? |
|
| Back to top |
|
|
ug123
Warnings : 1
New User
Joined: 01 Mar 2007
Posts: 39
Location: Chennai
|
|
|
|
The scenario is we are sending the compiler options via parm to a cobol program. Previously we were sending which is not more than 100 bytes but as per the current situation we are supposed to send more than 100 bytes..
Thanks,
Ugandar |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| we are sending the compiler options via parm to a cobol program |
If you explain what this does, it will help. What kind of process are you using that requires sending compiler options to a program?
The more you explain, the more likely it is that someone will be able to help. |
|
| Back to top |
|
|
Craq Giegerich
Senior Member
Joined: 19 May 2007
Posts: 1512
Location: Virginia, USA
|
|
|
|
| This keeps getting more and more interesting (amusing). |
|
| Back to top |
|
|
Craq Giegerich
Senior Member
Joined: 19 May 2007
Posts: 1512
Location: Virginia, USA
|
|
|
|
| ug123 wrote: |
The scenario is we are sending the compiler options via parm to a cobol program. Previously we were sending which is not more than 100 bytes but as per the current situation we are supposed to send more than 100 bytes..
Thanks,
Ugandar |
Have you tried using the abbreviated versions of the compiler options? Why are you sending the compiler options to a cobol program. Instead of telling us what you can not do why don't you explain what you are trying to do, then maybe could help you. |
|
| Back to top |
|
|
|
|
