COMPGROUPS.NET | Search | Post Question | Groups | Stream | About | Register

CICS VERIFY PASSWORD command issue.

  • Follow


Hi all,

I'm having a bit of a problem with checking the return codes from a
EXEC CICS VERIFY PASSWORD command.

Code as follows
CODE
WORKING-STORAGE SECTION.
 01  WSBB-PASSWORD        PIC X(8) VALUE SPACES.
 01  WSBB-USERID          PIC X(8) VALUE SPACES.
 01  WSBB-RESP-CODE       PIC S9(8) COMP VALUE ZEROS.
 01  WSBB-RESP-CODE1      PIC S9(8) COMP VALUE ZEROS.
 01  WSBB-RESP-CODE2      PIC S9(8) COMP VALUE ZEROS.
 01  WSBB-RETURN-CODE     PIC S9(8) COMP VALUE ZEROS.
 01  WSBB-DAYS-LEFT       PIC S9(4) COMP VALUE ZEROS.
 01  WSBB-RET-CODE        PIC -9(10).
 01  WSBB-CHANGETIME      PIC S9(15) COMP-3.
 01  WSBB-INVALIDCOUNT    PIC S9(4) COMP VALUE ZEROS.
 01  WSBB-LASTUSETIME     PIC S9(15) COMP-3.
 01  WSBB-EXPIRYTIME      PIC S9(15) COMP-3.
 01  WSBB-TIME            PIC X(64) VALUE SPACES.
 PROCEDURE DIVISION.
*
 100-MAINLINE SECTION.
**********************
*
 101-PARA.
     MOVE 'usernam' to WSBB-USERID.
     MOVE 'PASSWOR' to WSBB-PASSWORD.
     EXEC CICS VERIFY PASSWORD(WSBB-PASSWORD) USERID(WSBB-USERID)
          DAYSLEFT(WSBB-DAYS-LEFT)
          EMSRESP(WSBB-RESP-CODE1)
          EMSREASON(WSBB-RESP-CODE2)
          CHANGETIME(WSBB-CHANGETIME)
          INVALIDCOUNT(WSBB-INVALIDCOUNT)
          LASTUSETIME(WSBB-LASTUSETIME)
          EXPIRYTIME(WSBB-EXPIRYTIME)
          RESP(WSBB-RESP-CODE)
          RESP2(WSBB-RETURN-CODE)
     END-EXEC.

All done according to the manuals.
Command works fine, but the values of RESP AND RESP2 are always
invalid values. This is still the case if I use the cics precompiler
eibresp and eibresp2 fields.

In all cases the values returned on these 2 fields are
RESP= -0268166945
RESP2= 1342181408
even if the command was sucessefull, on which case RESP should be
equal zero.

All other return fields are correct upon execution.

This is Z/OS 1.07
CICS/ESA V6.2.0
CICS Transaction Server Version 2.2.0
ENTERPRISE COBOL FOR Z/OS  3.4.1 0402

compile options in place
ADV,NOAWO,BUFSIZE(22528),NOCOMPILE(S),DATA(31)     
NODBCS,NODECK,NODUMP,NODYNAM,FASTSRT               
FLAG(I),NOFLAGSTD                                  
LANGUAGE(UE),LIB,LINECOUNT(60),LIST,MAP,NONAME     
NONUMBER,NUMPROC(NOPFD),OBJECT,NOOFFSET,OPTIMIZE   
OUTDD(SYSOUT),RENT,NOSEQUENCE,SIZE(MAX)            
SOURCE,SPACE(1),NOSSRANGE,NOTERM,NOTEST,TRUNC(STD)
NOVBREF,NOWORD,XREF(FULL),NOZWB,APOST              

Already tried with different TRUNC(xxx) with no luck.

Any ideas/suggestions welcome
 

Regards


Frederico Fonseca
ema il: frederico_fonseca at syssoft-int.com
0
Reply real-email-in-msg-spam (383) 5/2/2008 6:00:34 PM 

