Skip to Content
author's profile photo Former Member
Former Member

Error monitoring during an ASCII conversion

I've used a CL program posted on the old SAPoniSeries forums to monitor for breaks/errors during an SAP upgrade and send a pager message. Is it possible to create anything similiar to look for a stop during an ASCII conversion?

thanx

Mark

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Oct 17, 2006 at 02:58 PM

    Hi Mark,

    that's interesting !

    I was asked the same question from Doreen half a year ago and said: no ...

    But, yesterday, I had the idea how to do that similar ...

    (but by now, I didn't put the few lines of code together)

    I always use the following scripts for the CPC:

    (Similar to SAP Note 739386 - check there in detail)

    Pgm: R3SETUP/R3SETUPBCH

    =======================

    PGM PARM(&SID &TYPE &TEMPLATE)

    DCL VAR(&SID) TYPE(*CHAR) LEN(3)

    /* UNLOAD OR RELOAD */

    DCL VAR(&TYPE) TYPE(*CHAR) LEN(10)

    DCL VAR(&TEMPLATE) TYPE(*CHAR) LEN(20)

    DCL VAR(&LIB) TYPE(*CHAR) LEN(10) VALUE('R3SETUP')

    DCL VAR(&INFILE) TYPE(*CHAR) LEN(10) VALUE('R3SETUPIN')

    DCL VAR(&OUTFILE) TYPE(*CHAR) LEN(10) VALUE('R3SETUPOUT')

    CRTPF FILE(&LIB/&INFILE) RCDLEN(80) REUSEDLT(*NO)

    MONMSG MSGID(CPF7302) EXEC(DO)

    CLRPFM FILE(&LIB/&INFILE)

    ENDDO

    CRTPF FILE(&LIB/&OUTFILE) RCDLEN(80)

    MONMSG MSGID(CPF7302) EXEC(DO)

    CLRPFM FILE(&LIB/&OUTFILE)

    ENDDO

    OVRDBF FILE(STDIN) TOFILE(&LIB/&INFILE) EOFDLY(1) SHARE(*YES)

    OVRDBF FILE(STDOUT) TOFILE(&LIB/&OUTFILE) SHARE(*YES)

    OVRDBF FILE(STDERR) TOFILE(&LIB/&OUTFILE) SHARE(*YES)

    CD DIR('/tmp/' *CAT &TYPE *TCAT '/' *CAT &SID)

    R3SETUP PARMLIST(&TEMPLATE)

    DLTOVR FILE(STDIN STDOUT STDERR)

    ENDPGM

    Pgm: R3SETUP/R3SETUPSBM

    =======================

    PGM PARM(&SID &TYPE &TEMPLATE)

    DCL VAR(&SID) TYPE(*CHAR) LEN(3)

    /* UNLOAD OR RELOAD */

    DCL VAR(&TYPE) TYPE(*CHAR) LEN(10)

    DCL VAR(&TEMPLATE) TYPE(*CHAR) LEN(20)

    SBMJOB CMD(CALL PGM(R3SETUPBCH) PARM(&SID &TYPE +

    &TEMPLATE)) JOB(R3SETUPBCH) JOBQ(QCTL) +

    LOG(4 00 *SECLVL)

    ENDPGM

    =>

    Unload:

    addlible r3setup

    CALL PGM(R3SETUPSBM) PARM(DEV UNLOAD 'dbexip.r3s')

    Reload:

    addlible r3setup

    CALL PGM(R3SETUPSBM) PARM(DEV RELOAD 'dbcpip.r3s')

    How to check for the current state ?

    DSPPFM FILE(R3SETUP/R3SETUPOUT)

    How to "answer" to the questions ?

    STRSQL: (keep in mind, that the first entry normally "disappears")

    insert into r3setup/r3setupin

    values('2 ')

    or UPDDTA r3setup/r3setupin

    (Do not forget, that the first entry of data is ALWAYS lost !)

    What happens during a CPC ?

    I NEVER had the case, that it somehow runs on message-wait after that you entered the data already. It ONLY stops totally and therefore the job disappears !

    Here is the idea: You just insert an ALCOBJ on a new *DTAARA CPCACTIVE *EXCLRD. Your pager tool tries to allocate the same. As soon as this is successful, it can page you to wake you up with trouble or final success 😊)

    (I never had cases, that are not covered with this idea)

    Good luck with that,

    Volker Gueldenpfennig, consolut.gmbh

    http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 17, 2006 at 01:35 PM

    Hello Mark,

    ASCII conversion is a different thing.

    Here you not only have to monitor the R3SETUP job, but also all R3LOAD jobs, if the import was terminated successfully.

    If you know about the structure and content in IFS-Directories unload, reload and data - it would be helpful to monitor the files in these directories.

    Regards

    Guido

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.