Thanks for the additional example.
It does give a warning message, so probably RC=4 right?  There could be cases 
where that's ok, but it's safer to assume not.

David Shackelford
DFSMS Development, IBM

On Tue, 1 Oct 2024 21:22:48 -0400, Tony Thigpen <[email protected]> wrote:

>I see the same issue on VSE 6.2 HLASM R6.0  2024/10/02 01.33
>
>0025F0 47F0 9098            02604  2194      B TONYXXX
>0025F4 9120 D064      00064        2195          TM    TMR4FLG1,FLG1MSG6
>0025F8 47E0 9090            025FC  2196          BNO   TU_PUB_R15
>                                    2197 TU_PUBJCFLG TEINDUMP PUBJCFLG
>0025FC                             2198 TU_PUB_R15 DS 0H
>                                    2199 *TONY*
>0025FC 91F8 2007      00007        2200          TM    PUBJCFLG,PUBDVCUP
>002600 4780 91C6            02732  2201          BZ    TU_DEVICE_DOWN
>                                    2202 TONYXXX  DROP  R2
>** ASMA165W UNEXPECTED NAME FIELD
>** ASMA435I RECORD 1137 IN SYSIPT ON VOLUME:
>002604                             2203 TU_CHK_DEVINF DS 0H
>
>Tony Thigpen
>
>Steve Thompson wrote on 10/1/24 5:29 PM:
>> Yes the subject is correct.
>> 
>> I just ran into this situation. Program is in production.
>> 
>> Multiple points in this program do the following:
>> 
>> 
>>          B  DROPR11
>> 
>> Now, a few screens away we have this:
>> 
>> 
>> DROPR11 DROP R11
>>          LA   R1,xxxxx  (or something similar)
>> 
>> The DROPR11 above gets flagged with an invalid label
>> 
>> The various B  DROPR11 statements resolve to the LA R1xxxx
>> 
>> Anyone see a problem with this? When did this kind of thing get accepted?
>> 
>> I would have figured that invalid label would have gotten at least an RC=8
>> 
>> And every one of those "Branch" instructions would have been flagged for 
>> an undefined label or some such.
>> 
>> 
>> An inquiring mind would like to know.
>> 
>> Regards,
>> Steve Thompson
>> 
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to