Frederico Fonseca wrote:
> Hi all,
> 
> I'm having a bit of a problem with checking the return codes from a
> EXEC CICS VERIFY PASSWORD command.
> 
> Code as follows
> CODE
> WORKING-STORAGE SECTION.
>  01  WSBB-PASSWORD        PIC X(8) VALUE SPACES.
>  01  WSBB-USERID          PIC X(8) VALUE SPACES.
>  01  WSBB-RESP-CODE       PIC S9(8) COMP VALUE ZEROS.
>  01  WSBB-RESP-CODE1      PIC S9(8) COMP VALUE ZEROS.
>  01  WSBB-RESP-CODE2      PIC S9(8) COMP VALUE ZEROS.
>  01  WSBB-RETURN-CODE     PIC S9(8) COMP VALUE ZEROS.
>  01  WSBB-DAYS-LEFT       PIC S9(4) COMP VALUE ZEROS.
>  01  WSBB-RET-CODE        PIC -9(10).
>  01  WSBB-CHANGETIME      PIC S9(15) COMP-3.
>  01  WSBB-INVALIDCOUNT    PIC S9(4) COMP VALUE ZEROS.
>  01  WSBB-LASTUSETIME     PIC S9(15) COMP-3.
>  01  WSBB-EXPIRYTIME      PIC S9(15) COMP-3.
>  01  WSBB-TIME            PIC X(64) VALUE SPACES.
>  PROCEDURE DIVISION.
> *
>  100-MAINLINE SECTION.
> **********************
> *
>  101-PARA.
>      MOVE 'usernam' to WSBB-USERID.
>      MOVE 'PASSWOR' to WSBB-PASSWORD.
>      EXEC CICS VERIFY PASSWORD(WSBB-PASSWORD) USERID(WSBB-USERID)
>           DAYSLEFT(WSBB-DAYS-LEFT)
>           EMSRESP(WSBB-RESP-CODE1)
>           EMSREASON(WSBB-RESP-CODE2)
>           CHANGETIME(WSBB-CHANGETIME)
>           INVALIDCOUNT(WSBB-INVALIDCOUNT)
>           LASTUSETIME(WSBB-LASTUSETIME)
>           EXPIRYTIME(WSBB-EXPIRYTIME)
>           RESP(WSBB-RESP-CODE)
>           RESP2(WSBB-RETURN-CODE)
>      END-EXEC.
> 
> All done according to the manuals.
> Command works fine, but the values of RESP AND RESP2 are always
> invalid values. This is still the case if I use the cics precompiler
> eibresp and eibresp2 fields.
> 
> In all cases the values returned on these 2 fields are
> RESP= -0268166945
> RESP2= 1342181408
> even if the command was sucessefull, on which case RESP should be
> equal zero.
> 
> All other return fields are correct upon execution.
> 
> This is Z/OS 1.07
> CICS/ESA V6.2.0
> CICS Transaction Server Version 2.2.0
> ENTERPRISE COBOL FOR Z/OS  3.4.1 0402
> 
> compile options in place
> ADV,NOAWO,BUFSIZE(22528),NOCOMPILE(S),DATA(31)     
> NODBCS,NODECK,NODUMP,NODYNAM,FASTSRT               
> FLAG(I),NOFLAGSTD                                  
> LANGUAGE(UE),LIB,LINECOUNT(60),LIST,MAP,NONAME     
> NONUMBER,NUMPROC(NOPFD),OBJECT,NOOFFSET,OPTIMIZE   
> OUTDD(SYSOUT),RENT,NOSEQUENCE,SIZE(MAX)            
> SOURCE,SPACE(1),NOSSRANGE,NOTERM,NOTEST,TRUNC(STD)
> NOVBREF,NOWORD,XREF(FULL),NOZWB,APOST              
> 
> Already tried with different TRUNC(xxx) with no luck.
> 
> Any ideas/suggestions welcome
>  
> 
> Regards
> 
> 
> Frederico Fonseca
> ema il: frederico_fonseca at syssoft-int.com

I think you need help from your CICS technical services department or 
your systems programmers.  The fact that your EIBRESP (WSBB-RESP-CODE) 
is way out of range suggests that something is not configured 
correctly in your CICS region.  You might be missing a library for 
RACF in your DFHRPL list.  Or perhaps you're missing a critical 
startup program at region initialization, or the CICS region has 
incorrect SIT parms (System Initialization Table) related to RACF 
processing.

I don't think there is anything in your compile options that should 
cause a problem.  NODYNAM is critical for the EIB interface, but you 
already have that correctly specified.


-- 
http://arnold.trembley.home.att.net/
0
Reply arnold.trembley (268) 5/3/2008 7:37:00 AM 


Frederico,
  I am a little confused by where you have:

