Binyamin:

Here is how I have things defined, and I do not get the message that you get:

         LA    R1,1               Most TU entries will need "1"       
*                                                                     
*              ALLOC w/  DDNAME text unit setup                       
         LA    R9,UT_DDN          Point to first text unit            
         USING S99TUNIT,R9        R9 points to "current" TU area      
         LA    R0,DALRTDDN        ... TU for ALLOC Return DDname ...  
         STH   R0,S99TUKEY        ... store in KEY ...                
         LA    R0,8               ... get length ...                  
         STH   R0,S99TULNG        ... store length ...                
         MVC   S99TUPAR(8),SPACE    ... Clear the DDname w/ blanks    


UT_DDN   DS    AL2(0,0,0),CL8   DDN to search (INFO), USE (ALLOC)     
                   DS    0A

The above is copied out of the listing, and you notice there are no message 
lines (I just truncated off the left side, statement number, etc.).

For all SVC99 work, I did not do anything special with the USING statements (no 
labels, etc.). However, I did make use of that with all my DCBs and DECBs.

So, I don't understand, at this point, why you got that warning message (and I 
have Text Units for several different things we are doing with INFO and 
ALLOCation "calls").


Regards,
Steve Thompson

-----Original Message-----

Date:    Mon, 21 Nov 2016 07:03:52 +0200
From:    Binyamin Dissen <[email protected]>
Subject: Re: ASMA033I Storage alignment for unfavorable for dependent DSECT?

It is properly aligned in the main dsect.

ZZZ          DSECT
                CNOP   2,8
DDNTXTU DS 3H,CL8



@DDNTXTU  USING S99TUNIT,DDNTXTU

                STG   R1,@DDNTXTU.S99TUPAR

The assembler knows that the resolved address is at a doubleword offset in ZZZ

On Sun, 20 Nov 2016 15:01:04 -0800 "[email protected]" <[email protected]>
wrote:

:>I don't have access to listings right now, but having just done a few 
routines that were doing SVC99 and making use of all the DSECTs provided by 
IBM, I found that I had to get alignment set up correctly.
:>
:>So, I would start Text Units on a fullword, so that you have (off the top of 
my head):
:>      DS 0A
:>verb  DS H
:>count DS H
:>len   DS H
:>parm  DS X 
:>
:>And then the parm value would be as long as needed. But, I made sure that the 
next text unit started on a full world. I think that will solve your problems.
:>
:>Sorry, I can't remember the correct names of the IBM DSECTs (and their 
related variables) so I could answer you by their names.
:>
:>Regards,
:>Steve Thompson
:>
:>--- [email protected] wrote:
:>
:>From:         Binyamin Dissen <[email protected]>
:>To:           [email protected]
:>Subject: [IBM-MAIN] ASMA033I Storage alignment for unfavorable for dependent 
DSECT?
:>Date:         Sun, 20 Nov 2016 22:42:16 +0200
:>
:>I am receiving
:>
:>ASMA033I Storage alignment for @DDNTXTU.S99TUPAR unfavorable 
:>
:>where the value of S99TUPAR is 6, but it is a dependent using and the actual
:>offset is at a doubleword boundary.
:>
:>Working as designed??

The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.


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

Reply via email to