|
View previous topic :: View next topic
|
| Author |
Message |
ayapatsr
New User
Joined: 01 Apr 2009
Posts: 14
Location: pune
|
|
|
|
Hi Frnds,
i am executing a CICS comand.
| Code: |
EXEC CICS ASKTIME ABSTIME (var1) END-EXEC
EXEC CICS
FORMATTIME ABSTIME (var1)
DATESEP ('/') DDMMYYYY (var2)
TIME (W03-TIME) TIMESEP
END-EXEC
|
it was working fine from the past 10years.
now i tried to compile the source today its getting compilation erreo at CICS transilator step.
error:
| Code: |
1CICS/ESA COMMAND LANGUAGE TRANSLATOR VERSION 3.2
0TRANSLATOR DIAGNOSTIC MESSAGES OF SEVERITY W AND ABOVE.
0MESSAGE NUMBER SEVERITY LINE NUMBER MESSAGE
DFH7067I W 00673 'DDMMYYYY' IS NOT VALID. 'DDMMYY' ASUMED
DFH7209I C 00673 A BLANK IS ASSUMED BETWEEN 'DDMMYY' A BLANK IS ASSUMED BETWEEN 'DDMMYY' AND 'YY'.
DFH7204I E 00673 'DDMMYY' KEYWORD REQUIRES 1 SUB-OPERAND(S). STATEMENT NOT TRANSLATED.
DFH7053I C 00673 OPTION 'YY' IS NOT VALID AND IS IGNOR
|
is there any changes in CICS versions?Why this is getting error?
z/OS version is V1.9. |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
it was working fine from the past 10years.
now i tried to compile the source today |
What has changed since the last successful compile? It is not so much a concern that it worked 10 years ago - did it work last week, last month, etc. . .? |
|
| Back to top |
|
|
ayapatsr
New User
Joined: 01 Apr 2009
Posts: 14
Location: pune
|
|
|
|
Yes it is working in production daily.
there is some updations in the code(array size increase),so i compiled it in test region.nothing changed in CICS comands.
while transilator step getting that error."DDMMYYYYY is not acceptable and DDMMYY is assumed"
VAR1 PIC 9(15) COMP-3 VALUE 0.
VAR2 PIC X(10) VALUE SPACES. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| What has changed since the last successful compile? |
I probably should have been more specific. . .
What has changed in the environment (not the application code) since the last successful compile?
| Quote: |
| nothing changed in CICS comands. |
Not in the code, but what has changed in the environment? New version of the operating system? CICS? The COBOL Compiler? |
|
| Back to top |
|
|
ayapatsr
New User
Joined: 01 Apr 2009
Posts: 14
Location: pune
|
|
|
|
Thanks
current versions
CICS/ESA COMMAND LANGUAGE TRANSLATOR VERSION 3.2
z/OS version 1.9
using the translator DFHECP1$ and PARM='COBOL2,NOSOURCE,VBREF,NOSEQ'
cobol compiler IGYCRCTL
PARM=('BUF(32760),LIB,XREF,NOSEQ,NODYNAM,RES,RENT',
'TRUNC(BIN),OFFSET,FDUMP')
even the production code also running on this versions only
please help me on this.
Thanks |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10872
Location: italy
|
|
|
|
| do other commands get translated/preprocessed properly ?? |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| I would change the translator parm from NOSOURCE to SOURCE to confirm exactly what is showing up -- sometimes the suppressed messages include critical data. |
|
| Back to top |
|
|
ayapatsr
New User
Joined: 01 Apr 2009
Posts: 14
Location: pune
|
|
|
|
Thanks,
Tried wit changing translator parm NOSORCE to SOURCE,but no improvement.getting same problem.
its just displaying the expanded source code in spool.earliear only error displayed. |
|
| Back to top |
|
|
|
|
