>ISTR that ALET 1 doesn't really work for parameters passed to BCP services.
As usual, Chris remembers well. The general rule is that the caller cannot ALET-qualify his parameter using ALET=1. Services such as TESTART treat ALET=1 as "not valid". And the reason is because if the interface happens to be a space-switch PC, the caller's secondary is not available to the target routine. And even if the PC "today" is not space-switch, the service provider likes to reserve the right to change to a space-switch PC if there is benefit to doing so. Restricting ALET=1 "now" generally makes such a change compatible. The ALET=1 rule is similar to the general rule that a caller cannot ALET-qualify using an ALET that is on the PASN access list. Here, similarly, if the PC is space-switch, the target routine cannot use this ALET. Exceptions should be made for ALETs representing common area data spaces (which are on the PASN access list, but since they are on every PASN access list, they can be used regardless of the target routine's ASN). Not every service recognized this, so there are surely some services that apply the rule "no PASN access list ALET" without the exception. If there is a business case made, a request to change such services might well be accepted. Peter Relson z/OS Core Technology Design
