Natural and other product zaps regularly have prerequisites for example;
* *+ZAP:NA93002
* -------- (C) Software AG, Darmstadt/Germany, 2012 --------
* ---------------- Release Date: 01.Nov.2012 ---------------
* PRODUCT: NAT823
* PREREQ. : NA92223
I suggest it would provide a more robust and reliable checking of prerequisites if a VER was included in the subsequent zaps. This would cause follow up zaps being applied without pre requisites and eliminating manual verification.
NAME NATURAL NATAZAP
VER 03A8 0000,2223
Co-req would not apply, though even in this case the first co-req could be checked by the second for example, the numerical sequence of zaps usually reflecting chronological order;
* *+ZAP:NA92246
* -------- (C) Software AG, Darmstadt/Germany, 2012 --------
* ---------------- Release Date: 30.Jul.2012 ---------------
* PRODUCT: NAT822
* PREREQ. : NA92069
* CO-REQ. : ******* NA92248
NAME NATURAL NATAZAP
VER 0140 0000,2069
* *+ZAP:NA92248
* -------- (C) Software AG, Darmstadt/Germany, 2012 --------
* ---------------- Release Date: 06.Aug.2012 ---------------
* PRODUCT: NAT822
* PREREQ. : NA92246
* CO-REQ. : NA92246 *******
NAME NATURAL NATAZAP
VER 0140 0000,2069
VER 0404 0000,2246
Cheers Kev
Our future thoughts are to provide complete load modules and not ZAPS. Therefore we do not plan to improve the prerequisites of ZAPS.