On 24 May 2012 08:24, CRPence wrote:
On 24 May 2012 07:46, Stone, Joel wrote:
<<SNIP>>

STRGRPJS JOB(HIJ544_LS TCMT544_LS 01) TIME(*IMMED)
PARM((HIJ544PRM1 'LS*ALLJSTONE'))
Cause: Command to execute is: CALL PGM(HIJ544) PARM(LS*ALLJSTONE)
CPD0020 "Character 'A' not valid following string 'LS* '."
<<SNIP>>

STRGRPJS JOB(HIJ544_LS TCMT544_LS 01) TIME(*IMMED)
PARM((HIJ544PRM1 '''LS*ALLJSTONE'''))
???#### "Quotes ('') in parameter data must appear in pairs."

All of the other error messages shown appear to be typical and
expected error messages issued by the command analyzer [CPD0000
range], followed by the CPF0001. The above seems not to be like
those. However as is so often the case, the message identifier,
second level text, message type, and the context [from and to
program, procedures etc.] was omitted from the quoted message,
so I can only guess that the AJS is diagnosing that.
What does the message say is the recovery?


I did not realize the AJS stuff was documented in the InfoCenter; I found it was, after searching the text of the ???#### message. With the original error [since re-inserted in the first quoted message], I can see that the design of that AJS feature appears to want to take the "Parameters" (PARM) parameter values of the STRGRPJS command [and apparently similarly for SMBJOBJS; maybe an UPDDEP command?] to generate a command string for a CL CALL. However due to a limitation, though IMO a defect, the generated string does not resolve the requirement to delimit the given string; i.e. the generated command string [without quote delimiting] is not valid according to the Command Analyzer; i.e. "CALL PGM(HIJ544) PARM(LS*ALLJSTONE)". The feature should have IMO, generated a functional invocation of [without quote delimiting] "CALL PGM(HIJ544) PARM('LS*ALLJSTONE')". And worse, the feature appears to explicitly prevent the user from easily resolving the issue by escaping the apostrophes; i.e. issues msg???#### "Quotes ('') in parameter data must appear in pairs.".

Perhaps try using the following, to test if that circumvents the issue:
PARM((HIJ544PRM1 x'D3E25CC1D3D3D1E2E3D6D5C5'))

Regards, Chuck

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].