Thanks to all. This issues is sorted now and customers able to ping. Thanks to all again.
On Thu, Jun 18, 2015 at 7:05 PM, Giovanni Bozzetti <[email protected]> wrote: > Yes, normally when the userid need an OMVS segment the groupid is good to > have also an UID > > The message is clear it works so I believe your USERID now has the > UID=1000, you can try the PING, need to work, if not just add a GID to > group $ADT > > Did you try the PING? Need to work instead $ADT don't have GID > > Giovanni > System Programmer > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Mainframe Mainframe > Sent: Thursday, June 18, 2015 09:58 AM > To: [email protected] > Subject: Re: OMVS segment Issue > > Now I tried adding UID for this user and getting below messages. > > tso altuser user1 OMVS(UID(1000)) > > and getting below message. > > > USER user1 IS ASSIGNED AN OMVS UID, BUT DEFAULT GROUP $ADT DOES NOT HAVE A > GID PROCESSING CONTINUES. > > > > On Thu, Jun 18, 2015 at 5:48 PM, Mainframe Mainframe < > [email protected]> wrote: > > > I just checked the user id and found that we have not set UID for this > > user.Can it be reason for this issue. > > > > UID= NONE > > HOME= /u/user1 > > PROGRAM= /bin/sh > > CPUTIMEMAX= NONE > > ASSIZEMAX= NONE > > FILEPROCMAX= NONE > > PROCUSERMAX= NONE > > THREADSMAX= NONE > > MMAPAREAMAX= NONE > > > > > > > > On Thu, Jun 18, 2015 at 4:01 PM, Giovanni Bozzetti > > <[email protected]> > > wrote: > > > >> Hi > >> > >> You probably need to define an OMVS segment to the TSO userid to use > >> TCPIP access or USS. > >> > >> Suppose your TSO userid is USER01, and you are a RACF administrator > >> you can do below command, if not do the command inside the USER01 if > >> RACF administrator authorize, if not require any RACF administrator > >> to do this command. > >> > >> You can use TSO LU USER01 OMVS to verify if it has an OMVS segment > >> if not define one number > >> > >> If no OMVS try to define one and see if helps to use PING. > >> > >> If you are a RACF administrator you can run this JOB, if not call > >> your security administrator and run. > >> > >> //ST1 EXEC PGM=IKJEFT01 > >> //SYSTSPRT DD SYSOUT=* > >> //SYSTERM DD DUMMY > >> //SYSTSIN DD * > >> ALTUSER USER01 + > >> OMVS(UID(56789) + <== any number can’t be repeated > >> HOME('/u/user01') + > >> PROGRAM('/bin/sh') ) > >> > >> > >> Regards > >> Giovanni > >> System programmer > >> > >> -----Original Message----- > >> From: IBM Mainframe Discussion List [mailto:[email protected]] > >> On Behalf Of Mainframe Mainframe > >> Sent: Thursday, June 18, 2015 06:11 AM > >> To: [email protected] > >> Subject: OMVS segment Issue > >> > >> we getting below error while using ping command on tso and > >> getting failed with > >> > >> > >> > >> CEE5101C During initialization, the callable service BPX1MSS failed. > >> > >> The system return code was 0000000156 , the reason code was > >> 0B0C00FC . > >> > >> The application will be terminated. > >> > >> > >> > >> When I checked for this error, I found below link > >> > >> > >> > >> > >> http://www-304.ibm.com/support/knowledgecenter/SS2L7A_5.2.0/doc/ccv-i > >> nstall-omvs.html > >> > >> > >> > >> and this link talks about this issue, I found below steps > >> > >> > >> > >> 1. Define an OMVS segment in RACF for the TSO user IDs that invoke > CICS > >> Configuration Manager clients. > >> > >> 2. Allow the TSO user IDs to execute BPX* programs > >> > >> > >> > >> But there are many BPX.** profile available in system like > >> > >> > >> BPX.DAEMON > >> > >> BPX.FILEATTR.APF > >> > >> BPX.FILEATTR.PROGCTL > >> > >> BPX.FILEATTR.SHARELIB > >> > >> BPX.SERVER > >> > >> BPX.SUPERUSER > >> > >> > >> etc > >> > >> > >> Which one to give access, not sure for this ping issue to get resolved. > >> > >> > >> Please suggest. > >> > >> --------------------------------------------------------------------- > >> - 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 > >> > > > > > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