> CICS/ESA V6.2.0
> CICS Transaction Server Version 2.2.0

Does this mean you have tried it with both?

Anyway, have you seen the NEWER migration guide information at:

  http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dfhefc00/1.5.7

That does mention changes to the EIBRESP code (with CICS TS 3.x).  Therefore, 
there may be changes (with or without PTFs) at lower levels.
-- 
Bill Klein
 wmklein <at> ix.netcom.com
"Frederico Fonseca" <real-email-in-msg-spam@email.com> wrote in message 
news:iklm14pfhmhshllio7drtni6ki7ssv1h9v@4ax.com...
> Hi all,
>
> I'm having a bit of a problem with checking the return codes from a
> EXEC CICS VERIFY PASSWORD command.
>
> Code as follows
> CODE
> WORKING-STORAGE SECTION.
> 01  WSBB-PASSWORD        PIC X(8) VALUE SPACES.
> 01  WSBB-USERID          PIC X(8) VALUE SPACES.
> 01  WSBB-RESP-CODE       PIC S9(8) COMP VALUE ZEROS.
> 01  WSBB-RESP-CODE1      PIC S9(8) COMP VALUE ZEROS.
> 01  WSBB-RESP-CODE2      PIC S9(8) COMP VALUE ZEROS.
> 01  WSBB-RETURN-CODE     PIC S9(8) COMP VALUE ZEROS.
> 01  WSBB-DAYS-LEFT       PIC S9(4) COMP VALUE ZEROS.
> 01  WSBB-RET-CODE        PIC -9(10).
> 01  WSBB-CHANGETIME      PIC S9(15) COMP-3.
> 01  WSBB-INVALIDCOUNT    PIC S9(4) COMP VALUE ZEROS.
> 01  WSBB-LASTUSETIME     PIC S9(15) COMP-3.
> 01  WSBB-EXPIRYTIME      PIC S9(15) COMP-3.
> 01  WSBB-TIME            PIC X(64) VALUE SPACES.
> PROCEDURE DIVISION.
> *
> 100-MAINLINE SECTION.
> **********************
> *
> 101-PARA.
>     MOVE 'usernam' to WSBB-USERID.
>     MOVE 'PASSWOR' to WSBB-PASSWORD.
>     EXEC CICS VERIFY PASSWORD(WSBB-PASSWORD) USERID(WSBB-USERID)
>          DAYSLEFT(WSBB-DAYS-LEFT)
>          EMSRESP(WSBB-RESP-CODE1)
>          EMSREASON(WSBB-RESP-CODE2)
>          CHANGETIME(WSBB-CHANGETIME)
>          INVALIDCOUNT(WSBB-INVALIDCOUNT)
>          LASTUSETIME(WSBB-LASTUSETIME)
>          EXPIRYTIME(WSBB-EXPIRYTIME)
>          RESP(WSBB-RESP-CODE)
>          RESP2(WSBB-RETURN-CODE)
>     END-EXEC.
>
> All done according to the manuals.
> Command works fine, but the values of RESP AND RESP2 are always
> invalid values. This is still the case if I use the cics precompiler
> eibresp and eibresp2 fields.
>
> In all cases the values returned on these 2 fields are
> RESP= -0268166945
> RESP2= 1342181408
> even if the command was sucessefull, on which case RESP should be
> equal zero.
>
> All other return fields are correct upon execution.
>
> This is Z/OS 1.07
> CICS/ESA V6.2.0
> CICS Transaction Server Version 2.2.0
> ENTERPRISE COBOL FOR Z/OS  3.4.1 0402
>
> compile options in place
> ADV,NOAWO,BUFSIZE(22528),NOCOMPILE(S),DATA(31)
> NODBCS,NODECK,NODUMP,NODYNAM,FASTSRT
> FLAG(I),NOFLAGSTD
> LANGUAGE(UE),LIB,LINECOUNT(60),LIST,MAP,NONAME
> NONUMBER,NUMPROC(NOPFD),OBJECT,NOOFFSET,OPTIMIZE
> OUTDD(SYSOUT),RENT,NOSEQUENCE,SIZE(MAX)
> SOURCE,SPACE(1),NOSSRANGE,NOTERM,NOTEST,TRUNC(STD)
> NOVBREF,NOWORD,XREF(FULL),NOZWB,APOST
>
> Already tried with different TRUNC(xxx) with no luck.
>
> Any ideas/suggestions welcome
>
>
> Regards
>
>
> Frederico Fonseca
> ema il: frederico_fonseca at syssoft-int.com
0
Reply wmklein (2605) 5/3/2008 6:01:04 PM 

