Hi Richard, Yes. The dataset where where the exits reside is APF.
Em seg., 28 de ago. de 2023 às 16:24, Richard McIntosh < richard.mcint...@oracle.com> escreveu: > Is the library authorized that the exits on it? Make sure it is the APF > list. > LONG TEXT => The user-written exit program was not found in an > authorized > library. > > Richard > > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf > Of Gilson Cesar de Oliveira > Sent: Monday, August 28, 2023 2:18 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [External] : Connect Direct for z/Os Upgrade > > We are upgrading COnnect Direct for z/Os at version 4.8 to 5.1 (this is > the first step to upgrade to version 6.2) and we are facing issues for some > processes when using the new version of the loadlib of Connect Direct. > SCIB006I SIGNON COMMAND (CONDENSED) => USERID /NODE = > > SCIC000I Connect:Direct - RC=00000008 MSG=SCBA029I NODE= @ > 06:48:51 / 08/25/23 > SHORT TEXT => SCBA029I The user exit is not in an authorized library. > > LONG TEXT => The user-written exit program was not found in an > authorized > library. > > > SYSTEM ACTION: Signon fails. > > > RESPONSE: Make sure the exit is in an authorized library > and > was assembled non-reentrant and non-reusable. > > SCIC013I Terminating before EOF due to error return code (HEX) =00000018 > > SCIB007I COMMAND => SIGNOFF FORCED BY DMBATCH > > SCIC000I Connect:Direct - RC=00000010 MSG=SCIA008I NODE= @ > 06:48:52 / 08/25/23 > SHORT TEXT => SCIA008I Syntax Error finding word SIGNON in SIGNON > command. > LONG TEXT => C:D was unable to find the word SIGNON in the first > > command passed. The SIGNON command MUST NOT have a > > label on it, and the word SIGNON MUST be surrounded by > spaces. Common reasons for this message are: > 1) A LABEL starting in Column 1 > 2) The word SIGNON starting in Column 1 > 3) The word SIGNON not followed by a space. > > SYSTEM ACTION: Set Return code to 16, and Fail the signon > > We recompiled two exits DGAMGSAF and DGACXSIG and for some processes it's > working as expected but for this example above we can see errors. > > Do you have any idea why this errors are occurring? > > As a workaround we created a new version of the proc used by these > processes but pointing in the STEPLIB the dataset of the version V4.8 > instead of V5.1. > > Thanks for any help. > > Regards, > > Gilson > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
