IBM Security Z Security

 View Only
  • 1.  C2P0268E - explanation

    Posted Wed June 03, 2020 05:47 AM
    Regarding zSecure Alert....
    in the joblog I receive a lot of C2P0268E messages : C2P0268E Command not recognized, scancode=00  
    What does it mean ?
    In the C2P messages I can read:  "This diagnostic message provides the result from the scan operation to determine the command and its keywords and parameters, or the value of the unrecognized command."
    I don't see the unrecognized command  in the message.
    Please, could you help on this ?
    Tks

    ------------------------------
    Luigi Perrone
    ------------------------------


  • 2.  RE: C2P0268E - explanation

    Posted Wed June 03, 2020 06:40 AM
    Do you by any chance use an asterisk or some other character as the first character in the alert configuration member?
    The only supported comment indicator is /*. Otherwise, all lines must have valid configuration statements.
    Btw: it seems that you have exposed a minor defect, in that we show 00, instead of a proper scancode.
    Guus Bonnes

    ------------------------------
    Guus Bonnes
    ------------------------------



  • 3.  RE: C2P0268E - explanation

    Posted Wed June 03, 2020 06:51 AM
    Exactly ! I don't understand the msg because I receive 00 as scancode, and I don't see the relative command 
    No, I don't use special character in the alert configuration
    Maybe a defect ?
    Tks!

    ------------------------------
    Luigi Perrone
    ------------------------------



  • 4.  RE: C2P0268E - explanation

    Posted Wed June 03, 2020 07:51 AM

    If you only have valid statements in the Alert configuration member, then you might need to open a "case" to diagnose why you get this message. We only issue it when the input lines do not start with one of the valid commands (e.g. unsupported characters).

    In the mean time we confirmed that the 00 should really have been something like 08. But without a copy of your configuration statements that doesn't tell us which statement was unacceptable.



    ------------------------------
    Guus Bonnes
    ------------------------------



  • 5.  RE: C2P0268E - explanation

    Posted Wed June 03, 2020 06:54 AM
    Hi Luigi,

    I will say that the documentation is a bit terse. There are two variants of message C2P0268E, one that will print a command name that was found but not recognized, and one that will print an error code because parsing the command input failed.

    If Guus's guess is correct, then the message probably should have printed scancode=08--meaning that the command scan service routine that is used determined that there was a syntax error. If you have a suggestion to make the explanation of the message clearer, we will consider it. :-)

    Best regards,

    --Jeroen

    ------------------------------
    Jeroen Tiggelman
    Software Development and Level 3 Support Manager IBM Security zSecure Suite
    IBM
    Delft
    ------------------------------



  • 6.  RE: C2P0268E - explanation

    Posted Wed June 03, 2020 07:55 AM
    Tks Jeroen, I understand. But in this case scancode=00

    C2P0268E Command not recognized, scancode=00 



    ------------------------------
    Luigi Perrone
    ------------------------------



  • 7.  RE: C2P0268E - explanation

    Posted Wed June 03, 2020 08:44 AM
    To further assist, we really need a view on the input statements, and probably the STC proc where you specify the input files.

    ------------------------------
    Guus Bonnes
    ------------------------------



  • 8.  RE: C2P0268E - explanation

    Posted Wed June 03, 2020 09:22 AM
    Ok, I will try to do it.
    Tks !

    ------------------------------
    Luigi Perrone
    ------------------------------



  • 9.  RE: C2P0268E - explanation

    IBM Champion
    Posted Wed June 03, 2020 12:53 PM
    Some users forget to specify the P in the PPARM keyword of C2POLICE:
    //C2POLICE PROC REGSIZE=256M, Region for zSecure Alert
    // CONFIG=C2R$PARM, Configuration member
    //* TCPDATA=TCPDATCP, TCPIP DATA membername if SYSTCPD is used
    // PPARM=C2PDFLP, C2POLICE parameter member <setname>P
    // PRTOUT=A, Sysout class "normal" output
    // ERROUT=Z Sysout class "debug" output

    If you had specified PPARM=C2PDFL, then the CARLa code in C2PDFL is read as parameter file, instead of the parameters.

    ------------------------------
    Rob van Hoboken
    ------------------------------