Coming in a little late here, but I don't understand the issue. Isn't EXLST coded on the DCB macro? So when the exit code gets invoked, why wouldn't you know in the exit what DCB called the exit?
So, even in the case of a multiple open, the DCB macro invokes the exit list code... Joe On Wed, Oct 24, 2018 at 12:00 PM ITURIEL DO NASCIMENTO NETO < [email protected]> wrote: > Mr Relson, > > Thanks for your feed back. > So, i assume that using an interface like VSMLIST should be more effective. > I'll give it a try. > > Atenciosamente / Regards / Saludos > > Ituriel do Nascimento Neto > BANCO BRADESCO S.A. > 4250 / DITI Engenharia de Software > Sistemas Operacionais Mainframes > Tel: +55 11 3684-9602 R: 49602 3-1404 > Fax: +55 11 3684-4427 > > > > -----Mensagem original----- > De: IBM Mainframe Discussion List [mailto:[email protected]] Em > nome de Peter Relson > Enviada em: quarta-feira, 24 de outubro de 2018 08:50 > Para: [email protected] > Assunto: Re: DCB Open Exit > > (Purely guessing, might be totally wrong) > > There is no way to tell because there is no association between the > processing done for the multiple DCBs other than possibly respect to > backing out upon error.. > Your exit will get control for each of these three and there is no > difference to the exit between one OPEN with three DCBs and three > consecutive OPENs. > > So do whatever you would do if you saw three consecutive OPENs. (No fields > in the LDA are programming interfaces, so use them completely at your own > risk.) > > Peter Relson > z/OS Core Technology Design > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to [email protected] with the message: INFO IBM-MAIN > > AVISO LEGAL <br>...Esta mensagem é destinada exclusivamente para a(s) > pessoa(s) a quem é dirigida, podendo conter informação confidencial e/ou > legalmente privilegiada. Se você não for destinatário desta mensagem, desde > já fica notificado de abster-se a divulgar, copiar, distribuir, examinar > ou, de qualquer forma, utilizar a informação contida nesta mensagem, por > ser ilegal. Caso você tenha recebido esta mensagem por engano, pedimos que > nos retorne este E-Mail, promovendo, desde logo, a eliminação do seu > conteúdo em sua base de dados, registros ou sistema de controle. Fica > desprovida de eficácia e validade a mensagem que contiver vínculos > obrigacionais, expedida por quem não detenha poderes de representação. > LEGAL ADVICE<br>...This message is exclusively destined for the people to > whom it is directed, and it can bear private and/or legally exceptional > information. If you are not addressee of this message, since now you are > advised to not release, copy, distribute, check or, otherwise, use the > information contained in this message, because it is illegal. If you > received this message by mistake, we ask you to return this email, making > possible, as soon as possible, the elimination of its contents of your > database, registrations or controls system. The message that bears any > mandatory links, issued by someone who has no representation powers, shall > be null or void. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