On Sat, 03 May 2008 07:37:00 GMT, Arnold Trembley
<arnold.trembley@worldnet.att.net> wrote:

>Frederico Fonseca wrote:
>> Hi all,
>> 
>> I'm having a bit of a problem with checking the return codes from a
>> EXEC CICS VERIFY PASSWORD command.
>> 
>> Code as follows
>> CODE
>> WORKING-STORAGE SECTION.
>>  01  WSBB-PASSWORD        PIC X(8) VALUE SPACES.
>>  01  WSBB-USERID          PIC X(8) VALUE SPACES.
>>  01  WSBB-RESP-CODE       PIC S9(8) COMP VALUE ZEROS.
>>  01  WSBB-RESP-CODE1      PIC S9(8) COMP VALUE ZEROS.
>>  01  WSBB-RESP-CODE2      PIC S9(8) COMP VALUE ZEROS.
>>  01  WSBB-RETURN-CODE     PIC S9(8) COMP VALUE ZEROS.
>>  01  WSBB-DAYS-LEFT       PIC S9(4) COMP VALUE ZEROS.
>>  01  WSBB-RET-CODE        PIC -9(10).
>>  01  WSBB-CHANGETIME      PIC S9(15) COMP-3.
>>  01  WSBB-INVALIDCOUNT    PIC S9(4) COMP VALUE ZEROS.
>>  01  WSBB-LASTUSETIME     PIC S9(15) COMP-3.
>>  01  WSBB-EXPIRYTIME      PIC S9(15) COMP-3.
>>  01  WSBB-TIME            PIC X(64) VALUE SPACES.
>>  PROCEDURE DIVISION.
>> *
>>  100-MAINLINE SECTION.
>> **********************
>> *
>>  101-PARA.
>>      MOVE 'usernam' to WSBB-USERID.
>>      MOVE 'PASSWOR' to WSBB-PASSWORD.
>>      EXEC CICS VERIFY PASSWORD(WSBB-PASSWORD) USERID(WSBB-USERID)
>>           DAYSLEFT(WSBB-DAYS-LEFT)
>>           EMSRESP(WSBB-RESP-CODE1)
>>           EMSREASON(WSBB-RESP-CODE2)
>>           CHANGETIME(WSBB-CHANGETIME)
>>           INVALIDCOUNT(WSBB-INVALIDCOUNT)
>>           LASTUSETIME(WSBB-LASTUSETIME)
>>           EXPIRYTIME(WSBB-EXPIRYTIME)
>>           RESP(WSBB-RESP-CODE)
>>           RESP2(WSBB-RETURN-CODE)
>>      END-EXEC.
>> 
>> All done according to the manuals.
>> Command works fine, but the values of RESP AND RESP2 are always
>> invalid values. This is still the case if I use the cics precompiler
>> eibresp and eibresp2 fields.
>> 
>> In all cases the values returned on these 2 fields are
>> RESP= -0268166945
>> RESP2= 1342181408
>> even if the command was sucessefull, on which case RESP should be
>> equal zero.
>> 
>> All other return fields are correct upon execution.
>> 
>> This is Z/OS 1.07
>> CICS/ESA V6.2.0
>> CICS Transaction Server Version 2.2.0
>> ENTERPRISE COBOL FOR Z/OS  3.4.1 0402
>> 
>> compile options in place
>> ADV,NOAWO,BUFSIZE(22528),NOCOMPILE(S),DATA(31)     
>> NODBCS,NODECK,NODUMP,NODYNAM,FASTSRT               
>> FLAG(I),NOFLAGSTD                                  
>> LANGUAGE(UE),LIB,LINECOUNT(60),LIST,MAP,NONAME     
>> NONUMBER,NUMPROC(NOPFD),OBJECT,NOOFFSET,OPTIMIZE   
>> OUTDD(SYSOUT),RENT,NOSEQUENCE,SIZE(MAX)            
>> SOURCE,SPACE(1),NOSSRANGE,NOTERM,NOTEST,TRUNC(STD)
>> NOVBREF,NOWORD,XREF(FULL),NOZWB,APOST              
>> 
>> Already tried with different TRUNC(xxx) with no luck.
>> 
>> Any ideas/suggestions welcome
>>  
>> 
>> Regards
>> 
>> 
>> Frederico Fonseca
>> ema il: frederico_fonseca at syssoft-int.com
>
>I think you need help from your CICS technical services department or 
>your systems programmers.  The fact that your EIBRESP (WSBB-RESP-CODE) 
>is way out of range suggests that something is not configured 
>correctly in your CICS region.  You might be missing a library for 
>RACF in your DFHRPL list.  Or perhaps you're missing a critical 
>startup program at region initialization, or the CICS region has 
>incorrect SIT parms (System Initialization Table) related to RACF 
>processing.
>
>I don't think there is anything in your compile options that should 
>cause a problem.  NODYNAM is critical for the EIB interface, but you 
>already have that correctly specified.
Found the problem.

