|
View previous topic :: View next topic
|
| Author |
Message |
withnams
New User
Joined: 06 Jul 2005
Posts: 26
Location: Chennai
|
|
|
|
We are trying to pass the date 02/04/05 to COBOL from JCL.
We tried
1. PARM='02/04/05'
2. PARM=(02/04/05)
2. PARM=&EFFDT
etc...
But the program ran fine, but in the SYSOUT it is throwing out message that 05 (last 2 bytes) is not a valid run type options.
We want to avoid the message. So if any one of u have come accross please let me know... |
|
| Back to top |
|
 |
rssomm
New User
Joined: 05 Jun 2005
Posts: 41
Location: Hyderabad
|
|
|
|
| What is the pic clause of the variable reecving this date thru PARM? |
|
| Back to top |
|
|
Rupesh.Kothari
Member of the Month
Joined: 27 Apr 2005
Posts: 463
|
|
|
|
Hi withnams,
Please check ur PIC Clause> My it contain only 6 char length. |
|
| Back to top |
|
|
jayesh_g
New User
Joined: 03 Mar 2004
Posts: 23
|
|
|
|
In PARM, '/' has a special significance. It delineates the program arguments from the run-time options. In your case, it is
| Code: |
| PARM='program-arguments/run-time-options' |
The last slash in a string delineates the program arguments from the run-time options. Anything before the last slash is interpreted as a program argument.
So don't use '/' in PARM  |
|
| Back to top |
|
|
die7nadal
Active User
Joined: 23 Mar 2005
Posts: 156
|
|
|
|
I want to add some more to what jayesh_g said,
| Quote: |
| Anything before the last slash is interpreted as a program argument. |
This is true so, why not end the PARM with a '/' and you wont get the SYSOUT message. Ofcourse the program would run fine irrespective of the SYSOUT message. I was able to avoid the SYSOUT message by doing this. |
|
| Back to top |
|
|
|
|
