Fw: [MI400] Leif's MIFHASH usage (was RE: Generate hash code for a source member?)

["Leif Svalgaard" <leif@xxxxxxxx>]

From: Leif Svalgaard <leif@leif.org>
To: Dan Bale
Sent: Tuesday, May 14, 2002 3:53 PM
Subject: Re: [MI400] Leif's MIFHASH usage (was RE: Generate hash code for a
source member?)


> From: Dan Bale
> > Detailed messages - - - - -
> > Message ID . . . :   MCH5601       Severity . . . :   40
> > Message type . . :   Escape
> > Date sent  . . . :   05/14/02      Time sent  . . :   13:37:37
> >
> > Message . . . . :   Template value not valid for instruction.
> > Cause . . . . . :   The location of the value is template  with an offset
> to
> >   field in bytes X'0000', an offset in field in bits X'0000', a length of
> >   field of 2, and an instruction operand number of 2.  The reason code is
.
> > If
> >   the reason code is X'0000', a reason code may not be available.
> >
>
> hmmm, the following little test program works well at v4r5:
>
>  DCL SPCPTR .ARG1 INIT(ARG1);
>  DCL SPCPTR .ARG2 INIT(ARG2);
>  DCL SPCPTR .ARG3 INIT(ARG3);
>  DCL SPCPTR .ARG4 INIT(ARG4);
>
>  DCL DD ARG1 CHAR(10); DCL DD LIB  CHAR(10) DEF(ARG1) POS(1);
>  DCL DD ARG2 CHAR(10); DCL DD FILE CHAR(10) DEF(ARG2) POS(1);
>  DCL DD ARG3 CHAR(10); DCL DD MBR  CHAR(10) DEF(ARG3) POS(1);
>  DCL DD ARG4 CHAR(40); DCL DD HASH CHAR(40) DEF(ARG4) POS(1);
>
>  DCL OL ARGS(.ARG1, .ARG2, .ARG3, .ARG4) ARG;
>
>  DCL SYSPTR .MIHSMBR INIT("MIHSMBR", TYPE(PGM));
>
>       CPYBLAP    LIB , "LSVALGAARD", " ";
>       CPYBLAP    FILE, "QMISRC"    , " ";
>       CPYBLAP    MBR , "MIHSMBR"   , " ";
>       CALLX     .MIHSMBR, ARGS, *;
> BRK "1";
>       RTX        *;
> PEND:
>
> ----------
>
> another thing that sometimes gives problems is that the "reserved"
> bytes of the template must sometimes be binary zeroes (although
> the manual *does* say 'ignored' for the CIPHER instruction).
>
> Try to expand the CONTROL data item to CHAR(96) and
> start the program with a CPYBREP CONTROL, X'00';
>
> other than that I don't know...
>
> maybe others can try it?
> Maybe the SHA-1 is not supported at v3r2?
> anybody have an answer to this?
>
>
>