Even so, at the time of the earlier question, I couldn’t make much sense of what was wanted. This time it makes a little more sense.

The program (or procedure) will accept two parms, a date variable in some knoen format a a code letter. Each code letter will correspond to a specific date format. When the code letter is ‘j’, the program should convert the input date to *MDY format. When the code is ‘M’, the conversion should be to *JUL format. The output should be in the form of a message sent with SNDPGMMSG.

The format of the input date is critical. It seems possible that code ‘j’ means that the input date is in julian format and should be converted to *MDY. Code ‘M’ would provide the opposite conversion.

Unfortunately, if this is indeed homework, the question should identify it as homework, should show the work that has already been done and should describe what obstacle needs explanation.

Answers should be limited to explanation of the meaning of the obstacle and methods to overcome it. Answers should be guidance rather than straight substitution of work.

Students can benefit from professional guidance.

Tom

C *MDY0 TEST (D) DAT_C6 51 (*IN51 On if date test failed)
C IF NOT *IN51 (Date is in MMDDYY format)
C do something here
C GOTO @TAG01
C ENDIF
*
C *CYMD0 TEST (D) DAT_C7 51 (test for CYYMMDD format without separator)
C IF NOT *IN51 (Date is in CYYMMDD format)
C do something here
C GOTO @TAG01
C ENDIF

C *YMD0 TEST(D) DAT_C6 51 (test of YYMMDD format without separator)
C IF NOT *IN51 (Date is in YYMMDD format)
C do something here
C GOTO @TAG01
C ENDIF

This code makes a lot more sense when its rendered in fixed font. Notice how the various date formats are tested. If the test fails, it tests a different format looking for one that is valid. Just code a date test for every format you think the program will encounter. If all tests fail, its an invalid date.

I warned you . . . this is really old code but it works.
You can do the same thing in free form RPG and it looks a lot better.