Code above is perfectly correct. problem was on one of the programs
higher on the calling stack that was not passing down the correct
linkage dfheiblk, so when my program tries to reference it, it gives
invalid results.

For others info, CICS precompiler programs will replace
          RESP(WSBB-RESP-CODE)
with
"Move eibresp to WSBB-RESP-CODE" where eibresp is supplied on the
linkage.   

Thanks both you and Bill for the replies.


Frederico Fonseca
ema il: frederico_fonseca at syssoft-int.com
0
Reply real-email-in-msg-spam (383) 5/7/2008 5:19:51 PM
comp.lang.cobol 4188 articles. 3 followers.

3 Replies
64 Views

(page loaded in 0.272 seconds)

Similiar Articles:

rsh problem - "password expired" message - comp.unix.shell ...
I am able to execute a command from u... ... comp.sys.hp.hpux Easy enough to verify if this is your problem; try ... rsh problem - "password expired" message Hi, I am trying ...

PASSWORD HISTORY on Solaris - comp.unix.solaris
... so that if you do not verify the clear text password but ... comp.unix.solaris Solaris Password Policy - Brandonhutchinson.com Problems ... solaris Exceed xstart command verify ...

LogonUser fails and GetLastError returns 0 - comp.os.ms-windows ...
I use LogonUser to verify the id and password. I ... for years without this problem occurring. I use LogonUser to verify the id and password. ... HTTP-headers related command ...

LDAP Authentication - Unable to load configuration '/var/ldap/ldap ...
Do you have a suggestion to verify that? I'm able to ... When I tried the ldaplist -l command, I get the same ... ldap ... user must chage password in ... user password problem ...

OpenVPN and Token USB ( long ) - comp.os.linux.networking ...
... Jan 12 13:16:53 centos openvpn[8040]: VERIFY OK ... have found that if I launch directly command ... tunnel is coming up when I give the right password. The problem ...

How to check if nfs connection exists - comp.unix.solaris ...
How do I verify that an nfs connection is established ... That's a problem in solaris 10: you cannot see if a ... Checking of password expiry - comp.unix.solaris How to ...

Kerberos error - KDC reply did not match expectations - comp ...
I'm new to Kerberos and I have an issue in setting my ... KRB5A_64 options =3D = authonly,tgt_verify ... =20 Our Active Directory admins ran the Ktpass command ...

cisco commands for checking for DOS attack - comp.dcom.sys.cisco ...
what are some command that i could use to see if someone ... setting up Strong password policy - comp.unix.solaris ... force overwirte in perl - comp.lang.perl ..... problem ...

Kentrox/Cisco/Subrate DS3 problems.... - comp.dcom.sys.cisco ...
If I do a clock rate command on the hssi interface, it ... service timestamps log datetime msec service password ... Did the local engineer b2b the 3725 and verify frame ...

Automatic Yahoo!mail or Gmail login by Javascript - comp.lang ...
... Gmail account without typing user name and password ... And some may verify other headers that you would have to duplicate. This was an issue when I tried to putz around ...

Upgrading from 2.3: Changes to EXEC CICS VERIFY PASSWORD
When you issue the EXEC CICS VERIFY PASSWORD command, CICS now enforces the revoked status of a user ID or a user's group connection. The new method CICS uses to ...

CICS command summary - IBM - United States
cics command summary ... change password; signoff; signon; verify password ... issue endfile; issue endoutput; issue eods; issue eraseaup

7/15/2012 8:39:12 PM


Reply:



Privacy Policy | All Times Are GMT(UTC) | powered by