>So anyone have any ideas how to avoid the HLL programmer doing a >CALL and executing data? > What is really the issue? It's going to get picked up in program testing if someone does it.
If an HLL program attempts to CALL and instead you make the table otherwise unavailable it is just going to abend in some way anyway (unless you "handle" it). You could put, at the "entry point" some code to specifically do something (like an explanatory message and then some controlled explosion), which would help when someone does the wrong thing - but how often would that be? People shouldn't just be using a module because they can see it on a library list. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
