I think we would see a.b. rather than just b if there was a prefix involved

I would recommend a LISTC before and after the del alias as a diagnosis process.


Lizette

-----Original Message-----
>From: Mark Steely <[email protected]>
>Sent: Oct 30, 2014 3:34 PM
>To: [email protected]
>Subject: Re: del alias command
>
>My prefix is always set to null - some work without the quotes others do not 
>
>Thanks
>
>-----Original Message-----
>From: IBM Mainframe Discussion List [mailto:[email protected]] On 
>Behalf Of Wayne Bickerdike
>Sent: Thursday, October 30, 2014 5:01 PM
>To: [email protected]
>Subject: Re: del alias command
>
>Check your TSO PROFILE PREFIX variable.
>
>Always safer to fully qualify and surround with quotes.
>
>If your PREFIX is NULL, it would have worked without quotes.
>
>On Fri, Oct 31, 2014 at 5:37 AM, Mark Steely <[email protected]> wrote:
>
>> We are z/OS v1r13. I have a confusing issue. We have a dataset that 
>> get generated every week that  has delete alias commands. I go to 
>> option 3.4 and list the dataset and type ex to process the file. Most 
>> of the alias's get deleted but some come up as not found. Then I try 
>> typing in the del alias command from the command line "tso del x18860 
>> alias" and I receive the same error. If I put the alias name in single 
>> quotes the command works.
>> Why do I need the quotes for some alias names but not for others. This 
>> seems to have started with z/os V1r13.
>>
>> IDC3901I ERROR QUALIFYING X18860
>> IDC3902I ** DEFAULT SERVICE ROUTINE ERROR CODE 20, LOCATE ERROR CODE 8 
>> IDC0014I LASTCC=8
>> ***
>>
>> I also have updated IGGCAT00 and executed the command to activate it:
>> (this was done  at least 6 months ago)
>>
>> /*  REQUIRED MEMBER - DEFAULTS WIL BE USED - DO NOT DELETE V1R13  */
>> EXTENDEDALIAS(YES)
>>
>> Thanks
>>
>>
>> Mark Steely
>>
>>
>>
>> ******* CONFIDENTIALITY NOTICE *******
>>
>>
>>
>> This e-mail message and all attachments transmitted with it may 
>> contain legally privileged and confidential information intended 
>> solely for the use of the addressee. If the reader of this message is 
>> not the intended recipient, you are hereby notified that any reading, 
>> dissemination, distribution, copying, or other use of this message or 
>> its attachments is strictly prohibited. If you have received this 
>> message in error, please notify the sender immediately and delete this 
>> message from your system.
>> Thank you.
>>
>>
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions, send 
>> email to [email protected] with the message: INFO IBM-MAIN
>>
>
>
>
>--
>Wayne V. Bickerdike
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
>[email protected] with the message: INFO IBM-MAIN
>
>
>******* CONFIDENTIALITY NOTICE *******
>
>This e-mail message and all attachments transmitted with it may contain 
>legally privileged and confidential information intended solely for the use of 
>the addressee. If the reader of this message is not the intended recipient, 
>you are hereby notified that any reading, dissemination, distribution, 
>copying, or other use of this message or its attachments is strictly 
>prohibited. If you have received this message in error, please notify the 
>sender immediately and delete this message from your system. Thank you.
>
>
>
>----------------------------------------------------------------------
>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