Hi Venkat, You need to use OSA/SF if you're using SNA mode on the OSE CHPID. Extract from OSA Express manual SA22-7935-14 below, where the "any other" refers to anything other than TCPIP Passthru using the default OAT:
---start extract Any other non-QDIO OSA-Express feature requires OSA/SF to configure the OSA. ---end extract Also, see the text for message IST1023E. cheers Peter On Sun, 17 Nov 2013 19:33:27 +0530, venkat kulkarni <[email protected]> wrote: >Hello, > We are trying to make SNA connectivity between CICS region on >z/OS 1.13 system using Bean connect and IBM communication controller >sitting on AIX system . >For doing this connectivity, we did below setup but somehow this >connectivity not working. > >1) I created OSE type of chipid and connected 30 devices with type OSA >using control unit. I have used OSE CHPID MAC address in AIX box for this >connection. > >2) I created XCA major node definition and used CUADDR= first device >number from above created 30 devices. > >OSA120MJ VBUILD TYPE=XCA EXT COMM ADAPTER MAJOR NODE >OSA120PT PORT MEDIUM=CSMACD, CSMA/CD 802.3 LAN + > ADAPNO=0, FIRST OSA ETHERNET PORT + > CUADDR=1200, CHANNEL UNIT ADDRESS + > TIMER=60, WAIT 60 SECS AFTER CHANNEL ACTIVATED + > SAPADDR=4 SERVICE ACCESS POINT ADDRESS >OSA120G1 GROUP DIAL=YES, LINES IN GROUP NEED SWITCHED PROT + > ANSWER=ON, PUS CAN DIAL TO VTAM WHEN LINE ACT + > AUTOGEN=(12,L,P), AUTO CREATE 12 LINES + > CALL=INOUT, INCOMING AND OUTGOING CALLS + > ISTATUS=ACTIVE LINE ACTIVE WHEN MAJ NODE ACTIVE > >3) I also created switched major node and in this I have used IDBLK and >IDNUM from the node_id = <05d12138> parameter in AIX system IBM >communication controller config file > >* >SNABD VBUILD TYPE=SWNET >ABD1 PU ADDR=04, * > IDBLK=05D, * > IDNUM=12138, * > CPCP=YES, * > DISCNT=NO, * > ISTATUS=ACTIVE, * > MAXPATH=4, * > MAXOUT=7, * > SSCPFM=USSSCS, * > USSTAB=USSTAB, * > USSTAB=USSTAB, * > MAXDATA=1033, * > PACING=0, * > VPACING=0, * > MODETAB=MODECIVM, * > PUTYPE=2 >PATH01 PATH DIALNO=00040015C5E836A6 >ABD101 LU LOCADDR=00, * > DLOGMOD=CICVLU62, * > MODETAB=MODECICV >ABD102 LU LOCADDR=00 INDEPENDENT NODE >ABD103 LU LOCADDR=00 INDEPENDENT NODE >ABD104 LU LOCADDR=00 INDEPENDENT NODE >ABD105 LU LOCADDR=00 INDEPENDENT NODE >ABD1L2 LU LOCADDR=02, 3270 LU2 SESSION * > DLOGMOD=M4G,MODETAB=M3278S >ABD1L3 LU LOCADDR=03, 3270 LU2 SESSION * > DLOGMOD=M4G,MODETAB=M3278S >ABD1A2 LU LOCADDR=12,USSTAB=USSNOMSG DEPENDENT LU FOR APPC >ABD1A3 LU LOCADDR=13,USSTAB=USSNOMSG DEPENDENT LU FOR APPC >ABD1A4 LU LOCADDR=14,USSTAB=USSNOMSG DEPENDENT LU FOR APPC > >3) We have CICS region name CICSB and below are VTAM defination > > > APPLCIC2 VBUILD TYPE=APPL >CICSB APPL ACBNAME=CICSB, NAME USED TO CONNECT TO VTAM X > AUTH=(ACQ,VPACE,PASS), ACQUIRE AND PASS DEVICES X > EAS=31, ESTIMATED NUMBER OF SESSIONS X > MODETAB=MODECICV, MODETABLE USED IF WE ARE SLU X > DLOGMOD=CICVLU62, DLOGMOD USED IF WE ARE SLU X > PARSESS=YES, MULTIPLE SESS WITH OTHER APPL X > SONSCIP=YES, USE SCIP EXIT IF WE ARE PLU X > APPC=NO, X > VPACING=5 VPACE TRAFFIC IF WE ARE SLU > >4) When I used to activate XCA and switched major node, I get below >messages and successfully gets activated. > >V NET,ACT,ID=XCA1200,SCOPE=ALL ----- XCA major node >IST097I VARY ACCEPTED >IST093I XCA1200 ACTIVE >IST1023E START I/O TIMEOUT OCCURRED FOR CUA=1200 > >V NET,ACT,ID=SNABD,SCOPE=ALL --- Switch MAJOR NODE >IST097I VARY ACCEPTED >IST093I ABD1 ACTIVE >IST093I SNABD ACTIVE > >4) But by looking more into IBM manual, I have changed CPCP parameter in >VTAM from LEASED to YES using MODFIY command for this connection. > >5) Now, when I m activating XCA major node, it gets activated with below >message > >V NET,ACT,ID=XCA1200,SCOPE=ALL ----- XCA major node >IST097I VARY ACCEPTED >IST093I XCA1200 ACTIVE >IST1023E START I/O TIMEOUT OCCURRED FOR CUA=1200 > >V NET,ACT,ID=SNABD,SCOPE=ALL --- Switch MAJOR NODE >IST097I VARY ACCEPTED >IST093I ABD1 ACTIVE >IST093I SNABD ACTIVE > > IST093I SNENG ACTIVE >IST380I ERROR FOR ID = L1200000 - REQUEST: ACTLINK, SENSE: 081C0000 >IST380I ERROR FOR ID = L1200002 - REQUEST: ACTLINK, SENSE: 081C0000 >IST380I ERROR FOR ID = L1200003 - REQUEST: ACTLINK, SENSE: 081C0000 >IST380I ERROR FOR ID = L1200001 - REQUEST: ACTLINK, SENSE: 081C0000 >IST380I ERROR FOR ID = L1200004 - REQUEST: ACTLINK, SENSE: 081C0000 >IST380I ERROR FOR ID = L1200005 - REQUEST: ACTLINK, SENSE: 081C0000 >IST380I ERROR FOR ID = L1200006 - REQUEST: ACTLINK, SENSE: 081C0000 >IST380I ERROR FOR ID = L1200007 - REQUEST: ACTLINK, SENSE: 081C0000 >IST380I ERROR FOR ID = L1200008 - REQUEST: ACTLINK, SENSE: 081C0000 >IST380I ERROR FOR ID = L1200009 - REQUEST: ACTLINK, SENSE: 081C0000 >IST380I ERROR FOR ID = L120000A - REQUEST: ACTLINK, SENSE: 081C0000 >IST380I ERROR FOR ID = L120000B - REQUEST: ACTLINK, SENSE: 081C0000 > >I tried investigating this issue using below link but not able to find >solution. > >http://www-01.ibm.com/support/docview.wss?uid=swg21160618 > > >6) From AIX side, we when I am trying for this connection, I am getting >below error. > >Link activation failed - adjacent link station *TST01* is not >responding. > >Adjacent station: MAC address = 00135ER7FA43 ( 00287AAB5LXC), SAP >address = 04 > >Local station: MAC address = 0014C5D839B6 ( 00A7A3156C45), SAP >address = 04 > >7) I also added below config in IBM Communication controller config file in >AIX to match with switched major node definition. I also used correct NETID >and SSCPNAME parameter in config file. > >[define_node] >cp_alias = ABD1 >fqcp_name = TIMBA.ABD1 > >Add a local LU definition to the Communication Server UNIX: > >[define_local_lu] > >lu_alias = ABD101 >list_name = "" >description = "" >lu_name = ABD101 > > >7) I also tried making connection from Mainframe to AIX box using ACT,PU >command that it successfully activated. But still this required connection >is not working. > >8) I am not sure, If I really need to implement OSA/SF also to make this >connection work. I feel this is optional feature not necessary to configure >at this stage. > >9) I also tried CPCP display command, but I don't see this connection . > >Please provide hint to resolve this issue > >---------------------------------------------------------------------- >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
