2023-05-03 11:06:20 +02:00
|
|
|
== Why is this an issue?
|
|
|
|
|
|
2021-04-28 16:49:39 +02:00
|
|
|
When using ``++CICS XCTL++`` or ``++CICS LINK++``, it is a bad practice not to specify the length of the communication area.
|
|
|
|
|
|
2021-04-28 18:08:03 +02:00
|
|
|
|
2023-05-03 11:06:20 +02:00
|
|
|
=== Noncompliant code example
|
2021-04-28 16:49:39 +02:00
|
|
|
|
2022-02-04 17:28:24 +01:00
|
|
|
[source,cobol]
|
2021-04-28 16:49:39 +02:00
|
|
|
----
|
|
|
|
|
EXEC CICS LINK PROGRAM ('SPI2TCV') COMMAREA (SPI-PARMCICS) RESP (WS-RESP) *> Noncompliant
|
|
|
|
|
|
|
|
|
|
EXEC CICS XCTL PROGRAM ('P4DERROR') COMMAREA (Y4DERROR) *> Noncompliant
|
|
|
|
|
----
|
|
|
|
|
|
2021-04-28 18:08:03 +02:00
|
|
|
|
2023-05-03 11:06:20 +02:00
|
|
|
=== Compliant solution
|
2021-04-28 16:49:39 +02:00
|
|
|
|
2022-02-04 17:28:24 +01:00
|
|
|
[source,cobol]
|
2021-04-28 16:49:39 +02:00
|
|
|
----
|
|
|
|
|
EXEC CICS LINK PROGRAM ('SPI2TCV') COMMAREA (SPI-PARMCICS) LENGTH (SPI-LONG) RESP (WS-RESP)
|
|
|
|
|
|
|
|
|
|
EXEC CICS XCTL PROGRAM ('P4DERROR') COMMAREA (Y4DERROR) LENGTH (Y4FLFIC-Y4DERROR)
|
|
|
|
|
----
|
2021-04-28 18:08:03 +02:00
|
|
|
|
