Problem opening VTAM-ACB
All, we currently move to another z/OS System (ADCD-based) and I have a poblem with one of our applications. This dialog-application generates the 3270 Datastream itself and communicates to the 3270 terminals using a VTAM ACB. I've configured this ACB as usual: AMYAPP VBUILD TYPE=APPL MYAPPAPPL APPC=YES, AUTH=(ACQ,PASS), MODETAB=LOGMODES, PARSESS=YES (of couse, I've put the continuation char in column 72) The command D NET,IP=MYAPP,SCOPE=ALL gives the following: IST075I NAME = ADCD.MYAPP, TYPE = APPL IST486I STATUS= CONCT, DESIRED STATE= CONCT IST1447I REGISTRATION TYPE = CDSERVR IST977I MDLTAB=***NA*** ASLTAB=***NA*** IST861I MODETAB=LOGMODES USSTAB=***NA*** LOGTAB=***NA*** IST934I DLOGMOD=***NA*** USS LANGTAB=***NA*** IST1632I VPACING = 8 IST1938I APPC = YES IST597I CAPABILITY-PLU INHIBITED,SLU INHIBITED,SESSION LIMIT NONE IST231I APPL MAJOR NODE = AMYAPP IST654I I/O TRACE = OFF, BUFFER TRACE = OFF IST1500I STATE TRACE = OFF IST271I JOBNAME = ***NA***, STEPNAME = ***NA***, DSPNAME ***NA*** IST228I ENCRYPTION = OPTIONAL , TYPE = DES IST1563I CKEYNAME = MYAPP CKEY = PRIMARY CERTIFY = NO IST1552I MAC = NONE MACTYPE = NONE IST1050I MAXIMUM COMPRESSION LEVEL - INPUT = 0, OUTPUT = 0 IST1633I ASRCVLM = 100 IST1634I DATA SPACE USAGE: CURRENT = ***NA*** MAXIMUM = ***NA*** IST171I ACTIVE SESSIONS = 00, SESSION REQUESTS = 00 IST172I NO SESSIONS EXIST IST314I END Now, when I tra to open the ACB in my assembler prog, I get the RC=8 in R15. This just says ACB was not opened - very helpful :-( Any hints how to track this down? My VTAM Skills are very, very, very limited (I'm a Coder - not an VTAM-Admin)! OPEN PACB ... PACB ACB AM=VTAM,APPLID=APPL1,EXLST=EXLST1,MACRF=LOGON EXLST1 EXLST AM=VTAM,LOGON=LOGON1,SYNAD=SYNAD1,LERAD=LERAD1, RESP=RESP1,TPEND=TPEND1,LOSTERM=LOSTERM1, DFASY=DFASY1,NSEXIT=NSEXIT1,RELREQ=RELREQ1,SCIP=SCIP1 . APPL1 DCX'08' APPL1A DCCL8'MYAPP ' Thank you very much for any hint! Bye, Michael -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem opening VTAM-ACB
Mike, There is an acb error code (2 or 4 bytes) that is useful. It used to be documented w/the VTAM OPEN as opposed to VSAM open. If I remember correctly it should be in the VTAM programming book(s). That will get you more detail. Ray Overby Michael Knigge wrote: All, we currently move to another z/OS System (ADCD-based) and I have a poblem with one of our applications. This dialog-application generates the 3270 Datastream itself and communicates to the 3270 terminals using a VTAM ACB. I've configured this ACB as usual: AMYAPP VBUILD TYPE=APPL MYAPPAPPL APPC=YES, AUTH=(ACQ,PASS), MODETAB=LOGMODES, PARSESS=YES (of couse, I've put the continuation char in column 72) The command D NET,IP=MYAPP,SCOPE=ALL gives the following: IST075I NAME = ADCD.MYAPP, TYPE = APPL IST486I STATUS= CONCT, DESIRED STATE= CONCT IST1447I REGISTRATION TYPE = CDSERVR IST977I MDLTAB=***NA*** ASLTAB=***NA*** IST861I MODETAB=LOGMODES USSTAB=***NA*** LOGTAB=***NA*** IST934I DLOGMOD=***NA*** USS LANGTAB=***NA*** IST1632I VPACING = 8 IST1938I APPC = YES IST597I CAPABILITY-PLU INHIBITED,SLU INHIBITED,SESSION LIMIT NONE IST231I APPL MAJOR NODE = AMYAPP IST654I I/O TRACE = OFF, BUFFER TRACE = OFF IST1500I STATE TRACE = OFF IST271I JOBNAME = ***NA***, STEPNAME = ***NA***, DSPNAME ***NA*** IST228I ENCRYPTION = OPTIONAL , TYPE = DES IST1563I CKEYNAME = MYAPP CKEY = PRIMARY CERTIFY = NO IST1552I MAC = NONE MACTYPE = NONE IST1050I MAXIMUM COMPRESSION LEVEL - INPUT = 0, OUTPUT = 0 IST1633I ASRCVLM = 100 IST1634I DATA SPACE USAGE: CURRENT = ***NA*** MAXIMUM = ***NA*** IST171I ACTIVE SESSIONS = 00, SESSION REQUESTS = 00 IST172I NO SESSIONS EXIST IST314I END Now, when I tra to open the ACB in my assembler prog, I get the RC=8 in R15. This just says ACB was not opened - very helpful :-( Any hints how to track this down? My VTAM Skills are very, very, very limited (I'm a Coder - not an VTAM-Admin)! OPEN PACB ... PACB ACB AM=VTAM,APPLID=APPL1,EXLST=EXLST1,MACRF=LOGON EXLST1 EXLST AM=VTAM,LOGON=LOGON1,SYNAD=SYNAD1,LERAD=LERAD1, RESP=RESP1,TPEND=TPEND1,LOSTERM=LOSTERM1, DFASY=DFASY1,NSEXIT=NSEXIT1,RELREQ=RELREQ1,SCIP=SCIP1 . APPL1 DCX'08' APPL1A DCCL8'MYAPP ' Thank you very much for any hint! Bye, Michael -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem opening VTAM-ACB
Michael Apropos of your excusing the lack of a character in column 72, you should continue operands by starting in column 16. Pasting your post into a Notepad caused the continuation to show as column 17 - but your VTAM DISPLAY command output shows that this change of column - also evident in the snippet of source code - is some sort of side-effect of your copy/paste process. There's nothing very usual about the way you have coded your APPL statement. I guess you must have been coding up TSO and a network solicitor to get you into the habit of coding AUTH=PASS. Maybe you have needed to code AUTH=ACQ for some applications, perhaps CICS, so you got into the habit of coding that also. I can't really be sure where you might have got into the habit of coding PARSESS=YES. Perhaps from the documentation of some APPC programs I've seen where the developers hadn't paid attention to the helpful way VTAM assumes PARSESS=YES when APPC=YES is specified. Unless your program uses the CLSDST macro with OPTCD=PASS specified, you will not need to AUTHorise that function. You will know that this is required if your program talks to the 3270 secondary process, typically an emulator on a PC these days, and then arranges for the 3270 secondary process to talk to another primary application, say CICS or some such. Unless your program issues - typically - the SIMLOGON macro, you will not need to AUTHorise that function with the AUTH=ACQ specification. You will know that this is required if you specify the LU name of the 3270 secondary process to your program and it initiates the session with the 3270 secondary process. Since this is a program using the 3270 data stream, I guess talking to a PC emulator, it will *not* require PARSESS=YES. It is much more likely to need the exact opposite, SESSLIM=YES. And most folk don't bother having to invent a name for the VBUILD statement - although *I think* I noticed from a customer with whom I was working recently that using the member name didn't cause any hiccoughs. Whether your MODETAB operand is a good idea or not rather depends on the contents of the LOGMODES member. I am rather encouraged by the fact that the name implies you have only one private mode table associated with the customisation of your VTAM. This is a happy situation for when the time comes for you to enable APPN. All your mode table entry problem should be dealt with by coding the DYNMODTB=LOGMODES start option - but I digress. Checking on all your operands, this analysis of your use of the adjective usual is not peripheral to the discussion but central. I just noticed that you have coded APPC=YES. This is most inappropriate for a VTAM program written to support the use of the 3270 data stream to the assumed PC emulator. The quick way - for a coder - I finally got to the end of your post! - to know whether or not APPC=YES is appropriate is to take a look at which VTAM programming manuals are being used in order to write the program. If it is exclusively SNA Programming, then APPC=YES is not to be specified (or, in order to emphasise the point, you can specify the default, APPC=NO). If SNA Programmer's LU 6.2 Guide and SNA Programmer's LU 6.2 Reference are also consulted, then APPC=YES is to be specified. Of course, if your skill in a particular area is limited, you should call on your colleague who has the necessary skill - assuming he/she has not been let go in the perhaps not so recent past! What your program logic should be doing immediately after the OPEN macro is to check whether the value of register 15 is zero or not - which I guess you are doing already. If it is not zero, you should then present the value of the ACBERFLG field for interpretation - and exit the program, of course. This was so much of a habit of VTAM program writers that these codes were copied to the VTAM messages manual - and are now found in the IP and SNA Codes manual. Having written that - I promise! - I checked the description of the OPEN macro in order to see if I could work out which code might have been used. And then I found exactly the coding advice I have just given written down! It would be interesting to know which code was used to describe your problem if you would be kind enough to post it. Chris Mason On Mon, 23 Jun 2008 16:24:36 +0200, Michael Knigge [EMAIL PROTECTED] SOFTWARE.DE wrote: All, we currently move to another z/OS System (ADCD-based) and I have a poblem with one of our applications. This dialog-application generates the 3270 Datastream itself and communicates to the 3270 terminals using a VTAM ACB. I've configured this ACB as usual: AMYAPP VBUILD TYPE=APPL MYAPPAPPL APPC=YES, AUTH=(ACQ,PASS), MODETAB=LOGMODES, PARSESS=YES (of couse, I've put the continuation char in column 72) The command D NET,IP=MYAPP,SCOPE=ALL gives the following: IST075I NAME = ADCD.MYAPP, TYPE = APPL IST486I
Re: Problem opening VTAM-ACB
Chis, thank you so far for your post! I wrote all the ACB and 3270 logic about nine years ago and I guess I've lost some knowledge over the years :-( adjective usual is not peripheral to the discussion but central. I just noticed that you have coded APPC=YES. This is most inappropriate for a VTAM program written to support the use of the 3270 data stream to the assumed PC emulator. We also support LU6.2 connections from the network - this is legacy code, nowadays we use TCP/IP are doing already. If it is not zero, you should then present the value of the ACBERFLG field for interpretation - and exit the program, of course. This was A, I forgot about this one as said, approx. nine years ago It would be interesting to know which code was used to describe your problem if you would be kind enough to post it. After all your efforts... I promise! ;-) I will try tomorrow and post the results Bye Thanks, Michael -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem opening VTAM-ACB
Chris, It would be interesting to know which code was used to describe your problem if you would be kind enough to post it. My Code is a F4: The application program is not authorized for SRBEXIT=YES. A request to open an ACB whose corresponding APPL definition statement specifies SRBEXIT=YES is rejected unless the application program is APF authorized, or using key 0-7, or in supervisor state. Ok, I don't run authorized. I added a SRBEXIT=NO to my VTAM-Definition but still in vain (and still F4) Seems I'm doning something really wrong locally. I also changed APPC=YES to APPC=NO in my VTAM-Definition but after a VARY NET,INACT,ID=MYAPPfollowed by a VARY NET,ACT,ID=MYAPP the command D NET,ID=MYAPP,SCOPE=ALL still shows APPC=YES Guess I have to grab the VTAM-Book ;) Bye, Michael -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem opening VTAM-ACB
Ok, I don't run authorized. I added a SRBEXIT=NO to my VTAM-Definition but still in vain (and still F4) Don't know why exactly, but now it works I've also stopped and started the Appl Major Node AMYAPP and now it works... THANK YOU!!! Bye, Michael -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Problem opening VTAM-ACB
Michael It was stopping and starting the application major node (VARY INACT followed by VARY ACT for the VTAMLST member I assume) which made the change APPC=YES to APPC=NO effective - think about it! You claimed in your definition of the APPL statement that the program was written for the APPC API and you were not in fact using the APPC API. I expect that confused VTAM sufficiently to cause it to return a most misleading ACBERFLG byte value. Anyhow thanks for the follow-up. Would that more OPs presenting problems came back with the answer to their problems. Chris Mason On Tue, 24 Jun 2008 00:10:41 +0200, Michael Knigge [EMAIL PROTECTED] SOFTWARE.DE wrote: Ok, I don't run authorized. I added a SRBEXIT=NO to my VTAM-Definition but still in vain (and still F4) Don't know why exactly, but now it works I've also stopped and started the Appl Major Node AMYAPP and now it works... THANK YOU!!! Bye, Michael -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
